Rust Data

rustdata.spaceservers178.140.132.216:28083.ipynb

Run all rust-data · live

‹ All servers

Offline 178.140.132.216:28082 checked 43d ago

Status QUO

Connect

srv = rust.server("178.140.132.216:28083")
print(srv.connect_command)

Right now

srv.summary()
players now 1/5 # 20% full
7-day average 0 # peak –
rank #13,329 # no region published
last wipe 51d ago # no schedule published
next wipe – # no wipe seen yet

Players

srv.players.plot(range="48h")
No hourly history yet.

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
This server has not answered a direct query in the last 48 hours.

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 best
RankRank in region
15k10k15k20k20 Sep21 Sep22 Sep23 Sep

Wipe schedule

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)
wipedpeakcrowdlastedplayers_before
Empty DataFrame · 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.

display(srv.map, srv.info())

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
178.140.132.216:28082
region
–
max players
5
group limit
8, the default
wipe schedule
–
last wipe
8 Sep 2026, 15:16 UTC
hostname
–
first seen
15 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 514 on average440/500
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average447/475
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 281 on average976/1000
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average63/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average992/1000
5Rustoria.co - US MainNA · groups of 16+ · weekly · 236 on average26/250

Quick answers

From the figures on this page.

Population data

How does Status QUO compare in the rankings?

Player hours over seven days put Status QUO at #13,329, in the top – of the ranked set.

How full does Status QUO run?

The current row shows Status QUO offline; the last response was 43 days 13 hours ago.

About the server

What Rust version does Status QUO run?

The build is Rust network protocol 2633 and build 163407 on Windows, run by Status QUO. The protocol has to match before you can join, and Steam does the updating.

How reliable is Status QUO, and is it up?

The latest sample has Status QUO offline, with a last sighting 43 days 13 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 15 September 2026.

Which location does Status QUO run from?

There is no region published for Status QUO. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 178.140.132.216:28082.

Map and rules

Which settings and rules does Status QUO run?

You will not find a gather rate in the string Status QUO. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

Which map has Status QUO selected?

Status QUO runs a procedural map, which the game generates.

Wipe schedule

On what schedule does Status QUO wipe?

Too few wipes are on record for Status QUO to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 51 days ago.

Tags and filters

Which Rust Data filters and lists contain Status QUO?

The Rust Data lists that Status QUO fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Which meanings do the tags on Status QUO hold?

These tags are published by Status QUO and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): To join, your game must run protocol 2633; cs163407 (Build): The server runs build 163407; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

How can I connect to Status QUO?

Enter client.connect 178.140.132.216:28082 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.

Server tags · what each one means

srv.tags.decode()

Published as mp5,ptrak,$r?,v2633,gmrust,cs163407,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp5
Max players The server lists 5 slots.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol To join, your game must run protocol 2633.
cs163407
Build The server runs build 163407.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

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.

Rust Data 96,005 players 11,867 servers online