RUST METRICSFlight deck · live data
Data live Servers11,645 Players42,938 Populated3,029 Fresh wipes 3 h91 Scan5 min
‹ All servers38.64.18.124:28015
Offline Full Queue Fresh wipe Wipe due No query

RustDev release test (local only)

Offline 38.64.18.124:28015 checked 2d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak 1
Rank#12,809top 58%
Last wipe24d agono schedule published
Next wipe–no rhythm it keeps
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k16 Oct19 Oct21 Oct24 Oct26 Oct29 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Fri 23 OctTue 20 OctMon 19 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 01:51 UTC6d ago 1 – running 0
Tue 20 Oct, 22:42 UTC8d ago 0 – 2.1 days 0
Mon 19 Oct, 22:47 UTC9d ago 1 – 1 days 0
Sun 18 Oct, 23:44 UTC10d ago 1 – 1 days 0
Fri 16 Oct, 23:12 UTC12d ago 0 – 2 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 schedule

What should you expect from wipe day on RustDev release test (local only)?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours.

When does RustDev release test (local only) wipe?

No next wipe can be predicted for RustDev release test (local only), which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 24 days 11 hours ago.

Tags

Which tags does RustDev release test (local only) carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game from RustDev release test (local only). 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 RustDev release test (local only)?

On Rust Metrics, RustDev release test (local only) sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does RustDev release test (local only) hold among Rust servers?

Ranking for RustDev release test (local only): #12,809 on seven-day player hours, top 58% of all ranked servers.

How full does RustDev release test (local only) get?

RustDev release test (local only) is not responding; status offline, last seen 2 days 13 hours ago. Check: players over seven days. Average 0, peak 1.

Operator and location

What location is RustDev release test (local only) hosted in?

Reading: location. RustDev release test (local only) gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 38.64.18.124:28015.

What Rust version is RustDev release test (local only) on?

Reading: RustDev release test (local only), Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

Is RustDev release test (local only) up, and how often does it stay up?

Reading: offline. RustDev release test (local only) last answered 2 days 13 hours ago. Uptime for the last 7 full days: 35 of 168 hours, or 21%. The first sighting on Rust Metrics was 16 October 2026.

Map and rules

How is RustDev release test (local only) configured, and what rules are in force?

No gather rate appears in the name: RustDev release test (local only). 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on RustDev release test (local only)?

Procedural map on RustDev release test (local only), made by the game's generator.

How to join

What do you do to join RustDev release test (local only)?

To join: start Rust, press F1 and type client.connect 38.64.18.124:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock 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.