Offline 31.57.56.141:28015 checked 12d ago
My Staging Test Server
Connect
srv = rust.server("31.57.56.141:28016")
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. 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 70% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 14:04 UTC12d ago | 1 | NaN | running | 0 |
| 1 | Thu 8 Oct, 17:03 UTC19d ago | 0 | NaN | 6.9 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())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 31.57.56.141:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 14:04 UTC
- hostname
- –
- first seen
- 30 Sep 2026
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 · 156 on average | 124/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 131/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 57/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 32/1000 |
Quick answers
From the figures on this page.
Player counts
What position does My Staging Test Server take in the server rankings?
Rank #15,098 on seven-day player hours for My Staging Test Server, within the top 70% of all ranked servers.
How many players does My Staging Test Server hold at once?
The current row shows My Staging Test Server offline; the last response was 12 days 16 hours ago.
About the server
What is the Rust version on My Staging Test Server?
Rust network protocol 2635 and build 168118 on Windows is what My Staging Test Server runs. Steam updates your game for you, but the protocol must match to join.
Is My Staging Test Server up, and what does its uptime show?
Offline now for My Staging Test Server, last seen 12 days 16 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 30 September 2026.
Where does My Staging Test Server sit?
For My Staging Test Server, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 31.57.56.141:28015 is its address.
Map and rules
Which settings and rules does My Staging Test Server run?
You will not find a gather rate in the string My Staging Test Server. No custom cap; the default of 8 players per group stands. Recorded as survival, 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. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has My Staging Test Server loaded?
The game generates its map: procedural, on My Staging Test Server.
Wipe schedule
When does My Staging Test Server wipe, and on what schedule?
Too few wipes are on record for My Staging Test Server to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 12 days 17 hours ago.
On My Staging Test Server, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does My Staging Test Server appear among Rust Data lists and filters?
On Rust Data, My Staging Test Server appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on My Staging Test Server?
The game's server browser reads these tags from My Staging Test Server: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168118 (Build): Build number: 168118; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. 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 into My Staging Test Server?
The manual route: launch Rust, F1, then client.connect 31.57.56.141:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.