A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,339 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
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
49/ 100
D
Slipped a little: down 166 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A+); population is the one to work on (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
Every five minutes, from the Steam server list.
AveragePeak
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
12 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
···W···
···WWWW
WWWW···
···W···
···W···
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h.
The force wipe · high confidence
usual gap1 daysbetween real wipes
on rhythm75%of its recent wipes
wipe-day peak0players, last three wipes
Coming wipes
7d 20hThu 5 Nov, 19:00 UTCFW
21d 14hThu 19 Nov, 13:25 UTC
35d 20hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 22 OctThu 15 OctThu 8 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 22 Oct, 13:25 UTC6d ago
0
–
running
0
Thu 15 Oct, 13:26 UTC13d ago
0
–
7 days
0
Thu 8 Oct, 13:26 UTC20d ago
0
–
7 days
0
Wed 7 Oct, 13:26 UTC21d ago
0
–
1 days
0
Tue 6 Oct, 13:23 UTC22d ago
0
–
1 days
0
Mon 5 Oct, 13:29 UTC23d ago
0
–
1 days
0
Sun 4 Oct, 13:22 UTC24d ago
0
–
1 days
0
Sat 3 Oct, 13:25 UTC25d ago
1
–
1 days
0
Fri 2 Oct, 13:26 UTC26d ago
1
–
1 days
0
Thu 1 Oct, 13:33 UTC27d ago
0
–
1 days
0
Thu 24 Sep, 13:22 UTC34d ago
0
–
7 days
0
Thu 17 Sep, 13:28 UTC41d ago
0
–
7 days
0
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
No region is published for Deathrive Rustocolypse. Rust Server Score takes the server's word for its location and does not trace the hardware. 68.168.20.252:28015 is the address to use.
Is Deathrive Rustocolypse up, and how steady is its uptime?
You can join now: Deathrive Rustocolypse is online. It was up 164 of 168 hours over the last 7 full days, which is 98% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Which Rust version is Deathrive Rustocolypse running?
You will find Deathrive Rustocolypse on Rust network protocol 2634 and build 166652, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does Deathrive Rustocolypse reset?
Its tag sets the prediction, as the record holds too few of Deathrive Rustocolypse's wipes to confirm its schedule. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 6 days 9 hours. Its tags say it wipes every two weeks.
What happens on Deathrive Rustocolypse when wipe day arrives?
The average peak on its recent wipes was 0 players. The crowd on the latest wipe was largest 0 hours after it began.
Player count
Where does Deathrive Rustocolypse sit among Rust servers?
In the top 69% of all ranked servers, Deathrive Rustocolypse sits at #15,339 for player hours over the last seven days.
Is Deathrive Rustocolypse a busy server?
With 100 slots available, Deathrive Rustocolypse currently has 0 players. A seven-day average of 0 players applies here.
Tags and filters
How should you read the tags on Deathrive Rustocolypse?
You'll see Deathrive Rustocolypse tagged with gmvanilla (Game mode): This is vanilla survival; mp100 (Max players): Its slot count is 100; 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; cs166652 (Build): This runs on build 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^b (Biweekly): Every two weeks it wipes; ^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): Plugin framework: Carbon in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show Deathrive Rustocolypse?
These Rust Server Score lists count Deathrive Rustocolypse among them: Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last week.
Server rules
What settings and rules apply on Deathrive Rustocolypse?
Nothing in the name of Deathrive Rustocolypse states a gather rate. The default of 8 players applies as the group cap. You get pve here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
Deathrive Rustocolypse runs which map?
A procedural map, generated by the game, is what Deathrive Rustocolypse runs.
Connecting
What is the way to join Deathrive Rustocolypse?
To connect, start Rust, press F1, and type client.connect 68.168.20.252:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2634,^z,^y,^b,^p,gmvanilla,cs166652,ts8
Game
gmvanilla
Game modeThis is vanilla survival.
mp100
Max playersIts slot count is 100.
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.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
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
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. Strongest in uptime (A+); population is the one to work on (F).