Status QUO
Offline 188.32.99.35:28082 checked 45d ago
Server instruments
no direct query in 48 hoursPlayers now
20% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 636/675
- 485/525
- 59/250
- 36/250
- 138/200
- 255/300
Quick answers
from the figures on this pageReset cycle
What wipe timing does Status QUO follow?
Its rhythm cannot be told from the wipes of Status QUO on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 50 days 4 hours ago the current world was made.
Tag meanings
How should you read the tags on Status QUO?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163407 (Build): Game build reading: 163407; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from Status QUO. 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.
Player count
What is the population on Status QUO?
Reading for Status QUO: offline at this moment; last seen 45 days 4 hours ago.
Operator and location
Where does Status QUO sit?
No region tag on Status QUO. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 188.32.99.35:28082.
What Rust version is Status QUO on?
Rust network protocol 2633 and build 163407 on Windows is the build Status QUO runs. 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 45 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Rules and settings
How is Status QUO configured, and what rules are in force?
No gather rate appears in the name: Status QUO. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Status QUO?
Procedural map on Status QUO, made by the game's generator.
How to join
How do you connect to Status QUO?
Check: join. Open Rust, press F1, then enter client.connect 188.32.99.35:28082. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.