Offline 195.201.109.240:28035 checked 34d ago
Sperrzone Staging Test
Connect
srv = rust.server("195.201.109.240:28037")
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, measured since 24 Sep. 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 71% 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 2, 2 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 24 Sep, 06:52 UTC34d ago | 2 | 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 1
- map
- Procedural Map
- size
- 3000
- seed
- 1
Server
srv.info()- address
- 195.201.109.240:28035
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 07:39 UTC
- hostname
- –
- first seen
- 24 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 · 152 on average | 43/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 48/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 17/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 1/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 4/1000 |
Quick answers
From the figures on this page.
Population data
What position does Sperrzone Staging Test take in the server rankings?
Rank #15,709 on seven-day player hours for Sperrzone Staging Test, within the top 71% of all ranked servers.
How full does Sperrzone Staging Test run?
Sperrzone Staging Test returns no live count at this refresh, having last been seen 34 days 16 hours ago.
Server data
Which Rust version is Sperrzone Staging Test on?
The build is Rust network protocol 2633 and build 165590 on Linux, run by Sperrzone Staging Test. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Sperrzone Staging Test, and is it online now?
Offline now for Sperrzone Staging Test, last seen 34 days 16 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 24 September 2026.
Which location does Sperrzone Staging Test run from?
For Sperrzone Staging Test, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 195.201.109.240:28035.
Settings and map
Which rules apply on Sperrzone Staging Test, and what settings?
You will not find a gather rate in the string Sperrzone Staging Test. No custom cap; the default of 8 players per group stands. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Sperrzone Staging Test selected?
Sperrzone Staging Test runs a procedural map of size 3,000 with seed 1, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
On what schedule does Sperrzone Staging Test wipe?
A rhythm cannot be read from the wipes of Sperrzone 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. The world it runs now was generated 34 days 21 hours ago.
On Sperrzone Staging Test, what happens on wipe day?
Recent wipes averaged 2 players at their peak. 2 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which Rust Data filters and lists contain Sperrzone Staging Test?
On Rust Data, Sperrzone Staging Test appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Which meanings do the tags on Sperrzone Staging Test hold?
Read by the game's server browser, the tags Sperrzone Staging Test publishes are: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs165590 (Build): Build number: 165590; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. 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
What is the way into Sperrzone Staging Test?
Enter client.connect 195.201.109.240:28035 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. https://discord.com/invite/sperrzone is the website recorded for it.
