Working its way up from the back of the class: #16,003 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
52/ 100
D
Moving up: up 699 places this week.
A term to build on.
Strongest in momentum (D); standing 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.
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.
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 2 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers, and #201 of the solo servers (top 90%). Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 4 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 3 Oct, 04:19 UTC24d ago
1
–
running
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 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.108.201.209: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 24 days 17 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 2 October 2026, Rust Server Score saw it for the first time.
What Rust version is DZ Raiders - 2x Weekly on?
The server DZ Raiders - 2x Weekly is on Rust network protocol 2634 and build 166652 under Linux. To join, your game must use the same protocol; Steam handles the update.
Resets
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. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 24 days 23 hours have passed since this world was made.
What happens on DZ Raiders - 2x Weekly when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 4 hours after it began.
Player count
What position does DZ Raiders - 2x Weekly hold in the rankings?
Over the last seven days, DZ Raiders - 2x Weekly has #16,003 for player hours, in the top 70% of all ranked servers. It comes #201 among servers in the solo group.
How many players does DZ Raiders - 2x Weekly usually have?
It has been 24 days 17 hours since DZ Raiders - 2x Weekly was last seen, and it is offline right now.
Lists and filters
What do DZ Raiders - 2x Weekly's tags stand for?
You'll see DZ Raiders - 2x Weekly tagged with gmvanilla (Game mode): This is vanilla survival; mp50 (Max players): Its slot count is 50; ts1 (Group limit): Teams cap out at 1; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server 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 - 2x Weekly?
Rust Server Score lists that include DZ Raiders - 2x Weekly: 2x Rust servers, graded, Best community servers, graded and Solo Rust servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: Solo; Gather rate: 2x.
Rules and settings
Which rules does DZ Raiders - 2x Weekly enforce, and what are its settings?
DZ Raiders - 2x Weekly sets gather at 2x, as its name suggests. No teams are allowed: it is solo only. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. You are covered by VAC, Valve's anti-cheat.
DZ Raiders - 2x Weekly runs which map?
A procedural map of size 3,500 and seed 1854909225, generated by the game, is what DZ Raiders - 2x Weekly runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to DZ Raiders - 2x Weekly?
To connect, start Rust, press F1, and type client.connect 41.108.201.209: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?,v2634,gmvanilla,cs166652,ts1
Game
gmvanilla
Game modeThis is vanilla survival.
mp50
Max playersIts slot count is 50.
ts1
Group limitTeams cap out at 1.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
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 momentum (D); standing is the one to work on (F).