Offline 31.58.178.2:28015 checked 10d ago
My Staging Test Server
Connect
srv = rust.server("31.58.178.2: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 bestTop 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 0, 46 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 14:04 UTC12d ago | 0 | NaN | running | 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.58.178.2:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 14:04 UTC
- hostname
- –
- first seen
- 12 Oct 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 · 164 on average | 154/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 112 on average | 135/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 28/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 86 on average | 147/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 46/1000 |
Quick answers
From the figures on this page.
Population data
What position does My Staging Test Server take in the server rankings?
Over the last seven days My Staging Test Server sits at #15,246 on player hours, in the top 70% of ranked servers.
How full does My Staging Test Server run?
My Staging Test Server returns no live count at this refresh, having last been seen 10 days 8 hours ago.
About the server
What is the Rust version on My Staging Test Server?
Rust network protocol 2635 and build 168330 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?
My Staging Test Server is offline at this refresh; the last response came 10 days 8 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 12 October 2026.
Which location does My Staging Test Server run from?
No region is published by My Staging Test Server. Rust Data does not look up where the machine stands; it shows where a server says it is. 31.58.178.2:28015 is its address.
Map and rules
Which rules apply on My Staging Test Server, and what settings?
No gather rate appears in the name: My Staging Test Server. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. 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, Valve's anti-cheat, is enabled.
Which map has My Staging Test Server loaded?
The game generates its map: procedural, on My Staging Test Server.
Wipes and dates
When does My Staging Test Server wipe, and how often?
Too few wipes are on record for My Staging Test Server to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 12 days 7 hours ago, and that is the one in play.
On My Staging Test Server, what happens on wipe day?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 46 hours in.
Lists and tags
Which lists on Rust Data hold My Staging Test Server, and which filters?
These Rust Data lists include My Staging Test Server: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on My Staging Test Server hold?
These tags are published by My Staging Test Server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168330 (Build): Build number: 168330; 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): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to My Staging Test Server?
In Rust, F1 opens the console: type client.connect 31.58.178.2:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.