Working its way up from the back of the class: #16,897 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
47/ 100
D
Slipped a little: down 1,066 places this week. Nothing a good wipe can't fix.
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.
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 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 72% of all ranked servers, and #205 of the solo servers (top 92%). 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 reports the location a server gives; it does not check where the machine actually is. Find it at 41.109.81.143:28015.
Is DZ Raiders - 2x Weekly up, and how steady is its uptime?
At this moment, DZ Raiders - 2x Weekly is offline; the last time it was seen was 32 days 21 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 26 September 2026.
On what Rust version does DZ Raiders - 2x Weekly sit?
Rust network protocol 2633 and build 165217 on Linux is what DZ Raiders - 2x Weekly runs. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does DZ Raiders - 2x Weekly reset?
DZ Raiders - 2x Weekly has not had enough wipes recorded to reveal its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 35 days 8 hours have passed since this world was made.
Population
Where does DZ Raiders - 2x Weekly sit among Rust servers?
In the top 72% of all ranked servers, DZ Raiders - 2x Weekly sits at #16,897 for player hours over the last seven days. It comes #205 among servers in the solo group.
What does the population on DZ Raiders - 2x Weekly look like?
The last sighting of DZ Raiders - 2x Weekly was 32 days 21 hours ago, and it is offline right now.
Tags and filters
What do DZ Raiders - 2x Weekly's tags stand for?
gmvanilla (Game mode): Survival, vanilla style; mp50 (Max players): 50 slots are available; ts1 (Group limit): No team may go above 1; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): This runs on build 165217; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set 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.
Which lists and filters on Rust Server Score show DZ Raiders - 2x Weekly?
These Rust Server Score lists count DZ Raiders - 2x Weekly among them: 2x Rust servers, graded, Best community servers, graded and Solo Rust servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: Solo; Gather rate: 2x.
Rules and settings
What settings and rules apply on DZ Raiders - 2x Weekly?
Going by its name, DZ Raiders - 2x Weekly runs 2x gather. Solo play only, with no teams permitted. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. You will see it in the Community section of the server browser, since it is a community server. The server runs Valve's anti-cheat, VAC.
Can you tell me which map DZ Raiders - 2x Weekly uses?
A procedural map of size 3,500 and seed 1192285343, 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.
How to join
How do you get onto DZ Raiders - 2x Weekly?
Enter client.connect 41.109.81.143: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/DmEGGSaxN9.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2633,gmvanilla,cs165217,ts1
Game
gmvanilla
Game modeSurvival, vanilla style.
mp50
Max players50 slots are available.
ts1
Group limitNo team may go above 1.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThis runs on build 165217.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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).