Working its way up from the back of the class: #15,490 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
38/ 100
F
Slipped a little: down 3,804 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.
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 17 Sep. 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, and #191 of the solo servers (top 86%). 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
No region is published for DZ Raiders - 2x Weekly. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 41.109.217.165:28015.
How reliable is DZ Raiders - 2x Weekly, and is it up?
At this moment, DZ Raiders - 2x Weekly is offline; the last time it was seen was 40 days 23 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 17 September 2026, Rust Server Score saw it for the first time.
Which Rust version is DZ Raiders - 2x Weekly running?
The server DZ Raiders - 2x Weekly is on Rust network protocol 2633 and build 164530 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does DZ Raiders - 2x Weekly wipe its map?
The record holds too few of DZ Raiders - 2x Weekly's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. 41 days 4 hours have passed since this world was made.
Player count
What position does DZ Raiders - 2x Weekly hold in the rankings?
Over the last seven days, DZ Raiders - 2x Weekly has #15,490 for player hours, in the top 69% of all ranked servers. In the solo group, it ranks #191.
What does the population on DZ Raiders - 2x Weekly look like?
DZ Raiders - 2x Weekly is offline at the moment; the last time it was seen was 40 days 23 hours ago.
Tags and filters
How should you read the tags on DZ Raiders - 2x Weekly?
You'll see DZ Raiders - 2x Weekly tagged with gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): The server holds 50 slots; ts1 (Group limit): A team can hold 1 players at most; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): Build number: 164530; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded 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 DZ Raiders - 2x Weekly appear in the Rust Server Score lists and filters?
Rust Server Score lists that include DZ Raiders - 2x Weekly: 2x Rust servers, graded, Modded Rust servers, graded and Solo Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo; Gather rate: 2x.
Rules and settings
How is DZ Raiders - 2x Weekly set up, and what rules does it keep?
Going by its name, DZ Raiders - 2x Weekly runs 2x gather. This is a solo-only server, so teams cannot form. You get survival here, 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. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
DZ Raiders - 2x Weekly runs which map?
A procedural map of size 3,500 and seed 476416543, generated by the game, is what DZ Raiders - 2x Weekly runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How do you get onto DZ Raiders - 2x Weekly?
To connect, start Rust, press F1, and type client.connect 41.109.217.165:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://discord.com/invite/DmEGGSaxN9.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmvanilla,cs164530,ts1,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp50
Max playersThe server holds 50 slots.
ts1
Group limitA team can hold 1 players at most.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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.