Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO X SRV11,640online PAX32,367playing OCC2,784with players WIPED 3H73
MODModded traffic
Callsign

DUS9442=

dust2v2.1_server

Online 212.22.93.48:28014 checked 6m ago

monthly wipes moddedoxide
Clearance · join
Players now 0/ 100 0% full
7-day average0peak 2
Rank#9,442top 42%
Last wipe13h agomonthly schedule
Next wipe7d 14hThu 5 Nov, 19:00 UTC FW
Track history

Players

AveragePeakWipe
00.511.5213:0016:0019:0022:0000:0003:00Wiped Wed 28 Oct, 13:38 UTCWIPE

Hourly average and peak, UTC.

Server performance

Server fpsWipe
010020030040013:0016:0019:0022:0000:0003:00Wiped Wed 28 Oct, 13:38 UTCWIPE

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
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 42% of all ranked servers. Ranked on player hours over the last seven days.

Flight plan

Wipe schedule

force wipes only
ETD · next wipe

Next wipe Thursday 5 November, 19:00 UTC, in 7d 14h.

The force wipe · high confidence

usual gap5.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak4players, last three wipes
crowd held50%else halves by day 3.5

Coming wipes

  1. 7d 14hThu 5 Nov, 19:00 UTCFW
  2. 35d 14hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

Sat 10 OctSat 3 OctThu 1 Oct
02468+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 3, 5 hours in, with 1 in the queue.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 13:38 UTC15h ago – – running 0
Sat 10 Oct, 11:11 UTC18d ago 3+1 queue halved by day 3 18.1 days 0
Sat 3 Oct, 18:37 UTC25d ago 5 halved by day 4 6.7 days 0
Thu 1 Oct, 18:23 UTC FW27d ago 5 held half 2 days 0
Sun 27 Sep, 16:36 UTC31d ago 3 held half 4.1 days 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign RUS021EU · groups of 16+ · monthly · 93 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10
    Players 13/700
  2. 02MOD
    Callsign RUS021EU · groups of 16+ · monthly · 84 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10
    Players 3/1000
  3. 03MOD
    Callsign RUS029EU · groups of 16+ · monthly · 78 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10
    Players 46/700
  4. 04MOD
    Callsign RUS025EU · groups of 16+ · monthly · 70 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10
    Players 34/1000
  5. 05MOD
    Callsign RUS017EU · groups of 16+ · monthly · 66 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10
    Players 4/1000
  6. 06MOD
    Callsign RUS029EU · groups of 16+ · monthly · 64 on average 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10
    Players 49/1000
ATIS · this server

Quick answers

From the figures on this page.

Filters

Which lists and filters on Rust Tracker show dust2v2.1_server?

On Rust Tracker, dust2v2.1_server sits in these lists: Modded servers, tracked live. On the server list, these filters bring it up: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 24 hours.

Which tags does dust2v2.1_server carry, and what do they mean?

The game's server browser reads these tags from dust2v2.1_server: gmrust (Game mode): Rust survival, standard mode; mp100 (Max players): Slots: 100; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): Region code: not set; ^m (Monthly): Follows Facepunch's force wipe: one wipe per month; ^o (Oxide): Plugin framework confirmed: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; listed under Modded. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.

Wipe Times

What happens on dust2v2.1_server on wipe day?

The average peak across recent wipes: 4 players. This wipe, 5 hours in was the peak: 1 were holding in the queue. The crowd stayed above half the peak until the next wipe in 50% of recent wipes. In the other cases, half the peak was lost by day 3.5.

Which wipe times are confirmed for dust2v2.1_server?

Once a month is the wipe rate at dust2v2.1_server, on the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. Its world went live 13 hours. Tags list a monthly wipe schedule.

Server Details

What is the uptime on dust2v2.1_server, and is it online?

dust2v2.1_server is up and online at this moment. By its own uptime figure, the last restart was roughly 7 hours ago. 10 of 168 hours up over the last 7 full days: 6% uptime. The first sighting by Rust Tracker was 20 September 2026.

Which Rust version is confirmed on dust2v2.1_server?

Rust network protocol 2635 and build 168909 on Windows is what dust2v2.1_server runs. Steam updates it for you; your game must share the protocol to join.

How smoothly does dust2v2.1_server run?

For the last 48 hours it averaged 198 server fps; the floor was 66. Peak entity count: 46,294, covering buildings, deployables and all else in the world. Peak memory use: 1,572 MB. A climbing entity count and low fps are what register as lag for players.

What location is dust2v2.1_server hosted in?

No region is published by dust2v2.1_server. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. You connect at 212.22.93.48:28014.

Player Count

What is the player count on dust2v2.1_server?

dust2v2.1_server is at 0 players, capacity 100. Peak of 2 in the last seven days, average 0 players. Busiest window in 48 hours: 20:00 UTC, 2 players on average.

Where does dust2v2.1_server sit in the server rankings?

Top 42% of all ranked servers, and #9,442 on seven-day player hours: dust2v2.1_server.

Settings

Which settings and rules are confirmed on dust2v2.1_server?

No gather rate appears in dust2v2.1_server's name. The game's default applies: groups can have up to 8 players. It runs survival, gather, build and raid: the standard game. Players can raid and fight each other here. The server browser lists it under Modded, where plugins or settings change the game. Oxide plugins run on it. VAC is on, Valve's anti-cheat.

What map is dust2v2.1_server on?

The map on dust2v2.1_server is procedural, size 2,000, seed 1605290779, generated by the game. Size and seed match, so the map is the same: view it on RustMaps from this page. Its map goes by the name Custom Map.

Connect

How do you get onto dust2v2.1_server?

To connect: start Rust, press F1, enter client.connect 212.22.93.48:28014 in the console. Or use Launch Rust on this page to open Rust through Steam and join.

Transponder codes

Server tags

What each one means.

Published as mp100,ptrak,$r?,v2635,^m,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Rust survival, standard mode.
mp100
Max players Slots: 100.
ts8
Group limit Teams cap at 8; this is the game default.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking RakNet is the network layer — the game's standard.
$r?
Region code Region code: not set.

Wipe schedule

^m
Monthly Follows Facepunch's force wipe: one wipe per month.

Mods and access

^o
Oxide Plugin framework confirmed: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; listed 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.