Rust Data

rustdata.spaceservers197.94.46.29:28016.ipynb

Run all rust-data · live

‹ All servers

Online 197.94.46.29:28015 checked 9m ago

My Rust server | Powered by AMP

Connect

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

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak 1
rank #13,774 # top 62%
last wipe 1d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.250.50.75104:0013:0023:0008:0017:0002:00Wiped Mon 26 Oct, 17:00 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 62% 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 gap4.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Fri 2 OctTue 29 SepTue 22 Sep
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 Mon 26 Oct, 17:00 UTC1d ago NaN NaN running 0
1 Fri 2 Oct, 07:24 UTC25d ago 1 halved by day 1 24.4 days 0
2 Tue 29 Sep, 18:46 UTC28d ago 1 halved by day 1 2.5 days 0
3 Tue 22 Sep, 11:53 UTC35d ago 1 halved by day 1 7.3 days 0
4 Mon 21 Sep, 18:15 UTC36d ago 1 NaN 0.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
197.94.46.29:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
26 Oct 2026, 17:00 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 · 530 on average231/250
1Rustoria.co - EU MainEU · groups of 16+ · weekly · 329 on average14/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 327 on average22/250
3Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average114/200
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 279 on average46/200
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 264 on average42/100

Quick answers

From the figures on this page.

Population

What position does My Rust server | Powered by AMP take in the server rankings?

Over the last seven days My Rust server | Powered by AMP sits at #13,774 on player hours, in the top 62% of ranked servers.

How many players does My Rust server | Powered by AMP hold at once?

My Rust server | Powered by AMP reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 18:00 UTC, averaging 1 players.

Server data

What Rust version does My Rust server | Powered by AMP run?

Version Rust network protocol 2635 and build 168909 on Linux is reported by My Rust server | Powered by AMP. The protocol has to match before you can join, and Steam does the updating.

How reliable is My Rust server | Powered by AMP, and is it up?

My Rust server | Powered by AMP reports itself online at the current refresh. Over the last 7 full days the hours up number 148 of 168, 88%. Rust Data logged it first on 20 September 2026.

Where does My Rust server | Powered by AMP sit?

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

Map and rules

Which rules apply on My Rust server | Powered by AMP, and what settings?

The name My Rust server | Powered by AMP carries no gather rate. No custom cap; the default of 8 players per group stands. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.

Which map has My Rust server | Powered by AMP selected?

My Rust server | Powered by AMP runs a procedural map, which the game generates.

Wipe schedule

When does My Rust server | Powered by AMP wipe, and how often?

No next wipe can be predicted for My Rust server | Powered by AMP, which wipes at irregular times. 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 34 hours ago.

What is wipe day on My Rust server | Powered by AMP like?

The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 1.

Lists and tags

Which lists on Rust Data hold My Rust server | Powered by AMP, and which filters?

These Rust Data lists include My Rust server | Powered by AMP: 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.

Which meanings do the tags on My Rust server | Powered by AMP hold?

The game's server browser reads these tags from My Rust server | Powered by AMP: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

Connecting

What is the way into My Rust server | Powered by AMP?

The manual route: launch Rust, F1, then client.connect 197.94.46.29:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players The server lists 100 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is 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 37,139 players 11,636 servers online