Rust Data

rustdata.spaceservers91.200.52.59:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 91.200.52.59:28015 checked 1d ago

TEST

Connect

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

Right now

srv.summary()
players now 1/10 # 10% full
7-day average 1 # peak 1
rank #8,189 # top 37%
last wipe 2d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75120:0021:00

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
15k10k15k20k20 Sep24 Sep13 Oct17 Oct22 Oct28 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap7.8 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sun 25 OctMon 12 OctFri 9 Oct
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 Sun 25 Oct, 10:37 UTC2d ago 1 NaN running 1
1 Mon 12 Oct, 19:27 UTC15d ago 1 held half 12.6 days 1
2 Fri 9 Oct, 17:59 UTC18d ago NaN NaN 3.1 days 1

# 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
91.200.52.59:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
25 Oct 2026, 10:37 UTC
hostname
–
first seen
20 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 · 532 on average214/250
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 327 on average15/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 325 on average19/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average115/200
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 278 on average40/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average42/100

Quick answers

From the figures on this page.

Population data

How does TEST compare in the rankings?

Over the last seven days TEST sits at #8,189 on player hours, in the top 37% of ranked servers.

What population does TEST carry?

Offline now for TEST, with the last sample 30 hours ago. Over the last seven days it averaged 1 players and peaked at 1. Averaged by hour over 48 hours, 21:00 UTC is the busiest, at 1 players.

About the server

What Rust version does TEST run?

Rust network protocol 2635 and build 168909 on Windows is what TEST runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is TEST, and is it up?

Offline now for TEST, last seen 30 hours ago. Over the last 7 full days the hours up number 10 of 168, 6%. Its earliest recorded date in Rust Data is 20 September 2026.

Where does TEST sit?

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

Rules, settings, map

What rules and settings are recorded for TEST?

No gather rate appears in the name: TEST. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It is a community server, and the browser files it under Community. VAC, Valve's anti-cheat, is enabled.

Which map has TEST loaded?

The game generates its map: procedural, on TEST.

Wipes and dates

On what schedule does TEST wipe?

TEST wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 2 days 17 hours ago.

On TEST, what happens on wipe day?

The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Lists and tags

Where does TEST appear among Rust Data lists and filters?

The Rust Data lists that TEST 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; Last wipe: In the last 3 days.

How should you read the server tags on TEST?

Read by the game's server browser, the tags TEST publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Join steps

How can I connect to TEST?

In Rust, F1 opens the console: type client.connect 91.200.52.59: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?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players The server lists 10 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build The server runs build 168909.
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 34,878 players 11,611 servers online