Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
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
You'll find no region listed by Apocalipse. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 200.52.30.231:28015.
How dependable is Apocalipse, and is it online at the moment?
The server is down: Apocalipse is offline now, with the last sighting 43 days 12 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
On what Rust version does Apocalipse sit?
You will find Apocalipse on Rust network protocol 2633 and build 163794, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does Apocalipse wipe its map?
Apocalipse 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 45 days 14 hours.
Population
Where does Apocalipse sit among Rust servers?
In the top – of all ranked servers, Apocalipse sits at #15,025 for player hours over the last seven days.
How many players does Apocalipse usually have?
Apocalipse is offline at the moment; the last time it was seen was 43 days 12 hours ago.
Tags
How should you read the tags on Apocalipse?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here are the tags Apocalipse 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.
Which Rust Server Score filters and lists feature Apocalipse?
Rust Server Score lists that include Apocalipse: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
What settings and rules apply on Apocalipse?
Nothing in the name of Apocalipse states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Apocalipse uses?
A procedural map, generated by the game, is what Apocalipse runs.
Connecting
How should you connect to Apocalipse?
To connect, start Rust, press F1, and type client.connect 200.52.30.231:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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.
Not enough figures yet to write a report. Check back after a few days on the list.