Online 160.251.236.100:28015 checked 9m ago
SUMI_Rust
Connect
srv = rust.server("160.251.236.100:28017")
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 22 Oct. 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 38% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 44 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 21:33 UTC6d ago | 1 | NaN | running | 0 |
| 1 | Thu 22 Oct, 13:29 UTC6d ago | 1 | NaN | 0.3 days | 0 |
# 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())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 173/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 125/100 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 81/700 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 20/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 24/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 84 on average | 260/700 |
Quick answers
From the figures on this page.
Player counts
How does SUMI_Rust compare in the rankings?
Rank #8,358 on seven-day player hours for SUMI_Rust, within the top 38% of all ranked servers.
How full does SUMI_Rust run?
The sample now reads 0 players for SUMI_Rust, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 1.
Server facts
How well does SUMI_Rust perform?
Averaged over 48 hours: 58 server fps, never under 33. The entity count peaked at 94,110, covering buildings, deployables and the rest of the world. Memory peaked at 3,551 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does SUMI_Rust run?
Version Rust network protocol 2635 and build 167781 on Linux is reported by SUMI_Rust. The protocol has to match before you can join, and Steam does the updating.
Is SUMI_Rust up, and what does its uptime show?
SUMI_Rust reports itself online at the current refresh. The uptime it reports puts the last restart about 3 days 20 hours ago. Uptime of 99% across the last 6 full days: 143 hours of 144. The first row Rust Data holds for it is dated 22 October 2026.
Where does SUMI_Rust sit?
No region is published by SUMI_Rust. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 160.251.236.100:28015.
Settings and map
What rules and settings are recorded for SUMI_Rust?
You will not find a gather rate in the string SUMI_Rust. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on SUMI_Rust?
Size 4,000, seed 1337: the procedural map on SUMI_Rust, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Under map name you will find: Custom Map.
Wipe schedule
On what schedule does SUMI_Rust wipe?
Too few wipes are on record for SUMI_Rust to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 6 days 15 hours ago.
What is wipe day on SUMI_Rust like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 44 hours after it began.
Lists and tags
Which Rust Data filters and lists contain SUMI_Rust?
On Rust Data, SUMI_Rust appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on SUMI_Rust?
Read by the game's server browser, the tags SUMI_Rust publishes are: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^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.
Connecting
What is the way to join SUMI_Rust?
In Rust, F1 opens the console: type client.connect 160.251.236.100:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.