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
16/ 100
F
Lost ground: down 10,417 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum 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.
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
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 19 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 #192 of the solo servers (top 84%). 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
DZ Raiders - 2x Weekly leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 41.109.246.134: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 39 days 11 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 19 September 2026.
Which Rust version is DZ Raiders - 2x Weekly running?
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?
DZ Raiders - 2x Weekly has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 41 days 15 hours.
Population
What position does DZ Raiders - 2x Weekly hold in the rankings?
In the top 68% of all ranked servers, DZ Raiders - 2x Weekly sits at #15,498 for player hours over the last seven days. It comes #192 among servers in the solo group.
How many players does DZ Raiders - 2x Weekly usually have?
It has been 39 days 11 hours since DZ Raiders - 2x Weekly was last seen, and it is offline right now.
Tags
What is meant by the tags on DZ Raiders - 2x Weekly?
gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): 50 slots are available; ts1 (Group limit): No team may go above 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): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags DZ Raiders - 2x Weekly 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.
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.
Rules and settings
Which rules does DZ Raiders - 2x Weekly enforce, and what are its settings?
The name of DZ Raiders - 2x Weekly points to a 2x gather rate. Solo play only, with no teams permitted. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. 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 - 2x Weekly?
DZ Raiders - 2x Weekly runs a game-generated procedural map at size 3,500, seed 476416543. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to DZ Raiders - 2x Weekly?
To connect, start Rust, press F1, and type client.connect 41.109.246.134: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 modeSurvival, vanilla style.
mp50
Max players50 slots are available.
ts1
Group limitNo team may go above 1.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: 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. Strongest in standing (F); momentum is the one to work on (F).