Rust Data

rustdata.spaceservers168.100.162.11:28088.ipynb

Run all rust-data · live

‹ All servers

Online 168.100.162.11:28085 checked 6m ago

training_grounds

vanilla

Connect

srv = rust.server("168.100.162.11:28088")
print(srv.connect_command)

Right now

srv.summary()
players now 0/?
7-day average 0 # peak –
rank #15,335 # top 69%
last wipe 16d ago # no schedule published
next wipe – # no rhythm it keeps
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123415:0003:0005:0008:0010:0013:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
01020304015:0003:0005:0008:0010:0013:00

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, measured since 17 Sep. 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 Sep27 Sep5 Oct12 Oct20 Oct29 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 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Mon 12 OctWed 7 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Mon 12 Oct, 15:25 UTC16d ago 1 NaN running 0
1 Wed 7 Oct, 15:39 UTC21d ago 0 NaN 5 days 0
2 Thu 1 Oct, 16:59 UTC27d ago 0 NaN 5.9 days 0
3 Mon 28 Sep, 14:32 UTC31d ago 1+1 queue NaN 3.1 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

4500 · seed 245503461
Map of training_grounds
map
Rustafied Custom Map
size
4500
seed
245503461
custom map
download

Server

srv.info()
address
168.100.162.11:28085
region
–
max players
–
group limit
16 max
wipe schedule
–
last wipe
12 Oct 2026, 15:25 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 · 514 on average531/575
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average430/475
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 290 on average274/250
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average58/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 275 on average359/250
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 236 on average393/350

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does training_grounds rank?

Rank #15,335 on seven-day player hours for training_grounds, within the top 69% of all ranked servers.

How many players does training_grounds hold at once?

Point query at this second: training_grounds returns 0 players. Over the last seven days it averaged 0 players.

Server data

How smoothly does training_grounds run?

The 48-hour average is 30 server fps, with a low of 29. The entity count peaked at 137,229, covering buildings, deployables and the rest of the world. The memory field tops out at 3,786 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is training_grounds on?

Rust network protocol 2635 and build 168909 on Linux is what training_grounds runs. Steam updates your game for you, but the protocol must match to join.

How reliable is training_grounds, and is it up?

training_grounds reports itself online at the current refresh. The uptime it reports puts the last restart about 9 hours ago. Over the last 7 full days the hours up number 99 of 168, 59%. Rust Data logged it first on 13 September 2026.

Which location does training_grounds run from?

For training_grounds, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 168.100.162.11:28085.

Settings and map

Which rules apply on training_grounds, and what settings?

You will not find a gather rate in the string training_grounds. Group size tops out at 16 players. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Community is its browser category. Vanilla, by its own description: untouched settings: rates, kits and rules as shipped. Anti-cheat status: VAC on.

Which map has training_grounds selected?

Custom map, 4,500, run by training_grounds; the file is published, so download it here.

Wipe data

On what schedule does training_grounds wipe?

No next wipe can be predicted for training_grounds, which wipes at irregular times. 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 16 days 23 hours ago.

What is wipe day on training_grounds like?

Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 2 hours in.

Tags and filters

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

On Rust Data, training_grounds appears in these lists: Rust community servers, unfiltered, Rust tutorial servers and Vanilla Rust servers. It appears under these filters on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Vanilla ^v and Tutorial on ^t; Group limit: 5 or more.

Which meanings do the tags on training_grounds hold?

These tags are published by training_grounds and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): 0 slots in total; ts16 (Group limit): No team may exceed 16; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^t (Tutorial on): The Facepunch tutorial is open to new players on this server; rustmaps (Custom tag): A plugin or the owner added this; standard Rust does not define it. 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

What is the way into training_grounds?

Enter client.connect 168.100.162.11:28085 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://forum.rustafied.com/store/product/75-sea-medium/.

Server tags · what each one means

srv.tags.decode()

Published as mp0,ptrak,$r?,v2635,^v,^t,gmrust,cs168909,ts16,rustmaps

Game

gmrust
Game mode Rust survival in its standard form.
mp0
Max players 0 slots in total.
ts16
Group limit No team may exceed 16.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Difficulty

^v
Vanilla Untouched settings: rates, kits and rules as shipped.

Gameplay

^t
Tutorial on The Facepunch tutorial is open to new players on this server.

Other

rustmaps
Custom tag A plugin or the owner added this; standard Rust does not define it.

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 84,816 players 11,846 servers online