Rust Data

rustdata.spaceservers87.151.212.210:28016.ipynb

Run all rust-data · live

‹ All servers

Online 87.151.212.210:28015 checked 7m ago

InternalTrainServer""

Connect

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

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,419 # top 69%
last wipe 10h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
0123406:0015:0000:0010:0019:0004:00Wiped Tue 27 Oct, 19:08 UTCWIPE

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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 69% 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 gap5.2 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Thu 8 OctSun 4 OctFri 2 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Tue 27 Oct, 19:08 UTC10h ago NaN NaN running 0
1 Thu 8 Oct, 18:52 UTC19d ago 0 NaN 19 days 0
2 Sun 4 Oct, 18:21 UTC23d ago 0 NaN 4 days 0
3 Fri 2 Oct, 15:53 UTC25d ago 0 NaN 2.1 days 0
4 Thu 1 Oct, 19:06 UTC FW26d ago 0 NaN 0.9 days 0
5 Fri 25 Sep, 11:44 UTC32d ago 0 NaN 6.3 days 0
6 Thu 17 Sep, 18:11 UTC40d ago 1 halved by day 3 7.7 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
87.151.212.210:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
27 Oct 2026, 19:08 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 · 534 on average247/275
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 322 on average20/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 321 on average17/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average163/200
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 277 on average64/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average37/100

Quick answers

From the figures on this page.

Player counts

What position does InternalTrainServer"" take in the server rankings?

Player hours over seven days put InternalTrainServer"" at #15,419, in the top 69% of the ranked set.

How full does InternalTrainServer"" run?

The sample now reads 0 players for InternalTrainServer"", out of 10 slots. Over the last seven days it averaged 0 players.

Server data

Which Rust version is InternalTrainServer"" on?

Version Rust network protocol 2635 and build 168909 on Linux is reported by InternalTrainServer"". Joining needs the same protocol on your game; Steam handles the update.

Is InternalTrainServer"" up, and what does its uptime show?

The current sample puts InternalTrainServer"" online. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

In which location is InternalTrainServer"" hosted?

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

Settings and map

Which settings and rules does InternalTrainServer"" run?

The name InternalTrainServer"" carries no gather rate. 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. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.

Which map has InternalTrainServer"" selected?

The game generates its map: procedural, on InternalTrainServer"".

Wipes and dates

When does InternalTrainServer"" wipe, and how often?

InternalTrainServer"" wipes on no fixed rhythm, so there is nothing to predict. 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 10 hours ago.

What is wipe day on InternalTrainServer"" like?

Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.

Lists and tags

Where does InternalTrainServer"" appear among Rust Data lists and filters?

The Rust Data lists that InternalTrainServer"" 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; Last wipe: In the last 24 hours.

How should you read the server tags on InternalTrainServer""?

The game's server browser reads these tags from InternalTrainServer"": gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. 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.

How to join

How can I connect to InternalTrainServer""?

Enter client.connect 87.151.212.210: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?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players 10 slots in total.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Build number: 168909.
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 34,072 players 11,598 servers online