Rust Data

rustdata.spaceservers91.52.67.130:28017.ipynb

Run all rust-data · live

‹ All servers

Offline 91.52.67.130:28015 checked 26d ago

Custom Aim Train

Connect

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

Right now

srv.summary()
players now 0/10 # 0% full · 1 in queue
7-day average 0 # peak –
rank #16,019 # top 69%
last wipe 26d ago # no schedule published
next wipe 8d 20h # Thu 5 Nov, 19:00 UTC FW

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
15k10k15k20k1 Oct2 Oct4 Oct5 Oct7 Oct8 Oct

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

Wipe schedule · force wipes only

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 8d 20h. # The force wipe · high confidence

wipe-day peak0players, last three wipes

Coming wipes

inatkind
08d 20hThu 5 Nov, 19:00 UTCFW force wipe
136d 20hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 18:14 UTC FW26d ago 0+1 queue NaN running 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
91.52.67.130:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 18:14 UTC
hostname
–
first seen
1 Oct 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0NA | Apex Aim Arena | 1v1 Facecheck FFA TargetsNA · groups of 8+ · 4 on average0/16
1Q1 - Aim Training / Matchmaking / Facechecks - EU MainEU · groups of 8+ · 4 on average0/16
2EU | Deadzone Aimtrain | Facechecks/1v1/SpeargunEU · groups of 8+ · 4 on average0/16
3Deadshot's Arena | NA | BedWars | Aim Train | Scrim | Gun GameNA · groups of 8+ · 4 on average0/16
4・RUST KILL・XXX|KILL $ CASH|FARM|SHOP|TP|HOME|KITS|PVPVEX10Xgroups of 10+ · weekly · 5 on average3/100
5PLUKN - US Monument/Oil Rig | Practice, Aimtrain, PVPNA · groups of 8+ · 5 on average2/10

Quick answers

From the figures on this page.

Population

Against other Rust servers, how does Custom Aim Train rank?

Over the last seven days Custom Aim Train sits at #16,019 on player hours, in the top 69% of ranked servers.

How many players does Custom Aim Train hold at once?

The current row shows Custom Aim Train offline; the last response was 26 days 1 hours ago.

Server data

Which Rust version is Custom Aim Train on?

Rust network protocol 2634 and build 166494 on Windows is what Custom Aim Train runs. Steam updates your game for you, but the protocol must match to join.

Is Custom Aim Train up, and what does its uptime show?

Offline now for Custom Aim Train, last seen 26 days 1 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 1 October 2026.

Where does Custom Aim Train sit?

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

Rules, settings, map

Which settings and rules does Custom Aim Train run?

The name Custom Aim Train carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. The server browser lists it under Community. VAC is not running; Valve's anti-cheat is off.

Which map has Custom Aim Train loaded?

A procedural map runs on Custom Aim Train, generated by the game.

Wipe data

When does Custom Aim Train wipe, and how often?

The only wipe Custom Aim Train takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 26 days 4 hours ago.

What is wipe day on Custom Aim Train like?

Across recent wipes the busiest point averaged 0 players. On the latest wipe the peak came 0 hours after the wipe, with a queue of 1.

Lists and tags

Which lists on Rust Data hold Custom Aim Train, and which filters?

On Rust Data, Custom Aim Train appears in these lists: Rust aim training servers and 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.

Which meanings do the tags on Custom Aim Train hold?

The game's server browser reads these tags from Custom Aim Train: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166494 (Build): Build number: 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $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.

How to join

How can I connect to Custom Aim Train?

In Rust, F1 opens the console: type client.connect 91.52.67.130: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?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit The default cap applies: 8 per team.
v2634
Protocol Protocol 2634 is required; a different game version cannot connect.
cs166494
Build Build number: 166494.
ptrak
Networking Standard network layer for Rust: RakNet.
$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 63,128 players 11,755 servers online