RUST METRICSFlight deck · live data
Data live Servers11,614 Players33,332 Populated2,810 Fresh wipes 3 h68 Scan5 min
‹ All servers168.100.162.12:29015
Online Full Queue Fresh wipe Wipe due No query

Dev

Online NA 168.100.162.12:29015 checked 11m ago

weekly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Thu 05:00 UTC
0 0.2 0.5 0.8 1 PAX 0 /?

Players now

no slots published 7-day avg7-day peak 1, past the slots
0 10 30 60 120 256 FPS 60 SERVER FPS

Server fps

48 h low 46 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 70,772 ×1000

Entities

48 h range 68,388–73,132 · memory 2,302 MB
1239 ET SINCE RESTART 08:25

Uptime

8 h 25 min since its last restart, at the last reading
7-day average0peak 1
Rank#13,062top 59% · #1412 in NA
Last wipe9h agoweekly schedule
Next wipe6d 14hWed 4 Nov, 20:36 UTC
Memory2,302MB48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75107:0016:0001:0010:0020:0005:00Wiped Wed 28 Oct, 20:36 UTCWIPE

Hourly average and peak, UTC.

REC 2

Server performance

Server fpsWipe
02040608007:0016:0001:0010:0020:0005:00Wiped Wed 28 Oct, 20:36 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 17 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 Sep6 Oct13 Oct21 Oct29 Oct

Top 59% of all ranked servers, top 76% in NA. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

from its schedule tag

Next wipe Wednesday 4 November, 20:36 UTC, in 6d 14h. Its weekly schedule tag · low confidence

usual gap2.8 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

Coming wipes

  1. WPT 1Wed 4 Nov, 20:36 UTC6d 14h
  2. WPT 2Thu 5 Nov, 19:00 UTC7d 12hFW
  3. WPT 3Wed 11 Nov, 20:36 UTC13d 14h
  4. WPT 4Wed 18 Nov, 20:36 UTC20d 14h
  5. WPT 5Wed 25 Nov, 20:36 UTC27d 14h
  6. WPT 6Wed 2 Dec, 20:36 UTC34d 14h
  7. WPT 7Thu 3 Dec, 19:00 UTC35d 12hFW
  8. WPT 8Wed 9 Dec, 20:36 UTC41d 14h

The first 48 hours of its last wipes

Mon 26 OctFri 23 OctThu 22 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 28 Oct, 20:36 UTC9h ago – – running 0
Mon 26 Oct, 19:35 UTC2d ago 1 halved by day 1 2 days 0
Fri 23 Oct, 04:45 UTC6d ago 1 halved by day 1 3.6 days 0
Thu 22 Oct, 04:06 UTC7d ago 1 – 1 days 0
Wed 14 Oct, 20:24 UTC14d ago 1 halved by day 1 7.3 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

Reset cycle

What should you expect from wipe day on Dev?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. By day 1 it fell below half when it didn't.

When does Dev wipe?

Its tag guides the prediction: too few of Dev's wipes are on record to confirm its schedule. Wednesday 4 November at 20:36 UTC is when its next wipe is due. 9 hours ago the current world was made. Its tags carry a weekly wipe schedule.

Lists and filters

How should you read the tags on Dev?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp0 (Max players): 0 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^w (Weekly): Wipe cycle: weekly; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game; NA (North America): North America is the browser category it sits in from Dev. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Dev appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Dev: Modded Rust servers, checked live and North America: server readout. Check: filters. On the server list it appears under these: Region: North America; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 24 hours.

Occupancy

What position does Dev hold among Rust servers?

Top 59% of all ranked servers: Dev takes #13,062 on seven-day player hours and #1,412 in North America.

What is the population on Dev?

0 players are on Dev at this moment. Seven-day check: 0 players on average. Peak reading: 1. The last 48 hours peaked at 20:00 UTC, averaging 0 players at that hour.

Operator and location

What location is Dev hosted in?

Reading: location. The NA tag puts Dev in North America. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 168.100.162.12:29015.

What Rust version is Dev on?

Version check: Rust network protocol 2635 and build 168909 on Linux, run by Dev. Matching protocol is required to join. Let Steam update your game.

Is performance on Dev within range?

Reading: 59 server fps on average across the last 48 hours. It never dropped below 46. Check: entities. The peak was 73,132, counting buildings, deployables and the rest of the world. Memory peak: 3,224 MB. What players call lag comes from low fps and an entity count on the rise.

What is the uptime on Dev, and is it online?

Dev reports online. Status: normal. Check: restart. The uptime it reports puts the last restart about 8 hours ago. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

How is Dev configured, and what rules are in force?

Reading the name gives no gather rate for Dev. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

What map is Dev on?

Size 3,700 and seed 1337: the game generates the procedural map on Dev from them. View it on RustMaps from this page: matching size and seed give an identical map. Its map carries the name Custom Map.

Connection

How do you connect to Dev?

Press F1 in Rust and enter client.connect 168.100.162.12:29015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2635,^w,NA,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp0
Max players 0 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Wipe schedule

^w
Weekly Wipe cycle: weekly.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock game.

Region

NA
North America North America is the browser category it sits in.

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.