Rust Data

rustdata.spaceservers188.32.99.35:28083.ipynb

Run all rust-data · live

‹ All servers

Offline 188.32.99.35:28082 checked 44d ago

Status QUO

Connect

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

Right now

srv.summary()
players now 1/5 # 20% full
7-day average 0 # peak –
rank None # score 0
last wipe 49d 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
No rank history yet.

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
188.32.99.35:28082
region
–
max players
5
group limit
8, the default
wipe schedule
–
last wipe
8 Sep 2026, 15:16 UTC
hostname
–
first seen
13 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 · 515 on average535/625
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 338 on average32/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 335 on average56/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average281/325
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 279 on average110/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 262 on average125/150

Quick answers

From the figures on this page.

Player counts

How full does Status QUO run?

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

Server data

What is the Rust version on Status QUO?

Version Rust network protocol 2633 and build 163407 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 online now?

Offline now for Status QUO, last seen 44 days 8 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 13 September 2026.

In which location is Status QUO hosted?

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 188.32.99.35:28082.

Settings and map

Which settings and rules does Status QUO run?

You will not find a gather rate in the string Status QUO. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat status: VAC on.

Which map has Status QUO loaded?

The game generates its map: procedural, on Status QUO.

Wipe data

When does Status QUO wipe, and on what schedule?

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 49 days 7 hours ago.

Tags, lists

Where does Status QUO appear among Rust Data lists and filters?

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

How should you read the server tags on Status QUO?

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): 5 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs163407 (Build): The server runs build 163407; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way to join Status QUO?

Enter client.connect 188.32.99.35: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 5 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2633
Protocol Protocol 2633 is required; a different game version cannot connect.
cs163407
Build The server runs build 163407.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code No region code is 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 61,690 players 11,757 servers online