RUST METRICSFlight deck · live data
Data live Servers11,701 Players46,298 Populated3,163 Fresh wipes 3 h102 Scan5 min
‹ All servers46.222.164.149:28015
Offline Full Queue Fresh wipe Wipe due No query

#1

Offline 46.222.164.149:28015 checked 23d ago

monthly wipes moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 1 /5

Players now

20% full 7-day avg
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 –
Rank#13,784top 61%
Last wipe27d agomonthly schedule
Next wipe7d 18hThu 5 Nov, 19:00 UTC FW
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
15k10k15k20k4 Oct6 Oct7 Oct9 Oct10 Oct12 Oct

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

PLAN

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 7d 18h. The force wipe

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 wipe timing does #1 follow?

The estimate for #1's next wipe comes from the force wipe. Mark Thursday 5 November at 19:00 UTC: that is force wipe day, and the wipe hits all Rust servers. The world it runs now was made 27 days 5 hours ago. The tags state a wipe schedule of one wipe a month.

Tag meanings

How should you read the tags on #1?

Tags published by #1, read by the game's server browser: gmvanilla (Game mode): Survival on vanilla settings; mp5 (Max players): Slots: 5; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does #1 appear in Rust Metrics lists and filters?

On Rust Metrics, #1 sits in these lists: 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.

Population

What position does #1 hold among Rust servers?

Player hours over seven days put #1 at #13,784, in the top 61% of all ranked servers.

What is the population on #1?

#1 is not responding; status offline, last seen 23 days 21 hours ago.

Server details

Where does #1 sit?

No region comes from #1. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 46.222.164.149:28015.

What Rust version is #1 on?

Reading: #1, Rust network protocol 2634 and build 166652, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is #1 up, and how often does it stay up?

#1 reports offline. The last reading came 23 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 4 October 2026.

Rules and settings

How is #1 configured, and what rules are in force?

Check: gather rate. The name #1 does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on #1?

The game generates a procedural map for #1.

Connection

How can you get onto #1?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,^m,gmvanilla,cs166652,ts8,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
mp5
Max players Slots: 5.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Build 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Wipe schedule

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

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.