Rust Server TrendsSeismic network · station log
Recording Stations11,844 Players83,167 Active3,755 Wipes · 3 h280 48 h

Station XX-16967 · no signal

DZ Raiders - 2x Weekly

Offline 105.103.191.110:28015 checked 32d ago

2x solo
Connect
Players now
0/ 50
0% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#16,967
top 72%
Last wipe
35d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-16967 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
0of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k27 Sep28 Sep30 Sep1 Oct3 Oct4 Oct

Top 72% of all ranked servers, and #206 of the solo servers (top 92%). Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
Dusk till Dawn SOLO | 2x | 5% Upkeep | No BP Wipe NA · solo · 2x · monthly · 2 on average
0/ 100
Magic Rust #1 — Modded 2x (Только SOLO) | Pyccкий EU · solo · 2x · weekly · 72 on average
24/ 100
WARBANDITS.GG EU 2X SOLO ONLY|Loot+|X2 JUST WIPED EU · solo · 2x · weekly · 64 on average
44/ 200
Blood Rust - Purple [solo, x2] EU · solo · 2x · weekly · 54 on average
53/ 200
WARBANDITS.GG 2X SOLO ONLY|Loot+|X2 JUST WIPED NA · solo · 2x · weekly · 47 on average
22/ 200
Magic Rust #16 — Modded 2x (Toлькo SOLO) | Pyccкий EU · solo · 2x · weekly · 43 on average
63/ 100
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on DZ Raiders - 2x Weekly?

DZ Raiders - 2x Weekly runs a procedural map of size 3,500 with seed 1192285343, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on DZ Raiders - 2x Weekly?

Its name points to a gather rate of 2x on DZ Raiders - 2x Weekly. This is a solo-only server, with no teams. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. The server browser lists it under Community, as a community server. The server has VAC on, Valve's anti-cheat.

Player counts

How many players are recorded on DZ Raiders - 2x Weekly right now?

No players are recorded on DZ Raiders - 2x Weekly at this moment; it is offline, and the last sighting was 32 days 4 hours ago.

How does DZ Raiders - 2x Weekly rank against other Rust servers?

The last seven days of player hours place DZ Raiders - 2x Weekly at #16,967, in the top 72% of all ranked servers. It sits at #206 among solo servers.

Server details

How reliably does DZ Raiders - 2x Weekly stay online?

No contact with DZ Raiders - 2x Weekly right now, and the last recorded contact was 32 days 4 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 27 September 2026 is when Rust Server Trends first recorded it.

Which region does DZ Raiders - 2x Weekly run from?

No region is published by DZ Raiders - 2x Weekly. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 105.103.191.110:28015 is the address it uses.

Which Rust version is DZ Raiders - 2x Weekly running?

On Linux, DZ Raiders - 2x Weekly runs Rust network protocol 2633 and build 165217. The protocol must match for you to join, and Steam takes care of updating it.

Wipe day

On what timetable does DZ Raiders - 2x Weekly run its wipes?

Too few wipes of DZ Raiders - 2x Weekly are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 35 days.

Lists and tags

What do the server tags on DZ Raiders - 2x Weekly mean?

These are the tags DZ Raiders - 2x Weekly publishes for the browser to read: gmvanilla (Game mode): Survival in vanilla mode; mp50 (Max players): Slots: 50; ts1 (Group limit): Each team can hold up to 1; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does DZ Raiders - 2x Weekly appear?

The Rust Server Trends lists that take in DZ Raiders - 2x Weekly are: 2x Rust servers, listed live, Rust community servers without the side modes and Solo Rust servers. 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.

Join the server

What steps get you onto DZ Raiders - 2x Weekly?

You can connect by pressing F1 in Rust and typing client.connect 105.103.191.110:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. For the website, go to https://discord.com/invite/DmEGGSaxN9.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmvanilla,cs165217,ts1

Game

gmvanilla
Game mode Survival in vanilla mode.
mp50
Max players Slots: 50.
ts1
Group limit Each team can hold up to 1.
v2633
Protocol Your game needs to be on protocol 2633 to join.
cs165217
Build The game build is 165217.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.