RUST METRICSFlight deck · live data
Data live Servers11,691 Players35,842 Populated2,916 Fresh wipes 3 h97 Scan5 min
‹ All servers37.135.183.7:28015
Offline Full Queue Fresh wipe Wipe due No query

#1

Offline 37.135.183.7:28015 checked 28d 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#16,293top 68%
Last wipe43d agomonthly schedule
Next wipe7d 15hThu 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
15k10k15k20k29 Sep1 Oct2 Oct4 Oct5 Oct7 Oct

Top 68% 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 15h. 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?

From the force wipe, the next wipe of #1 is an estimate. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world in play was created 43 days 22 hours ago. The tags state a wipe schedule of one wipe a month.

Tag meanings

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): Survival on vanilla settings; 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): Game build reading: 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^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. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.

Player count

What position does #1 hold among Rust servers?

Player hours over seven days put #1 at #16,293, in the top 68% of all ranked servers.

How full does #1 get?

Reading for #1: offline at this moment; last seen 28 days 11 hours ago.

Server details

Where does #1 sit?

No region comes from #1. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 37.135.183.7:28015.

What Rust version is #1 on?

Reading: #1, Rust network protocol 2633 and build 165217, Windows. Matching protocol is required to join. Let Steam update your game.

How reliable is #1, and is it online now?

Reading: offline. #1 last answered 28 days 11 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 29 September 2026, recorded by Rust Metrics.

Rules and settings

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

No gather rate appears in the name: #1. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Which map is live on #1?

Procedural map on #1, made by the game's generator.

Connection

What do you do to join #1?

Press F1 in Rust and enter client.connect 37.135.183.7:28015. 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 mp5,ptrak,$r?,v2633,^m,gmvanilla,cs165217,ts8,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
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 Game build reading: 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.