Rust Data

rustdata.spaceservers145.224.72.110:20001.ipynb

Run all rust-data · live

‹ All servers

Offline 145.224.72.110:20000 checked 19d ago

test

Connect

srv = rust.server("145.224.72.110:20001")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,882 # top 72%
last wipe 26d 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
15k10k15k20k9 Oct10 Oct12 Oct13 Oct15 Oct16 Oct

Top 72% 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
145.224.72.110:20000
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 17:58 UTC
hostname
–
first seen
9 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 · 542 on average145/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average131/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average15/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 283 on average19/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average16/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 249 on average46/200

Quick answers

From the figures on this page.

Player counts

How does test compare in the rankings?

Over the last seven days test sits at #15,882 on player hours, in the top 72% of ranked servers.

How full does test run?

The current row shows test offline; the last response was 19 days 11 hours ago.

About the server

What is the Rust version on test?

Rust network protocol 2634 and build 167398 on Windows is what test runs. The protocol has to match before you can join, and Steam does the updating.

Is test up, and what does its uptime show?

test is offline at this refresh; the last response came 19 days 11 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 9 October 2026.

Where does test sit?

There is no region published for test. Rust Data does not look up where the machine stands; it shows where a server says it is. 145.224.72.110:20000 is its address.

Settings and map

Which settings and rules does test run?

The name test carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is not running; Valve's anti-cheat is off.

Which map has test selected?

A procedural map runs on test, generated by the game.

Wipe data

When does test wipe, and how often?

The record for test holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 26 days 11 hours ago.

Tags and filters

Which lists on Rust Data hold test, and which filters?

These Rust Data lists include test: 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?

These tags are published by test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs167398 (Build): Recorded game build: 167398; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way to join test?

The manual route: launch Rust, F1, then client.connect 145.224.72.110:20000. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol To join, your game must run protocol 2634.
cs167398
Build Recorded game build: 167398.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code The region field is empty.

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 31,131 players 11,626 servers online