Status QUO
Offline 178.140.132.216:28082 checked 43d 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- 84/250
- 115/200
- 397/450
- 21/100
- 476/525
- 362/425
Quick answers
from the figures on this pageWipe schedule
How often does Status QUO wipe, and when?
The rhythm of Status QUO's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 51 days 9 hours ago.
Tags
Which tags does Status QUO carry, and what do they mean?
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): The server holds 5 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163407 (Build): Build 163407; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show Status QUO?
Rust Metrics lists featuring Status QUO: 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
What position does Status QUO hold among Rust servers?
Player hours over seven days put Status QUO at #13,329, in the top – of all ranked servers.
How full does Status QUO get?
Status for Status QUO: offline. Last seen 43 days 22 hours ago.
Operator and location
Where does Status QUO sit?
No region comes from Status QUO. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 178.140.132.216:28082.
What Rust version is Status QUO on?
Version check: Rust network protocol 2633 and build 163407 on Windows, run by Status QUO. To get in, your game needs the same protocol; Steam applies the update.
Is Status QUO up, and how often does it stay up?
Reading: offline. Status QUO last answered 43 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 15 September 2026.
Map and rules
What rules does Status QUO enforce, and what are its settings?
Reading the name gives no gather rate for Status QUO. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on Status QUO?
Check: map. Procedural, generated by the game, on Status QUO.
Join
How can you get onto Status QUO?
Check: join. Open Rust, press F1, then enter client.connect 178.140.132.216:28082. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.