Working its way up from the back of the class: #15,498 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
32/ 100
F
Lost ground: down 5,467 places this week. A strong wipe could turn it round.
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.
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 21 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 68% of all ranked servers, and #191 of the solo servers (top 85%). 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. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 41.109.203.225:28015.
How reliable is DZ Raiders - 2x Weekly, and is it up?
You cannot join now: DZ Raiders - 2x Weekly is offline, last seen 37 days 13 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 21 September 2026.
On what Rust version does DZ Raiders - 2x Weekly sit?
You will find DZ Raiders - 2x Weekly on Rust network protocol 2633 and build 164530, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does DZ Raiders - 2x Weekly reset?
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. It has been running its current world for 41 days 13 hours.
Population
Where does DZ Raiders - 2x Weekly place in the wider field of Rust servers?
Over the last seven days, DZ Raiders - 2x Weekly has #15,498 for player hours, in the top 68% of all ranked servers. It comes #191 among servers in the solo group.
Is DZ Raiders - 2x Weekly a busy server?
It has been 37 days 13 hours since DZ Raiders - 2x Weekly was last seen, and it is offline right now.
Tags
What do DZ Raiders - 2x Weekly's tags stand for?
gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): The server holds 50 slots; ts1 (Group limit): Teams cap out at 1; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): Build number: 164530; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags DZ Raiders - 2x Weekly publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does DZ Raiders - 2x Weekly appear in the Rust Server Score lists and filters?
These Rust Server Score lists count DZ Raiders - 2x Weekly among them: 2x Rust servers, graded, Modded Rust servers, graded and Solo Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo; Gather rate: 2x.
Server rules
What settings and rules apply on DZ Raiders - 2x Weekly?
DZ Raiders - 2x Weekly sets gather at 2x, as its name suggests. This is a solo-only server, so teams cannot form. survival is the mode 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. The plugin count runs to Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on DZ Raiders - 2x Weekly?
DZ Raiders - 2x Weekly runs a game-generated procedural map at size 3,500, seed 476416543. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto DZ Raiders - 2x Weekly?
To connect, start Rust, press F1, and type client.connect 41.109.203.225:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is 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 limitTeams cap out at 1.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^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. Even marks across the subjects, from F to F.