Working its way up from the back of the class: #15,491 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
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
32/ 100
F
Lost ground: down 5,508 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
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.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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
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
classmates: the same kind of game, then region, group limit, rate and wipes
Status QUO leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 178.140.102.238:28082 is the address to use.
Is Status QUO up, and how steady is its uptime?
You cannot join now: Status QUO is offline, last seen 37 days 23 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Status QUO sit?
You will find Status QUO on Rust network protocol 2633 and build 163407, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
When does Status QUO wipe, and how often?
The record holds too few of Status QUO's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 50 days 8 hours have passed since this world was made.
Player numbers
What position does Status QUO hold in the rankings?
Over the last seven days, Status QUO has #15,491 for player hours, in the top 69% of all ranked servers.
What does the population on Status QUO look like?
Status QUO is offline at the moment; the last time it was seen was 37 days 23 hours ago.
Lists and filters
How should you read the tags on Status QUO?
The game's browser takes its cue from the tags Status QUO has set: gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): Its slot count is 5; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs163407 (Build): This runs on build 163407; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Status QUO?
Rust Server Score lists that include Status QUO: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Server rules
How is Status QUO set up, and what rules does it keep?
The name of Status QUO gives no gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in 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?
The game generates the procedural map on Status QUO at size 4,250 with seed 561321969. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
What is the way to join Status QUO?
To connect, start Rust, press F1, and type client.connect 178.140.102.238:28082. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,gmrust,cs163407,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max playersIts slot count is 5.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs163407
BuildThis runs on build 163407.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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. Even marks across the subjects, from F to F.