Working its way up from the back of the class: #15,709 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
45/ 100
D
Slipped a little: down 1,662 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
Average fpsLowest fpsWipe
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
Average fpsLowest fpsWipe
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 71% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak2players, last three wipes
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
Wiped
Peak
Crowd
Lasted
Players before
Thu 24 Sep, 06:52 UTC35d ago
2
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Sperrzone Staging Test leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 195.201.109.240:28035.
How reliable is Sperrzone Staging Test, and is it up?
The server is down: Sperrzone Staging Test is offline now, with the last sighting 34 days 20 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 24 September 2026, Rust Server Score saw it for the first time.
What Rust version is Sperrzone Staging Test on?
The server Sperrzone Staging Test is on Rust network protocol 2633 and build 165590 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does Sperrzone Staging Test reset?
There are too few wipes on record for Sperrzone Staging Test to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 35 days 1 hours.
What happens on Sperrzone Staging Test when wipe day arrives?
Recent wipes have peaked at 2 players on average. 2 hours after the latest wipe began, the crowd hit its peak.
Player numbers
What position does Sperrzone Staging Test hold in the rankings?
In the top 71% of all ranked servers, Sperrzone Staging Test sits at #15,709 for player hours over the last seven days.
What does the population on Sperrzone Staging Test look like?
The last sighting of Sperrzone Staging Test was 34 days 20 hours ago, and it is offline right now.
Tags and filters
How should you read the tags on Sperrzone Staging Test?
The game's browser takes its cue from the tags Sperrzone Staging Test has set: gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): Its slot count is 1; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165590 (Build): The game build is 165590; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show Sperrzone Staging Test?
These Rust Server Score lists count Sperrzone Staging Test among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Rules and settings
How is Sperrzone Staging Test set up, and what rules does it keep?
The name of Sperrzone Staging Test gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
Sperrzone Staging Test runs which map?
The game generates the procedural map on Sperrzone Staging Test at size 3,000 with seed 1. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto Sperrzone Staging Test?
Enter client.connect 195.201.109.240:28035 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/sperrzone.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2633,gmrust,cs165590,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max playersIts slot count is 1.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165590
BuildThe game build is 165590.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon provides the plugin framework here.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).