RUST METRICSFlight deck · live data
Data live Servers11,633 Players40,937 Populated2,826 Fresh wipes 3 h115 Scan5 min
‹ All servers159.196.59.137:28315
Online Full Queue Fresh wipe Wipe due No query

<mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events |

Online 159.196.59.137:28315 checked 12m ago

2x moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

last reading Fri 03:00 UTC
0 6 12 19 25 PAX 0 /25

Players now

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

Server fps

48 h low 29 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 121,733 ×1000

Entities

48 h range 121,733–130,442 · memory 3,767 MB
1239 ET SINCE RESTART 06:48

Uptime

6 h 48 min since its last restart, at the last reading
7-day average0peak 2
Rank#5,255top 24%
Last wipe28d agono schedule published
Next wipe6d 14hThu 5 Nov, 19:00 UTC FW
Memory3,767MB48 h peak 2 players
REC 1

Players
AveragePeak
00.511.5205:0014:0000:0009:0018:0003:00

Hourly average and peak, UTC.

REC 2

Server performance
02040608005:0014:0000:0009:0018:0003:00

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
12k4k6k8k20 Sep28 Sep6 Oct14 Oct22 Oct30 Oct

Top 24% 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 6d 14h. The force wipe · high confidence

wipe-day peak6players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC6d 14hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC34d 14hFW

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 21:31 UTC FW28d ago 6 – running 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 <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events |?

At their busiest, its recent wipes drew 6 players on average. 14 hours after the wipe, the crowd peaked on the latest wipe.

When does <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | wipe?

The only wipe for <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | is the force wipe, once a month. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. 28 days 6 hours ago the current world was made.

Lists and filters

How should you read the tags on <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events |?

Tags published by <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events |, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp25 (Max players): Slots: 25; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; 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; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | appear in Rust Metrics lists and filters?

On Rust Metrics, <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | sits in these lists: 2x Rust servers, checked live and Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.

Player count

What position does <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | hold among Rust servers?

Ranking for <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events |: #5,255 on seven-day player hours, top 24% of all ranked servers.

What is the population on <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events |?

0 of 25 slots are filled on <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | right now. Seven-day check: 0 players on average. Peak reading: 2. Average at the busiest hour was 2 players, at 02:00 UTC over the last 48 hours.

Server

What location is <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | hosted in?

Reading: location. <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 159.196.59.137:28315.

What Rust version is <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | on?

Rust network protocol 2635 and build 168909 on Windows is the build <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | runs. Matching protocol is required to join. Let Steam update your game.

What is the performance reading for <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events |?

Over the last 48 hours the average was 38 server fps; the floor was 29. Check: entities. The peak was 130,442, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 4,390 MB. What players call lag comes from low fps and an entity count on the rise.

How reliable is <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events |, and is it online now?

Check: connection. <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | is online at this moment. Reading: uptime. About 6 hours ago it restarted, on its own count. Reading: 89% uptime over the last 7 full days. It was up 149 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Map and rules

How is <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | configured, and what rules are in force?

The name carries the rate: 2x gather on <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events |. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events |?

Size 4,250 and seed 969105723: the game generates the procedural map on <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events | from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

What do you do to join <mag> Rust | Adelaide | PVE | 2x | Kits | NPCs | Events |?

Check: join. Open Rust, press F1, then enter client.connect 159.196.59.137:28315. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp25
Max players Slots: 25.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
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.

Mods and access

^o
Oxide It runs Oxide, also known as 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.