Working its way up from the back of the class: #12,182 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
50/ 100
D
Holding steady: up 88 places this week.
A term to build on.
Even marks across the subjects, from D to D.
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.
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 53% 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
STALKER_Chernobyl_Zone leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 212.32.208.22:28015.
How dependable is STALKER_Chernobyl_Zone, and is it online at the moment?
At this moment, STALKER_Chernobyl_Zone is offline; the last time it was seen was 37 days 14 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 22 September 2026, Rust Server Score saw it for the first time.
Which Rust version is STALKER_Chernobyl_Zone running?
You will find STALKER_Chernobyl_Zone on Rust network protocol 2633 and build 165217, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
When does STALKER_Chernobyl_Zone wipe, and how often?
STALKER_Chernobyl_Zone has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 37 days 15 hours.
Population
Where does STALKER_Chernobyl_Zone sit among Rust servers?
Over the last seven days, STALKER_Chernobyl_Zone has #12,182 for player hours, in the top 53% of all ranked servers.
Is STALKER_Chernobyl_Zone a busy server?
It has been 37 days 14 hours since STALKER_Chernobyl_Zone was last seen, and it is offline right now.
Tags and filters
How should you read the tags on STALKER_Chernobyl_Zone?
You'll see STALKER_Chernobyl_Zone tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): Its slot count is 5; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): This runs on build 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. 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 STALKER_Chernobyl_Zone appear in the Rust Server Score lists and filters?
These Rust Server Score lists count STALKER_Chernobyl_Zone among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
Which rules does STALKER_Chernobyl_Zone enforce, and what are its settings?
Nothing in the name of STALKER_Chernobyl_Zone states a 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. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on STALKER_Chernobyl_Zone?
STALKER_Chernobyl_Zone runs a procedural map, which the game generates.
How to join
What is the way to join STALKER_Chernobyl_Zone?
To connect, start Rust, press F1, and type client.connect 212.32.208.22:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max playersIts slot count is 5.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set 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. Even marks across the subjects, from D to D.