Working its way up from the back of the class: #15,491 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
34/ 100
F
Lost ground: down 5,072 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 20 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 #192 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. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 105.111.192.14:28015.
How dependable is DZ Raiders - 2x Weekly, and is it online at the moment?
You cannot join now: DZ Raiders - 2x Weekly is offline, last seen 38 days 7 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
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. To join, your game must use the same protocol; Steam handles the update.
Resets
How frequently does DZ Raiders - 2x Weekly wipe its map?
DZ Raiders - 2x Weekly has not had enough wipes recorded to reveal 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 12 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,491 for player hours, in the top 69% of all ranked servers. It comes #192 among servers in the solo group.
How many players does DZ Raiders - 2x Weekly usually have?
It has been 38 days 7 hours since DZ Raiders - 2x Weekly was last seen, and it is offline right now.
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): Survival, vanilla style; mp50 (Max players): The server holds 50 slots; ts1 (Group limit): Teams cap out at 1; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs164530 (Build): This runs on build 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. 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?
Rust Server Score lists that include DZ Raiders - 2x Weekly: 2x Rust servers, graded, Modded Rust servers, graded and Solo Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: Solo; Gather rate: 2x.
Server rules
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. Solo play only, with no teams permitted. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map DZ Raiders - 2x Weekly uses?
The game generates the procedural map on DZ Raiders - 2x Weekly at size 3,500 with seed 476416543. 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?
Enter client.connect 105.111.192.14: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,cs164530,ts1,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp50
Max playersThe server holds 50 slots.
ts1
Group limitTeams cap out at 1.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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.