RUST METRICSFlight deck · live data
Data live Servers11,793 Players79,700 Populated3,567 Fresh wipes 3 h247 Scan5 min
‹ All servers185.189.255.162:35400
Online Full Queue Fresh wipe Wipe due No query

104KA ToP Mod

Online 185.189.255.162:35400 checked 15m ago

monthly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 21:00 UTC
0 50 100 150 200 PAX 0 /200

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 99 SERVER FPS

Server fps

48 h low 79 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 93,260 ×1000

Entities

48 h range 93,096–93,750 · memory 4,089 MB
1239 ET SINCE RESTART 10D 06H

Uptime

10 days 6 hours since its last restart, at the last reading
7-day average0peak 1
Rank#12,861top 58%
Last wipe12d agomonthly schedule
Next wipe6d 20hThu 5 Nov, 19:00 UTC FW
Memory4,089MBat the last reading
REC 1

Players

AveragePeak
0123423:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020023:0008:0017:0003:0012:0021:00

48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep27 Sep4 Oct15 Oct22 Oct29 Oct

Top 58% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 6d 20h. The force wipe · high confidence

usual gap1 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak50players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC6d 20hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC34d 20hFW

The first 48 hours of its last wipes

Sat 17 OctThu 15 OctThu 1 Oct
050100150200+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 12 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 21:19 UTC12d ago 3 – running 0
Thu 15 Oct, 13:03 UTC14d ago 2 held half 2.3 days 0
Thu 1 Oct, 11:58 UTC28d ago 146+26 queue – 14 days 67
Wed 30 Sep, 11:58 UTC29d ago 147+26 queue – 1 days 69
Tue 29 Sep, 11:58 UTC30d ago 147+20 queue – 1 days 73
Mon 28 Sep, 11:58 UTC31d ago 147+19 queue – 1 days 53
Sun 27 Sep, 12:02 UTC32d ago 147+26 queue – 1 days 126
Sat 26 Sep, 11:58 UTC33d ago 147+26 queue – 1 days 120
Fri 25 Sep, 11:58 UTC34d ago 147+18 queue – 1 days 71
Thu 24 Sep, 11:58 UTC35d ago 145+7 queue – 1 days 59

Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on 104KA ToP Mod?

An average of 50 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 12 hours in. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.

When does 104KA ToP Mod wipe?

With the force wipe, once a month, 104KA ToP Mod wipes. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world in play was created 12 days 1 hours ago. Its tags carry a monthly wipe schedule.

Tag meanings

Which tags does 104KA ToP Mod carry, and what do they mean?

These are the tags 104KA ToP Mod publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp200 (Max players): Slots: 200; ts5 (Group limit): Team cap: 5; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does 104KA ToP Mod appear in Rust Metrics lists and filters?

On Rust Metrics, 104KA ToP Mod sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 2 weeks.

Player count

What position does 104KA ToP Mod hold among Rust servers?

Ranking for 104KA ToP Mod: #12,861 on seven-day player hours, top 58% of all ranked servers.

What is the population on 104KA ToP Mod?

Current headcount on 104KA ToP Mod: 0 players, 200 slots available. Seven-day check: 0 players on average. Peak reading: 1.

Server details

Which location does 104KA ToP Mod run from?

Reading: location. 104KA ToP Mod gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 185.189.255.162:35400.

What Rust version is 104KA ToP Mod on?

Rust network protocol 2634 and build 167781 on Windows is the build 104KA ToP Mod runs. Matching protocol is required to join. Let Steam update your game.

How does 104KA ToP Mod perform?

Check: fps. Average 92 server fps over the last 48 hours, low of 79. Within range. Peak entity count: 93,750. Buildings, deployables and all else included. Memory peak: 4,589 MB. Lag, as players feel it, is low fps plus a climbing entity count.

What is the uptime on 104KA ToP Mod, and is it online?

104KA ToP Mod reports online. Status: normal. Reading: uptime. About 10 days 6 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Settings and map

What rules does 104KA ToP Mod enforce, and what are its settings?

No gather rate appears in the name: 104KA ToP Mod. The cap on groups is 5 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on 104KA ToP Mod?

Size 4,000 and seed 290843: the game generates the procedural map on 104KA ToP Mod from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to 104KA ToP Mod?

Check: join. Open Rust, press F1, then enter client.connect 185.189.255.162:35400. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://game.104ka.ru.

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2634,^m,gmvanilla,cs167781,ts5,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
mp200
Max players Slots: 200.
ts5
Group limit Team cap: 5.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Check: category. Modded, because plugins or settings alter the game.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.