RUST METRICSFlight deck · live data
Data live Servers11,688 Players56,552 Populated3,390 Fresh wipes 3 h97 Scan5 min
‹ All servers178.140.185.87:28015
Online Full Queue Fresh wipe Wipe due No query

Status QUO

Online 178.140.185.87:28015 checked 14m ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.8 1.5 2.2 3 PAX 0 /3

Players now

0% full 7-day avg7-day peak
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 1
Rank#14,367top 65%
Last wipe1d agono schedule published
Next wipe–too few wipes seen yet
Memory–48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75100:0007:0013:0020:0002:0009:00Wiped Tue 27 Oct, 00:36 UTCWIPE

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
15k10k15k20k26 Oct27 Oct28 Oct

Top 65% 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.

usual gap0.9 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 00:36 UTC1d ago – – running 0
Mon 26 Oct, 02:01 UTC2d ago 1 – 0.9 days 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

Reset cycle

What should you expect from wipe day on Status QUO?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 23 hours.

What wipe timing does Status QUO follow?

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 it runs now was made 33 hours ago.

Lists and filters

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; mp3 (Max players): The server holds 3 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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?

Rust Metrics lists featuring 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; Last wipe: In the last 3 days.

Occupancy

Where does Status QUO sit in the rankings?

Player hours over seven days put Status QUO at #14,367, in the top 65% of all ranked servers.

How full does Status QUO get?

Current headcount on Status QUO: 0 players, 3 slots available. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 0 players, at 01:00 UTC over the last 48 hours.

Server details

Where does Status QUO sit?

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 178.140.185.87:28015.

What Rust version is Status QUO on?

Rust network protocol 2635 and build 168909 on Windows is the build Status QUO runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: online. Status QUO answers right now. Uptime for the last 1 full day: 24 of 24 hours, or 100%. Check: first contact. Rust Metrics logged it on 26 October 2026.

Map and rules

What settings and rules apply on Status QUO?

Check: gather rate. The name Status QUO does not state one. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

Which map is live on Status QUO?

Check: map. Procedural, generated by the game, on Status QUO.

How to join

How can you get onto Status QUO?

Press F1 in Rust and enter client.connect 178.140.185.87: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 mp3,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp3
Max players The server holds 3 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.