Fig. 1Players on 104KA ToP ModRG-S12874-01 · Sheet 1 of 11
Fig. 2
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S12874-02 · Sheet 2 of 11
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 58% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S12874-03 · Sheet 3 of 11
Schedule
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 6d 17h.
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
6d 17hThu 5 Nov, 19:00 UTCFW
34d 17hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Sat 17 OctThu 15 OctThu 1 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 3, 12 hours in.
ScheduleExpected wipesRG-S12874-04 · Sheet 4 of 11
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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
Wed 23 Sep, 11:58 UTC36d ago
147+17 queue
–
1 days
50
Tue 22 Sep, 11:58 UTC37d ago
147+17 queue
–
1 days
60
Mon 21 Sep, 11:58 UTC38d ago
146+11 queue
–
1 days
73
Sun 20 Sep, 11:58 UTC39d ago
147+29 queue
–
1 days
51
Sat 19 Sep, 11:58 UTC40d ago
148+29 queue
–
1 days
102
Fri 18 Sep, 11:58 UTC41d ago
148+18 queue
–
1 days
56
Thu 17 Sep, 11:58 UTC42d ago
147+14 queue
–
1 days
56
Wed 16 Sep, 11:58 UTC43d ago
147+14 queue
–
1 days
31
Tue 15 Sep, 11:58 UTC44d ago
142
–
1 days
133
Mon 14 Sep, 11:58 UTC45d ago
142
–
1 days
48
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.
Table 1Wipe logRG-S12874-05 · Sheet 5 of 11
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
What uptime is recorded for 104KA ToP Mod, and is it up?
Right now, 104KA ToP Mod is recorded as online. About 10 days 9 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
2.
How does 104KA ToP Mod perform, as measured?
92 server fps on average over the last 48 hours, and never under 79. Counted at its highest: 93,750 entities, buildings, deployables and the rest of the world included. Memory use peaked at 4,805 MB. Players feel low fps and a climbing entity count as lag.
3.
In which location is 104KA ToP Mod hosted?
No region is published by 104KA ToP Mod. Where a server says it is, that is what Rust Graphs shows; no lookup of the machine's location is made. 185.189.255.162:35400 is its address.
4.
On which Rust version is 104KA ToP Mod running?
The platform is Windows and the version is Rust network protocol 2634 and build 167781 on 104KA ToP Mod. The same protocol is required for joining, and Steam updates your game to it.
Player data
5.
What player count is recorded on 104KA ToP Mod?
Current player count on 104KA ToP Mod: 0, of 200 slots. The seven-day mean is 0 players; the peak over the same period is 1.
6.
Against other Rust servers, where is 104KA ToP Mod placed?
Within the top 58% of all ranked servers: 104KA ToP Mod at #12,874 for player hours, seven days recorded.
Schedules
7.
What happens on 104KA ToP Mod on the day of a wipe?
The recent wipes averaged a busiest count of 50 players. At 12 hours after the latest wipe the crowd was at its peak. Half that peak was held until the next wipe in 100% of its recent wipes.
8.
What wipe schedule has been recorded for 104KA ToP Mod?
The force wipe is the only wipe at 104KA ToP Mod, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The current world has been in use since 12 days 4 hours ago. Its tags give a wipe schedule of one wipe per month.
Rules and settings
9.
What settings and rules apply on 104KA ToP Mod?
The name of 104KA ToP Mod records no gather rate. 5 players per group at most. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. The server browser lists it under Modded: plugins or settings change the game. Plugins run: Oxide. VAC is on: that is Valve's anti-cheat.
10.
What is the map for 104KA ToP Mod?
Seed 290843 and size 4,000 define the procedural map 104KA ToP Mod generates in game. Size and seed fix the map, so this page links it on RustMaps for viewing.
Filters
11.
On Rust Graphs, which lists and filters contain 104KA ToP Mod?
The Rust Graphs lists that carry 104KA ToP Mod are: Modded Rust servers. It is returned by these filters on the server list: 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.
12.
Which meaning is attached to each tag on 104KA ToP Mod?
gmvanilla (Game mode): The mode is vanilla survival; mp200 (Max players): 200 player slots; ts5 (Group limit): The team limit is 5; v2634 (Protocol): Your game must match protocol 2634 to join; cs167781 (Build): Build: 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^m (Monthly): Facepunch's force wipe brings a monthly wipe; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded are the tags 104KA ToP Mod publishes; the game's server browser reads them. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
How to join
13.
What is the way to connect to 104KA ToP Mod?
In Rust, press F1 and type client.connect 185.189.255.162:35400 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. https://game.104ka.ru is its website.
NotesAnswered from the figuresRG-S12874-10 · Sheet 10 of 11
Key
Server tags
what each one means
Published asmp200,ptrak,$r?,v2634,^m,gmvanilla,cs167781,ts5,^o^z
Game
gmvanilla
Game modeThe mode is vanilla survival.
mp200
Max players200 player slots.
ts5
Group limitThe team limit is 5.
v2634
ProtocolYour game must match protocol 2634 to join.
cs167781
BuildBuild: 167781.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeRegion code not set.
Wipe schedule
^m
MonthlyFacepunch's force wipe brings a monthly wipe.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings change the game, so it is listed under Modded.
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.
KeyTag string decodedRG-S12874-11 · Sheet 11 of 11