Offline 213.193.252.202:28015 checked 27d ago
Local Staging Test
Connect
srv = rust.server("213.193.252.202: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
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 | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 213.193.252.202:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 30 Sep 2026, 21:17 UTC
- hostname
- –
- first seen
- 1 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 · 151 on average | 59/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 122/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 93/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 31/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
Quick answers
From the figures on this page.
Population data
What position does Local Staging Test take in the server rankings?
Player hours over seven days put Local Staging Test at #16,608, in the top 70% of the ranked set.
How many players does Local Staging Test hold at once?
The current row shows Local Staging Test offline; the last response was 27 days 20 hours ago.
Server data
What is the Rust version on Local Staging Test?
The build is Rust network protocol 2634 and build 166427 on Windows, run by Local Staging Test. Joining needs the same protocol on your game; Steam handles the update.
Is Local Staging Test up, and what does its uptime show?
The latest sample has Local Staging Test offline, with a last sighting 27 days 20 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 1 October 2026.
In which location is Local Staging Test hosted?
For Local Staging Test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 213.193.252.202:28015.
Settings and map
Which rules apply on Local Staging Test, and what settings?
You will not find a gather rate in the string Local Staging Test. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on Local Staging Test?
Local Staging Test runs a procedural map, which the game generates.
Wipe data
When does Local Staging Test wipe, and how often?
A rhythm cannot be read from the wipes of Local Staging Test on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 28 days 9 hours ago.
Tags and filters
Which Rust Data filters and lists contain Local Staging Test?
These Rust Data lists include Local Staging Test: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on Local Staging Test?
These tags are published by Local Staging Test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166427 (Build): Build number: 166427; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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.
Connecting
How can I connect to Local Staging Test?
Enter client.connect 213.193.252.202:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.