Offline 2.31.115.187:28015 checked 7h ago
Staging Dev Server
Connect
srv = rust.server("2.31.115.187: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. 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 69% 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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 14:58 UTC9h ago | NaN | 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
3000 · seed 12345
- map
- Procedural Map
- size
- 3000
- seed
- 12345
Server
srv.info()- address
- 2.31.115.187:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Oct 2026, 16:11 UTC
- hostname
- –
- first seen
- 27 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 · 163 on average | 48/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 113 on average | 62/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 59/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 13/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 16/1000 |
Quick answers
From the figures on this page.
Population data
How does Staging Dev Server compare in the rankings?
Over the last seven days Staging Dev Server sits at #15,409 on player hours, in the top 69% of ranked servers.
What population does Staging Dev Server carry?
Staging Dev Server returns no live count at this refresh, having last been seen 7 hours ago. Over the last seven days it averaged 0 players.
Server facts
How smoothly does Staging Dev Server run?
Averaged over 48 hours: 254 server fps, never under 253. Buildings, deployables and all else in the world took the count as high as 44,000 entities. A high of 1,482 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.
What is the Rust version on Staging Dev Server?
The build is Rust network protocol 2635 and build 169364 on Linux, run by Staging Dev Server. Steam updates your game for you, but the protocol must match to join.
Is Staging Dev Server up, and what does its uptime show?
Staging Dev Server is offline at this refresh; the last response came 7 hours ago. The first row Rust Data holds for it is dated 27 October 2026.
Which location does Staging Dev Server run from?
For Staging Dev 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. You can reach it at 2.31.115.187:28015.
Rules, settings, map
Which rules apply on Staging Dev Server, and what settings?
No gather rate appears in the name: Staging Dev Server. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on Staging Dev Server?
Staging Dev Server runs a procedural map of size 3,000 with seed 12345, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
When does Staging Dev Server wipe, and on what schedule?
Too few wipes are on record for Staging Dev Server 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. A new world was started 7 hours ago, and that is the one in play.
Tags, lists
Which lists on Rust Data hold Staging Dev Server, and which filters?
On Rust Data, Staging Dev 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 24 hours.
How should you read the server tags on Staging Dev Server?
The game's server browser reads these tags from Staging Dev Server: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs169364 (Build): Build number: 169364; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
How can I connect to Staging Dev Server?
In Rust, F1 opens the console: type client.connect 2.31.115.187:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.