Working its way up from the back of the class: #13,887 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
37/ 100
F
Slipped a little: down 3,671 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
AveragePeak
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.
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.
This server has not answered a direct query in the last 60 days.
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.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 63% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Wiped
Peak
Crowd
Lasted
Players before
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is ZombieSurvival Private Test based in?
You'll find no region listed by ZombieSurvival Private Test. Rust Server Score takes the server's word for its location and does not trace the hardware. 172.59.128.1:28015 is the address to use.
Is ZombieSurvival Private Test up, and how steady is its uptime?
At this moment, ZombieSurvival Private Test is offline; the last time it was seen was 9 days 19 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 15 October 2026, Rust Server Score saw it for the first time.
On what Rust version does ZombieSurvival Private Test sit?
Rust network protocol 2634 and build 167398 on Windows is what ZombieSurvival Private Test runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does ZombieSurvival Private Test wipe, and how often?
The record holds too few of ZombieSurvival Private Test's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 16 days 12 hours.
Population
Where does ZombieSurvival Private Test place in the wider field of Rust servers?
Over the last seven days, ZombieSurvival Private Test has #13,887 for player hours, in the top 63% of all ranked servers.
How many players does ZombieSurvival Private Test usually have?
It has been 9 days 19 hours since ZombieSurvival Private Test was last seen, and it is offline right now.
Lists and filters
How should you read the tags on ZombieSurvival Private Test?
gmrust (Game mode): Survival in the standard Rust style; mp30 (Max players): The server holds 30 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167398 (Build): The game build is 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^p (PvE): This is player against world: players do not fight each other; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon are the tags ZombieSurvival Private Test publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does ZombieSurvival Private Test appear in the Rust Server Score lists and filters?
These Rust Server Score lists count ZombieSurvival Private Test among them: Modded Rust servers, graded, Rust PvE servers, graded and Rust zombie servers, graded. It shows under the following filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
Which rules does ZombieSurvival Private Test enforce, and what are its settings?
Nothing in the name of ZombieSurvival Private Test states a gather rate. With no change from the game default, groups take up to 8 players. It runs pve, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. The server runs Valve's anti-cheat, VAC.
Can you tell me which map ZombieSurvival Private Test uses?
ZombieSurvival Private Test runs a procedural map, which the game generates.
Getting in
How should you connect to ZombieSurvival Private Test?
To connect, start Rust, press F1, and type client.connect 172.59.128.1:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp30,ptrak,$r?,v2634,^z,^y,^p,gmrust,cs167398,ts8
Game
gmrust
Game modeSurvival in the standard Rust style.
mp30
Max playersThe server holds 30 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167398
BuildThe game build is 167398.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonPlugin framework: Carbon.
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. Even marks across the subjects, from F to F.