Offline 14.1.95.213:28015 checked 27d ago
Local Staging Map Test
Connect
srv = rust.server("14.1.95.213: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 65% 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 1 Oct, 12:21 UTC27d ago | 1 | NaN | running | 1 |
| 1 | Wed 30 Sep, 12:23 UTC28d ago | 1 | NaN | 1 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 14.1.95.213:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 12:21 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 · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Population
How does Local Staging Map Test compare in the rankings?
Over the last seven days Local Staging Map Test sits at #15,490 on player hours, in the top 65% of ranked servers.
What population does Local Staging Map Test carry?
Local Staging Map Test returns no live count at this refresh, having last been seen 27 days 7 hours ago.
About the server
What is the Rust version on Local Staging Map Test?
Rust network protocol 2634 and build 166472 on Windows is what Local Staging Map Test runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Local Staging Map Test, and is it online now?
The latest sample has Local Staging Map Test offline, with a last sighting 27 days 7 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 30 September 2026.
Where does Local Staging Map Test sit?
There is no region published for Local Staging Map Test. Rust Data does not look up where the machine stands; it shows where a server says it is. 14.1.95.213:28015 is its address.
Settings and map
What rules and settings are recorded for Local Staging Map Test?
No gather rate appears in the name: Local Staging Map Test. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. VAC is running: Valve's anti-cheat is on.
Wipes and dates
When does Local Staging Map Test wipe, and on what schedule?
The record for Local Staging Map Test holds too few wipes to show a 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 27 days 7 hours ago.
What is wipe day on Local Staging Map Test like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Where does Local Staging Map Test appear among Rust Data lists and filters?
These Rust Data lists include Local Staging Map Test: 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.
How should you read the server tags on Local Staging Map Test?
These tags are published by Local Staging Map Test and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166472 (Build): Recorded game build: 166472; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): Plugin framework: Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into Local Staging Map Test?
In Rust, F1 opens the console: type client.connect 14.1.95.213:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.