Working its way up from the back of the class: #13,219 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
35/ 100
F
Slipped a little: down 4,008 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.
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 57% 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
Solo Zombie Survival leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 77.64.154.55:28015 is the address to use.
How reliable is Solo Zombie Survival, and is it up?
The server is down: Solo Zombie Survival is offline now, with the last sighting 35 days 3 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 20 September 2026.
Which Rust version is Solo Zombie Survival running?
Rust network protocol 2633 and build 164530 on Windows is what Solo Zombie Survival runs. Steam updates your game for you, but you need the same protocol to join.
Resets
When does Solo Zombie Survival wipe, and how often?
Solo Zombie Survival has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 38 days 2 hours have passed since this world was made.
Population
Where does Solo Zombie Survival place in the wider field of Rust servers?
Over the last seven days, Solo Zombie Survival has #13,219 for player hours, in the top 57% of all ranked servers.
How many players does Solo Zombie Survival usually have?
It has been 35 days 3 hours since Solo Zombie Survival was last seen, and it is offline right now.
Lists and filters
What do Solo Zombie Survival's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): 1 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): The game build is 164530; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags Solo Zombie Survival publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does Solo Zombie Survival appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Solo Zombie Survival: Modded Rust servers, graded and Rust zombie servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
Which rules does Solo Zombie Survival enforce, and what are its settings?
The name of Solo Zombie Survival gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Solo Zombie Survival uses?
The game generates a procedural map for Solo Zombie Survival.
Getting in
How should you connect to Solo Zombie Survival?
Enter client.connect 77.64.154.55:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2633,gmrust,cs164530,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max players1 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThe game build is 164530.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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.