RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h113 Scan5 min
‹ All servers212.22.93.48:28014
Online Full Queue Fresh wipe Wipe due No query

dust2v2.1_server

Online 212.22.93.48:28014 checked 1h ago

monthly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Wed 16:00 UTC
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 227 SERVER FPS

Server fps

48 h low 66 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 2,680 ×1000

Entities

48 h range 2,680–46,294 · memory 603 MB
1239 ET SINCE RESTART 00:33

Uptime

0 h 33 min since its last restart, at the last reading
7-day average0peak 1
Rank#14,326top 64%
Last wipe2h agomonthly schedule
Next wipe8d 0hThu 5 Nov, 19:00 UTC FW
Memory603MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75113:0014:0015:0016:00Wiped Wed 28 Oct, 13:38 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
010020030040013:0014:0015:0016: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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 8d 0h. 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. WPT 1Thu 5 Nov, 19:00 UTC8d 0hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC36d 0hFW

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 13:38 UTC4h 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 UTC24d ago 5 halved by day 4 6.7 days 0
Thu 1 Oct, 18:23 UTC FW26d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What should you expect from wipe day on dust2v2.1_server?

The busiest point of its recent wipes drew 4 players on average. 5 hours after the wipe the crowd peaked on the latest wipe, with 1 more in the queue. Until the next wipe, the crowd stayed above half that peak in 50% of its recent wipes. When it didn't hold, by day 3.5 it fell below half.

What wipe timing does dust2v2.1_server follow?

With the force wipe, once a month, dust2v2.1_server wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 2 hours ago the current world was made. Its tags carry a monthly wipe schedule.

Lists and filters

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from dust2v2.1_server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

Rust Metrics lists featuring dust2v2.1_server: Modded Rust servers, checked live. 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.

Player count

Where does dust2v2.1_server sit in the rankings?

Ranking for dust2v2.1_server: #14,326 on seven-day player hours, top 64% of all ranked servers.

What is the population on dust2v2.1_server?

Current headcount on dust2v2.1_server: 1 players, 1 slots available. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 16:00 UTC, 0 players on average.

Server

Which location does dust2v2.1_server run from?

No region comes from dust2v2.1_server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 212.22.93.48:28014.

What Rust version is dust2v2.1_server on?

Rust network protocol 2635 and build 168909 on Windows is the build dust2v2.1_server runs. Check: protocol. To join, your game must match; Steam handles the update.

Is performance on dust2v2.1_server within range?

Over the last 48 hours the average was 120 server fps; the floor was 66. Reading: 46,294 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 1,572 MB. What players call lag comes from low fps and an entity count on the rise.

How reliable is dust2v2.1_server, and is it online now?

dust2v2.1_server reports online. Status: normal. Reading: uptime. About 33 minutes ago it restarted, on its own count. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 20 September 2026, recorded by Rust Metrics.

Rules and settings

How is dust2v2.1_server configured, and what rules are in force?

Check: gather rate. The name dust2v2.1_server does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is dust2v2.1_server on?

Check: map. Procedural, size 2,000, seed 1605290779, generated by the game on dust2v2.1_server. The map repeats when size and seed match. Open it on RustMaps from this page. Map name, as listed: Custom Map.

Connection

What do you do to join dust2v2.1_server?

Press F1 in Rust and enter client.connect 212.22.93.48:28014. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. Reading: full. Expect to queue.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.