Working its way up from the back of the class: #13,235 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
33/ 100
F
Lost ground: down 4,520 places this week. A strong wipe could turn it round.
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.
AveragePeakWipe
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 61% 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
Where in the world is ZombieSurvival Private Test?
You'll find no region listed by ZombieSurvival Private Test. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 172.59.129.169:28015 is the address to use.
How dependable is ZombieSurvival Private Test, and is it online at the moment?
You cannot join now: ZombieSurvival Private Test is offline, last seen 15 days 17 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 12 October 2026.
What Rust version is ZombieSurvival Private Test on?
Rust network protocol 2634 and build 167398 on Windows is what ZombieSurvival Private Test runs. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does ZombieSurvival Private Test wipe its map?
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 19 hours.
Player count
Where does ZombieSurvival Private Test sit among Rust servers?
In the top 61% of all ranked servers, ZombieSurvival Private Test sits at #13,235 for player hours over the last seven days.
How many players does ZombieSurvival Private Test usually have?
The last sighting of ZombieSurvival Private Test was 15 days 17 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on ZombieSurvival Private Test?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp30 (Max players): Its slot count is 30; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167398 (Build): This runs on build 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^p (PvE): Players do not fight one another here; the world is the danger; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags ZombieSurvival Private Test publishes, and the game's server browser reads them. 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 ZombieSurvival Private Test?
Rust Server Score lists that include ZombieSurvival Private Test: Modded Rust servers, graded, Rust PvE servers, graded and Rust zombie servers, graded. You can find it under these server-list filters: 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?
You will find no gather rate in the name of ZombieSurvival Private Test. The group limit stays at the game's default of 8 players. pve is the mode here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. Carbon plugins are running on it. 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.
Connecting
How should you connect to ZombieSurvival Private Test?
To connect, start Rust, press F1, and type client.connect 172.59.129.169: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 modeThis one runs plain Rust survival, with nothing altered.
mp30
Max playersIts slot count is 30.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Gameplay
^p
PvEPlayers do not fight one another here; the world is the danger.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is 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.