Rust Data

rustdata.spaceservers213.109.145.5:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 213.109.145.5:28015 checked 10d ago

TEST

Connect

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

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 0 # peak –
rank #13,075 # top 60%
last wipe 11d 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
15k10k15k20k17 Oct19 Oct20 Oct22 Oct23 Oct25 Oct

Top 60% 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
213.109.145.5:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
17 Oct 2026, 18:58 UTC
hostname
–
first seen
17 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 average151/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average137/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average14/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 283 on average21/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average16/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 249 on average57/200

Quick answers

From the figures on this page.

Player counts

Against other Rust servers, how does TEST rank?

Rank #13,075 on seven-day player hours for TEST, within the top 60% of all ranked servers.

What population does TEST carry?

Offline now for TEST, with the last sample 10 days 21 hours ago.

Server data

What Rust version does TEST run?

Rust network protocol 2634 and build 167781 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?

The latest sample has TEST offline, with a last sighting 10 days 21 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 17 October 2026.

In which location is TEST hosted?

For TEST, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 213.109.145.5:28015 is its address.

Settings and map

Which rules apply on TEST, and what settings?

No gather rate appears in the name: TEST. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. It is a community server, and the browser files it under Community. VAC is running: Valve's anti-cheat is on.

What is the map on TEST?

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

Wipe data

When does TEST wipe, and on what schedule?

The record for TEST holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 11 days 10 hours ago.

Lists and tags

Where does TEST appear among Rust Data lists and filters?

On Rust Data, TEST appears in these lists: 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; Last wipe: In the last 2 weeks.

Which meanings do the tags on TEST hold?

The game's server browser reads these tags from TEST: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not 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.

Join steps

How can I connect to TEST?

The manual route: launch Rust, F1, then client.connect 213.109.145.5:28015. 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,cs167781,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players The server lists 10 slots.
ts8
Group limit Team limit of 8, as shipped by default.
v2634
Protocol To join, your game must run protocol 2634.
cs167781
Build The server runs build 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$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 32,059 players 11,620 servers online