RUST METRICSFlight deck · live data
Data live Servers11,700 Players38,808 Populated2,943 Fresh wipes 3 h91 Scan5 min
‹ All servers37.204.225.17:28082
Offline Full Queue Fresh wipe Wipe due No query

Status QUO

Offline 37.204.225.17:28082 checked 32d ago

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,853top 67%
Last wipe50d agono schedule published
Next wipe–no wipe seen yet
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, measured since 26 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
15k10k15k20k26 Sep28 Sep29 Sep1 Oct2 Oct4 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly 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 Status QUO follow?

The rhythm of Status QUO's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 50 days 11 hours ago the current world was made.

Tags

How should you read the tags on Status QUO?

These are the tags Status QUO publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163407 (Build): Game build reading: 163407; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Status QUO appear in Rust Metrics lists and filters?

On Rust Metrics, Status QUO sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does Status QUO sit in the rankings?

Ranking for Status QUO: #15,853 on seven-day player hours, top 67% of all ranked servers.

How full does Status QUO get?

Status QUO is not responding; status offline, last seen 32 days ago.

Server details

What location is Status QUO hosted in?

Reading: location. Status QUO gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 37.204.225.17:28082.

What Rust version is Status QUO on?

Version check: Rust network protocol 2633 and build 163407 on Windows, run by Status QUO. Check: protocol. To join, your game must match; Steam handles the update.

Is Status QUO up, and how often does it stay up?

Status QUO reports offline. The last reading came 32 days ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 26 September 2026.

Rules and settings

How is Status QUO configured, and what rules are in force?

Reading the name gives no gather rate for Status QUO. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Status QUO?

From seed 561321969, the game generates the procedural map on Status QUO. Its size is 4,250. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How can you get onto Status QUO?

Press F1 in Rust and enter client.connect 37.204.225.17:28082. 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,gmrust,cs163407,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players 5 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163407
Build Game build reading: 163407.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

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.