On the class lists: F (26), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 2
Rank#9,661top 43%
Last wipe6d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
57/ 100
C−
Working its way up from the back of the class: #9,661 on player hours.
Uptimehours on the list, last 48
19/ 100
F
Attendance needs work: on the list only 9 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 103 server fps on average.
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.
A term to build on.
Strongest in performance (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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 27 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 43% 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
Which region is DZ Raiders | Thursday Wipes based in?
No region is published for DZ Raiders | Thursday Wipes. Rust Server Score takes the server's word for its location and does not trace the hardware. 197.203.81.237:28015 is the address to use.
How dependable is DZ Raiders | Thursday Wipes, and is it online at the moment?
The server is down: DZ Raiders | Thursday Wipes is offline now, with the last sighting 29 hours ago. The uptime it reports puts the last restart at about 2 days ago. For the last 1 full day, it was up 1 of 24 hours, or 4% of the time. It was first seen by Rust Server Score on 27 October 2026.
Is DZ Raiders | Thursday Wipes smooth to play on?
It never fell below 96 server fps in the last 48 hours, averaging 103. Up to 68,075 entities were in the world, covering buildings, deployables and the rest. Up to 2,899 MB of memory was used. Players feel lag when fps drops and entities pile up.
What Rust version is DZ Raiders | Thursday Wipes on?
Rust network protocol 2635 and build 168909 on Linux is what DZ Raiders | Thursday Wipes runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does DZ Raiders | Thursday Wipes reset?
There are too few wipes on record for DZ Raiders | Thursday Wipes to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 6 days 15 hours have passed since this world was made.
Population
Where does DZ Raiders | Thursday Wipes place in the wider field of Rust servers?
Over the last seven days, DZ Raiders | Thursday Wipes has #9,661 for player hours, in the top 43% of all ranked servers.
What does the population on DZ Raiders | Thursday Wipes look like?
The last sighting of DZ Raiders | Thursday Wipes was 29 hours ago, and it is offline right now. It peaked at 2 and averaged 0 players over the last seven days. The busiest time in the last 48 hours was 18:00 UTC, with an average of 2 players.
Tags
What do DZ Raiders | Thursday Wipes's tags stand for?
You'll see DZ Raiders | Thursday Wipes tagged with gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. 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 Rust Server Score filters and lists feature DZ Raiders | Thursday Wipes?
Rust Server Score lists that include DZ Raiders | Thursday Wipes: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Map and rules
How is DZ Raiders | Thursday Wipes set up, and what rules does it keep?
Nothing in the name of DZ Raiders | Thursday Wipes states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on DZ Raiders | Thursday Wipes?
DZ Raiders | Thursday Wipes runs a game-generated procedural map at size 3,500, seed 101458828. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to DZ Raiders | Thursday Wipes?
Enter client.connect 197.203.81.237:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://discord.com/invite/mxCqpDRUub.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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. Strongest in performance (A+); population is the one to work on (F).