Online 185.189.255.162:35400 checked 11m ago
104KA ToP Mod
Connect
srv = rust.server("185.189.255.162:35410")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 58% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 6d 16h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 16h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 16h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 12 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 17 Oct, 21:19 UTC12d ago | 3 | NaN | running | 0 |
| 1 | Thu 15 Oct, 13:03 UTC14d ago | 2 | held half | 2.3 days | 0 |
| 2 | Thu 1 Oct, 11:58 UTC28d ago | 146+26 queue | NaN | 14 days | 67 |
| 3 | Wed 30 Sep, 11:58 UTC29d ago | 147+26 queue | NaN | 1 days | 69 |
| 4 | Tue 29 Sep, 11:58 UTC30d ago | 147+20 queue | NaN | 1 days | 73 |
| 5 | Mon 28 Sep, 11:58 UTC31d ago | 147+19 queue | NaN | 1 days | 53 |
| 6 | Sun 27 Sep, 12:02 UTC32d ago | 147+26 queue | NaN | 1 days | 126 |
| 7 | Sat 26 Sep, 11:58 UTC33d ago | 147+26 queue | NaN | 1 days | 120 |
| 8 | Fri 25 Sep, 11:58 UTC34d ago | 147+18 queue | NaN | 1 days | 71 |
| 9 | Thu 24 Sep, 11:58 UTC35d ago | 145+7 queue | NaN | 1 days | 59 |
| 10 | Wed 23 Sep, 11:58 UTC36d ago | 147+17 queue | NaN | 1 days | 50 |
| 11 | Tue 22 Sep, 11:58 UTC37d ago | 147+17 queue | NaN | 1 days | 60 |
| 12 | Mon 21 Sep, 11:58 UTC38d ago | 146+11 queue | NaN | 1 days | 73 |
| 13 | Sun 20 Sep, 11:58 UTC39d ago | 147+29 queue | NaN | 1 days | 51 |
| 14 | Sat 19 Sep, 11:58 UTC40d ago | 148+29 queue | NaN | 1 days | 102 |
| 15 | Fri 18 Sep, 11:58 UTC41d ago | 148+18 queue | NaN | 1 days | 56 |
| 16 | Thu 17 Sep, 11:58 UTC42d ago | 147+14 queue | NaN | 1 days | 56 |
| 17 | Wed 16 Sep, 11:58 UTC43d ago | 147+14 queue | NaN | 1 days | 31 |
| 18 | Tue 15 Sep, 11:58 UTC44d ago | 142 | NaN | 1 days | 133 |
| 19 | Mon 14 Sep, 11:58 UTC45d ago | 142 | NaN | 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.
display(srv.map, srv.info())
Map
4000 · seed 290843
- map
- Procedural Map
- size
- 4000
- seed
- 290843
Server
srv.info()- address
- 185.189.255.162:35400
- region
- –
- max players
- 200
- group limit
- 5 max
- wipe schedule
- monthly
- last wipe
- 17 Oct 2026, 21:19 UTC
- hostname
- –
- first seen
- 13 Sep 2026
About this server · in its own words
print(srv.description)
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [RU] | КЛАССИКА | ДЛЯ НОВИЧКОВ | EU · groups of 5 · monthly · 1 on average | 0/200 |
| 1 | Rust: City of Tarkov [MAIN] | NA · groups of 5 · monthly · 1 on average | 1/50 |
| 2 | Rust up North | groups of 6 · monthly · 1 on average | 0/50 |
| 3 | Rustafied.com - US Low Pop | NA · groups of 6 · monthly · 90 on average | 103/150 |
| 4 | Rustafied.com - EU Low Pop | EU · groups of 6 · monthly · 89 on average | 37/150 |
| 5 | Rustoria.co - EU Low Pop | EU · groups of 6 · monthly · 81 on average | 20/100 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does 104KA ToP Mod rank?
Rank #12,863 on seven-day player hours for 104KA ToP Mod, within the top 58% of all ranked servers.
How full does 104KA ToP Mod run?
Current row: 0 players on 104KA ToP Mod, against 200 slots. Over the last seven days it averaged 0 players and peaked at 1.
About the server
How well does 104KA ToP Mod perform?
Averaged over 48 hours: 93 server fps, never under 79. The entity count peaked at 93,750, covering buildings, deployables and the rest of the world. A high of 4,805 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on 104KA ToP Mod?
Rust network protocol 2634 and build 167781 on Windows is what 104KA ToP Mod runs. Steam updates your game for you, but the protocol must match to join.
How reliable is 104KA ToP Mod, and is it up?
104KA ToP Mod reports itself online at the current refresh. A restart about 10 days 10 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is 104KA ToP Mod hosted?
For 104KA ToP Mod, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 185.189.255.162:35400.
Map and rules
Which settings and rules does 104KA ToP Mod run?
No gather rate appears in the name: 104KA ToP Mod. Group size tops out at 5 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has 104KA ToP Mod selected?
104KA ToP Mod runs a procedural map of size 4,000 with seed 290843, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does 104KA ToP Mod wipe, and on what schedule?
Once a month 104KA ToP Mod wipes, with the force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. The world it runs now was generated 12 days 5 hours ago. Its tags carry a monthly wipe schedule.
On 104KA ToP Mod, what happens on wipe day?
Across recent wipes the busiest point averaged 50 players. The crowd on the latest wipe topped out 12 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Tags, lists
Which Rust Data filters and lists contain 104KA ToP Mod?
The Rust Data lists that 104KA ToP Mod fits are: Modded Rust servers. These filters bring it up 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.
How should you read the server tags on 104KA ToP Mod?
Read by the game's server browser, the tags 104KA ToP Mod publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp200 (Max players): The server lists 200 slots; ts5 (Group limit): The team cap is 5; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way to join 104KA ToP Mod?
Enter client.connect 185.189.255.162:35400 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://game.104ka.ru.