Rust Server Analytics 32,059 players11,620 servers
All servers
Drill-through Server detail

dust2v2.1_server

Online 212.22.93.48:28014 checked 13m ago

Drill-through
FilterServeris dust2v2.1_server
Attributes
monthly wipes moddedoxide
Last refreshed
Players now 0/ 100
7-day average 0 peak 2
Rank #9,443 top 42%
Last wipe 14h ago monthly schedule
Next wipe 7d 13h Thu 5 Nov, 19:00 UTC FW
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeakWipe
00.511.5213:0016:0020:0022:0001:0004:00Wiped Wed 28 Oct, 13:38 UTCWIPE

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
Server fpsWipe
010020030040013:0016:0020:0022:0001:0004: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.

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 13h. 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

InWhen, UTCKind
7d 13hThu 5 Nov, 19:00 UTCFW force wipe
35d 13hThu 3 Dec, 19:00 UTCFW force wipe

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 UTC16h 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average 18 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 4 / 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 79 on average 68 / 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 EU · groups of 16+ · monthly · 70 on average 43 / 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10 EU · groups of 16+ · monthly · 66 on average 4 / 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 EU · groups of 16+ · monthly · 64 on average 55 / 1000

Quick answers

from the figures on this page

Wipe data

On what cycle does dust2v2.1_server wipe?

Once a month dust2v2.1_server wipes, with the force wipe. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. 14 hours ago the current world was made. A monthly wipe schedule is published in its tags.

Wipe day on dust2v2.1_server: what should you expect?

The average busiest count over recent wipes is 4 players. 5 hours after the latest wipe the crowd peaked, with 1 more queued. The crowd stayed above half that peak until the next wipe in 50% of recent wipes. By day 3.5 it had fallen below half where the hold failed.

Server

In which region does dust2v2.1_server sit?

No region appears in what dust2v2.1_server publishes. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. 212.22.93.48:28014 is its address.

Which Rust version is dust2v2.1_server on?

Rust network protocol 2635 and build 168909 on Windows is the setup for dust2v2.1_server. Joining requires the same protocol on your game; Steam handles the update.

What uptime does dust2v2.1_server show, and is it up?

The current status of dust2v2.1_server is online. Its reported uptime indicates a restart roughly 8 hours ago. Uptime over the last full days (7) was 6%, or 10 of 168 hours. 20 September 2026 is when Rust Server Analytics first recorded it.

Does dust2v2.1_server perform well?

The 48-hour average was 200 server fps; the low was 66. Entity count reached 46,294, covering buildings, deployables and the rest of the world. At its highest, memory use was 1,572 MB. Lag, for players, means low fps alongside a growing entity count.

Tags

How should the tags on dust2v2.1_server be read?

Tags from dust2v2.1_server, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default team size of 8; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^m (Monthly): A monthly cycle, with Facepunch's force wipe as the reset; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): Plugins or settings change the game, so it sits under Modded. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

On Rust Server Analytics, which lists and filters feature dust2v2.1_server?

These Rust Server Analytics lists include dust2v2.1_server: Modded Rust servers: live data. These filters bring it up on the server list: 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.

Population

What position does dust2v2.1_server hold in the server rankings?

Player hours for the last seven days place dust2v2.1_server at #9,443, in the top 42% of the ranked field.

What is the population of dust2v2.1_server?

Population at the current refresh: 0 players on dust2v2.1_server, against 100 slots. The seven-day mean is 0 players, against a peak of 2. Across the last 48 hours, 20:00 UTC shows the highest average: 2 players.

Settings

What are the settings on dust2v2.1_server, and its rules?

The name of dust2v2.1_server does not state a gather rate. No custom group limit: 8 players is the standard. survival is the game mode, the standard game: gather, build, raid. Both fighting and raiding between players are allowed. In the server browser it sits under Modded, where plugins or settings alter the game. Oxide plugins are run. The server runs with VAC, Valve's anti-cheat, enabled.

The map on dust2v2.1_server: which one is it?

A procedural map of size 2,000 with seed 1605290779, generated by the game, runs on dust2v2.1_server. Because size and seed determine the map, it can be viewed on RustMaps via this page. The name of the map is Custom Map.

How to join

How can a player join dust2v2.1_server?

Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 212.22.93.48:28014.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp100
Max players 100 slots in total.
ts8
Group limit Default team size of 8.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build The game build is 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code No region code has been set.

Wipe schedule

^m
Monthly A monthly cycle, with Facepunch's force wipe as the reset.

Mods and access

^o
Oxide The Oxide (uMod) plugin framework is installed.
^z
Modded Plugins or settings change 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.