Skip to the page
Network live 11,687 servers online 50,243 players aboard 134 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

InternalTrainServer""

Online 87.151.212.210:28015 checked 13m ago

Tracking number · connect
Wipe progress · wiped 5h ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA –no rhythm it keeps
0/ 10 players now 0% full
07-day averagepeak –
#15,414ranktop 69%
5h agolast wipeno schedule published
–next wipeno rhythm it keeps
Delivery history

Players, performance and rank

Players

AveragePeakWipe
0123401:0010:0019:0005:0014:0023:00Wiped Tue 27 Oct, 19:08 UTCWIPE

Hourly average and peak, UTC.

Server performance

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
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

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

5.2 daysusual gapbetween real wipes
0%on rhythmof its recent wipes
0wipe-day peakplayers, 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

every wipe as a delivery, newest first
  1. Tue 27 Oct, 19:08 UTC 19:08 UK · 5h ago
    Wipe delivered
    Peak
    –
    Crowd
    –
    Lasted
    running
    Players before
    0
  2. Thu 8 Oct, 18:52 UTC 19:52 UK · 19d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    19 days
    Players before
    0
  3. Sun 4 Oct, 18:21 UTC 19:21 UK · 23d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    4 days
    Players before
    0
  4. Fri 2 Oct, 15:53 UTC 16:53 UK · 25d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    2.1 days
    Players before
    0
  5. Thu 1 Oct, 19:06 UTC FW 20:06 UK · 26d ago
    Force wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    0.9 days
    Players before
    0
  6. Fri 25 Sep, 11:44 UTC 12:44 UK · 32d ago
    Wipe delivered
    Peak
    0
    Crowd
    –
    Lasted
    6.3 days
    Players before
    0
  7. Thu 17 Sep, 18:11 UTC 19:11 UK · 40d ago
    Wipe delivered
    Peak
    1
    Crowd
    halved by day 3
    Lasted
    7.7 days
    Players before
    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.

Similar parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 524 on average 363 / 425
  2. Rustoria.co - EU MainEU · groups of 16+ · weekly · 334 on average 25 / 250
  3. Rusty Moose |EU Main|EU · groups of 12+ · weekly · 331 on average 44 / 250
  4. Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average 168 / 200
  5. Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 279 on average 67 / 200
  6. Rustafied.com - EU FridayEU · groups of 16+ · weekly · 263 on average 70 / 100
Help desk

Quick answers

From the figures on this page.

Player count

How does InternalTrainServer"" compare with other Rust servers in the rankings?

In the top 69% of all ranked servers sits InternalTrainServer"", at #15,414 on hours played over seven days.

What is the current population on InternalTrainServer""?

The current count is 0 players on 10 slots for InternalTrainServer"". For the last seven days the average player count was 0.

Rules and settings

Which map is active on InternalTrainServer""?

The map on InternalTrainServer"" is procedural, produced by the game.

What settings and rules should you know for InternalTrainServer""?

The name of InternalTrainServer"" gives no gather rate. The game's default applies: 8 players to a group at most. It runs survival, the usual game: build, gather, raid. Raiding and PvP are both on. It appears in the server browser under Community, being a community server. The VAC anti-cheat from Valve is enabled.

Server details

In which region is InternalTrainServer"" based?

No region is published by InternalTrainServer"". Rust Wipe Tracker takes the location a server states and shows it, without looking up where the machine actually stands. The address to connect to is 87.151.212.210:28015.

What is the uptime of InternalTrainServer"", and is it online?

You can find InternalTrainServer"" online at present. 100% is the uptime for the last 7 full days, up for 168 of 168 hours. The first sighting of it by Rust Wipe Tracker came on 13 September 2026.

On what Rust version does InternalTrainServer"" operate?

Rust network protocol 2635 and build 168909 on Linux is what InternalTrainServer"" runs. The same protocol is required to join, and Steam takes care of updating it.

Wipe schedule

How does InternalTrainServer"" handle its wipe days?

0 players is the average peak across its recent wipes. On the latest wipe, 0 hours passed before the crowd peaked.

When does InternalTrainServer"" wipe? What schedule does it follow?

There is no next wipe to predict for InternalTrainServer"": it wipes at irregular times. The monthly force wipe takes every Rust server with it, and Thursday 5 November at 19:00 UTC is the next one. The world it is running was made 5 hours.

Tags and filters

Where does InternalTrainServer"" appear across the Rust Wipe Tracker lists and filters?

The Rust Wipe Tracker lists that include InternalTrainServer"" are: Rust community servers, unmodded. On the server list, apply Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 24 hours and it appears.

How should you read the tags on InternalTrainServer""?

The game's server browser picks up these InternalTrainServer"" tags: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): The server has 10 slots; ts8 (Group limit): The game default caps teams at 8; v2635 (Protocol): Protocol 2635 is required; a different version can't join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles networking, as standard for the game; $r? (Region code): The region code is unset. You will find its live player count, its queue and its world's age in the tags, shown at the top of this page.

Connecting

How do you connect to InternalTrainServer""?

Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 87.151.212.210:28015.

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players The server has 10 slots.
ts8
Group limit The game default caps teams at 8.
v2635
Protocol Protocol 2635 is required; a different version can't join.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet handles networking, as standard for the game.
$r?
Region code The region code is unset.

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.