Online 178.140.185.87:28015 checked 10m ago
Status QUO
Connect
srv = rust.server("178.140.185.87:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 65% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 00:36 UTC23h ago | NaN | NaN | running | 0 |
| 1 | Mon 26 Oct, 02:01 UTC1d ago | NaN | NaN | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 178.140.185.87:28015
- region
- –
- max players
- 3
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Oct 2026, 00:36 UTC
- hostname
- –
- first seen
- 26 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 520 on average | 389/425 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 336 on average | 22/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 333 on average | 45/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 317 on average | 180/200 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 279 on average | 69/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 263 on average | 77/100 |
Quick answers
From the figures on this page.
Population
What position does Status QUO take in the server rankings?
Over the last seven days Status QUO sits at #14,337 on player hours, in the top 65% of ranked servers.
How full does Status QUO run?
The sample now reads 0 players for Status QUO, out of 3 slots. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 01:00 UTC, averaging 0 players.
Server facts
What Rust version does Status QUO run?
Version Rust network protocol 2635 and build 168909 on Windows is reported by Status QUO. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Status QUO, and is it up?
Status QUO reports itself online at the current refresh. Over the last 1 full day the hours up number 0 of 24, 0%. The first row Rust Data holds for it is dated 26 October 2026.
Which location does Status QUO run from?
There is no region published for Status QUO. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 178.140.185.87:28015 is its address.
Map and rules
Which rules apply on Status QUO, and what settings?
The name Status QUO carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.
What is the map on Status QUO?
Status QUO runs a procedural map, which the game generates.
Wipes and dates
When does Status QUO wipe, and how often?
Too few wipes are on record for Status QUO to reveal its rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 23 hours ago, and that is the one in play.
Tags and filters
Which Rust Data filters and lists contain Status QUO?
On Rust Data, Status QUO appears in these lists: Rust community servers, unfiltered. 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; Last wipe: In the last 24 hours.
Which meanings do the tags on Status QUO hold?
Read by the game's server browser, the tags Status QUO publishes are: gmrust (Game mode): Survival play, standard Rust; mp3 (Max players): The server lists 3 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into Status QUO?
Enter client.connect 178.140.185.87:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.