A quiet classroom so far: 0 of 3 on average. Plenty of space to grow.
Standingrank on player hours
35/ 100
F
Working its way up from the back of the class: #14,370 on player hours.
Uptimehours on the list, last 48
62/ 100
C
Missed a few lessons: on the list 30 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in uptime (C); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 65% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
WW·
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
Players each hour, from the hour of the wipe. The latest peaked at 1, 23 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
You'll find no region listed by Status QUO. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 178.140.185.87:28015.
Is Status QUO up, and how steady is its uptime?
Right now, Status QUO is online. For the last 1 full day, it was up 24 of 24 hours, or 100% of the time. The first sighting by Rust Server Score was on 26 October 2026.
Which Rust version is Status QUO running?
Rust network protocol 2635 and build 168909 on Windows is what Status QUO runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Status QUO wipe, and how often?
There are too few wipes on record for Status QUO to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 29 hours.
What happens on Status QUO when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 23 hours after the latest wipe began, the crowd hit its peak.
Player numbers
What position does Status QUO hold in the rankings?
In the top 65% of all ranked servers, Status QUO sits at #14,370 for player hours over the last seven days.
Is Status QUO a busy server?
With 3 slots available, Status QUO currently has 0 players. It peaked at 1 and averaged 0 players over the last seven days. Over the last 48 hours, the peak hour was 01:00 UTC, averaging 0 players.
Lists and filters
What do Status QUO's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp3 (Max players): The server holds 3 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server are the tags Status QUO publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show Status QUO?
These Rust Server Score lists count Status QUO among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.
Rules and settings
Which rules does Status QUO enforce, and what are its settings?
The name of Status QUO gives no gather rate. The default of 8 players applies as the group cap. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. The server runs Valve's anti-cheat, VAC.
Status QUO runs which map?
Status QUO runs a procedural map, which the game generates.
Connecting
What is the way to join Status QUO?
To connect, start Rust, press F1, and type client.connect 178.140.185.87:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp3,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp3
Max playersThe server holds 3 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
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.
A term to build on. Strongest in uptime (C); population is the one to work on (F).