RUST METRICSFlight deck · live data
Data live Servers11,716 Players52,540 Populated3,337 Fresh wipes 3 h139 Scan5 min
‹ All servers37.110.26.219:28082
Offline Full Queue Fresh wipe Wipe due No query

Status QUO

Offline 37.110.26.219:28082 checked 15d 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,627top 71%
Last wipe18d agono schedule published
Next wipe–too few wipes 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 11 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k9 Oct11 Oct13 Oct15 Oct17 Oct19 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

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

Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 9 Oct, 11:58 UTC18d ago 1 – 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 Status QUO?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 2 hours.

When does Status QUO wipe?

The rhythm of Status QUO's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 18 days 12 hours ago.

Tag meanings

How should you read the tags on Status QUO?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167398 (Build): Build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from Status QUO. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Status QUO?

These Rust Metrics lists carry Status QUO: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does Status QUO hold among Rust servers?

Player hours over seven days put Status QUO at #15,627, in the top 71% of all ranked servers.

What player count does Status QUO carry?

Status QUO is not responding; status offline, last seen 15 days 22 hours ago.

Server details

Which location does Status QUO run from?

No region comes from Status QUO. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 37.110.26.219:28082.

What Rust version is Status QUO on?

Version check: Rust network protocol 2634 and build 167398 on Windows, run by Status QUO. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Status QUO, and is it online?

Check: connection. Status QUO is offline at this moment. Last contact was 15 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 9 October 2026.

Map and rules

What rules does Status QUO enforce, and what are its settings?

Check: gather rate. The name Status QUO does not state one. 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. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on Status QUO?

Check: map. Procedural, size 4,250, seed 561321969, generated by the game on Status QUO. View it on RustMaps from this page: matching size and seed give an identical map.

Join

How do you connect to Status QUO?

Press F1 in Rust and enter client.connect 37.110.26.219: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?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players Slots: 5.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167398
Build Build 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.