Rust Data

rustdata.spaceservers31.210.52.135:28016.ipynb

Run all rust-data · live

‹ All servers

Offline 31.210.52.135:28015 checked 29d ago

My Staging Test Server

Connect

srv = rust.server("31.210.52.135:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,577 # top 65%
last wipe 33d ago # no schedule published
next wipe – # too few wipes 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
15k10k15k20k21 Sep24 Sep27 Sep29 Sep2 Oct5 Oct

Top 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.

usual gap1.1 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Thu 24 SepWed 23 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 24 Sep, 16:12 UTC33d ago 1 NaN running 0
1 Wed 23 Sep, 14:13 UTC34d ago 1 NaN 1.1 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.

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

Map

No map picture published
map
Procedural Map
size
–
seed
–

Server

srv.info()
address
31.210.52.135:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
24 Sep 2026, 16:12 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 · 540 on average530/575
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average358/400
2Rustoria.co - EU MainEU · groups of 16+ · weekly · 314 on average36/250
3Rusty Moose |EU Main|EU · groups of 12+ · weekly · 313 on average44/250
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 273 on average152/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 265 on average79/100

Quick answers

From the figures on this page.

Population data

How does My Staging Test Server compare in the rankings?

Rank #15,577 on seven-day player hours for My Staging Test Server, within the top 65% of all ranked servers.

How full does My Staging Test Server run?

My Staging Test Server returns no live count at this refresh, having last been seen 29 days 19 hours ago.

Server data

What is the Rust version on My Staging Test Server?

Version Rust network protocol 2634 and build 165654 on Windows is reported by My Staging Test Server. The protocol has to match before you can join, and Steam does the updating.

How reliable is My Staging Test Server, and is it online now?

The latest sample has My Staging Test Server offline, with a last sighting 29 days 19 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 13 September 2026.

Which location does My Staging Test Server run from?

For My Staging Test Server, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 31.210.52.135:28015.

Map and rules

What rules and settings are recorded for My Staging Test Server?

You will not find a gather rate in the string My Staging Test Server. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Community is its browser category. Anti-cheat status: VAC on.

Which map has My Staging Test Server selected?

A procedural map runs on My Staging Test Server, generated by the game.

Wipe schedule

When does My Staging Test Server wipe, and on what schedule?

A rhythm cannot be read from the wipes of My Staging Test Server on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 33 days 18 hours ago.

What is wipe day on My Staging Test Server like?

Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 0 hours in.

Tags and filters

Where does My Staging Test Server appear among Rust Data lists and filters?

The Rust Data lists that My Staging Test Server 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 My Staging Test Server hold?

These tags are published by My Staging Test Server and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs165654 (Build): Recorded game build: 165654; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way into My Staging Test Server?

In Rust, F1 opens the console: type client.connect 31.210.52.135:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp10,ptrak,$r?,v2634,gmrust,cs165654,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players Slot count: 10.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs165654
Build Recorded game build: 165654.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$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 55,436 players 11,682 servers online