RUST METRICSFlight deck · live data
Data live Servers11,716 Players60,383 Populated3,374 Fresh wipes 3 h178 Scan5 min
‹ All servers37.135.183.19:28015
Offline Full Queue Fresh wipe Wipe due No query

#1

Offline 37.135.183.19:28015 checked 30d ago

monthly wipes moddedoxide
COM 1 · connect

Server instruments

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

Players now

0% 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#15,728top 66%
Last wipe44d agomonthly schedule
Next wipe7d 7hThu 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
15k10k15k20k24 Sep26 Sep28 Sep1 Oct3 Oct5 Oct

Top 66% 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 7h. 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 timing

What wipe timing does #1 follow?

The estimate for #1's next wipe comes from the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world in play was created 44 days 6 hours ago. The tags state a wipe schedule of one wipe a month.

Tags

Which tags does #1 carry, and what do they mean?

These are the tags #1 publishes, and the server browser reads them: gmvanilla (Game mode): Check: mode. Vanilla survival; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. 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. Reading: server list filters. It comes up under 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 #15,728, in the top 66% of all ranked servers.

How full does #1 get?

Status for #1: offline. Last seen 30 days 14 hours ago.

Server details

Which location does #1 run from?

No region tag on #1. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 37.135.183.19:28015.

What Rust version is #1 on?

Reading: #1, Rust network protocol 2633 and build 165217, Windows. To get in, your game needs the same protocol; Steam applies the update.

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

#1 reports offline. The last reading came 30 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 24 September 2026.

Settings and map

What settings and rules apply on #1?

Check: gather rate. The name #1 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. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Check: anti-cheat. VAC, Valve's system, is on.

What map is #1 on?

The game generates a procedural map for #1.

Join

How do you connect to #1?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2633,^m,gmvanilla,cs165217,ts8,^o^z

Game

gmvanilla
Game mode Check: mode. Vanilla survival.
mp5
Max players The server holds 5 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build The server runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Wipe schedule

^m
Monthly Check: wipe cycle. Monthly, alongside Facepunch's force wipe.

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.