Rust Data

rustdata.spaceservers31.186.54.181:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 31.186.54.181:28015 checked 18d ago

TEST

Connect

srv = rust.server("31.186.54.181:28017")
print(srv.connect_command)

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak –
rank #14,530 # top 66%
last wipe 18d 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
15k10k15k20k11 Oct12 Oct13 Oct15 Oct16 Oct17 Oct

Top 66% of all ranked servers. Ranked on player hours over the last seven days.

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
31.186.54.181:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
10 Oct 2026, 23:55 UTC
hostname
–
first seen
11 Oct 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 · 510 on average303/375
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 317 on average406/475
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 281 on average962/1000
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 276 on average44/100
4eulongtest (private perf box)EU · groups of 14+ · monthly · 267 on average480/8
5Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average986/1000

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does TEST rank?

Player hours over seven days put TEST at #14,530, in the top 66% of the ranked set.

How full does TEST run?

The current row shows TEST offline; the last response was 18 days 19 hours ago.

Server data

What is the Rust version on TEST?

Rust network protocol 2634 and build 167398 on Windows is what TEST runs. Steam updates your game for you, but the protocol must match to join.

Is TEST up, and what does its uptime show?

TEST is offline at this refresh; the last response came 18 days 19 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 11 October 2026.

Where does TEST sit?

There is no region published for TEST. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 31.186.54.181:28015 is its address.

Rules, settings, map

Which rules apply on TEST, and what settings?

No gather rate appears in the name: TEST. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.

Which map has TEST loaded?

TEST runs a procedural map, which the game generates.

Wipe schedule

When does TEST wipe, and how often?

A rhythm cannot be read from the wipes of TEST on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 18 days 19 hours ago.

Tags and filters

Which Rust Data filters and lists contain TEST?

The Rust Data lists that TEST fits are: Rust community servers, unfiltered. These filters bring it up 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 TEST?

The game's server browser reads these tags from TEST: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167398 (Build): Recorded game build: 167398; 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.

How to join

What is the way to join TEST?

Enter client.connect 31.186.54.181:28015 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 mp10,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players 10 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs167398
Build Recorded game build: 167398.
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 104,326 players 11,886 servers online