Rust Data

rustdata.spaceservers24.216.36.70:28016.ipynb

Run all rust-data · live

‹ All servers

Online 24.216.36.70:28015 checked 12m ago

My Rust server | Powered by AMP

Connect

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

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak 1
rank #15,270 # top 69%
last wipe 24d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123414:0023:0008:0018:0003:0012:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020014:0023:0008:0018:0003:0012: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 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

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

Wipe schedule · too few wipes seen yet

srv.wipe_schedule()

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap8.5 daysbetween real wipes
wipe-day peak0players, last three wipes
crowd held0%else halves by day 2

The first 48 hours of its last wipes

Sun 4 OctFri 25 Sep
00.250.50.751+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 Sun 4 Oct, 04:35 UTC24d ago 0 NaN running 0
1 Fri 25 Sep, 16:03 UTC32d ago 1 halved by day 2 8.5 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 6738
Map of My Rust server | Powered by AMP
map
Procedural Map
size
4500
seed
6738
Open on RustMaps

Server

srv.info()
address
24.216.36.70:28015
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
4 Oct 2026, 04:35 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 · 543 on average673/725
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average433/475
2Rustoria.co - EU MainEU · groups of 16+ · weekly · 308 on average40/250
3Rusty Moose |EU Main|EU · groups of 12+ · weekly · 308 on average54/250
4Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 268 on average234/250
5Rustafied.com - EU FridayEU · groups of 16+ · weekly · 266 on average130/175

Quick answers

From the figures on this page.

Player counts

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

Rank #15,270 on seven-day player hours for My Rust server | Powered by AMP, within the top 69% of all ranked servers.

What population does My Rust server | Powered by AMP carry?

The sample now reads 0 players for My Rust server | Powered by AMP, out of 100 slots. Over the last seven days it averaged 0 players and peaked at 1.

Server data

How smoothly does My Rust server | Powered by AMP run?

The 48-hour average is 133 server fps, with a low of 83. Buildings, deployables and all else in the world took the count as high as 111,765 entities. A high of 4,483 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

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?

The current sample puts My Rust server | Powered by AMP online. A restart about 5 days 17 hours ago is what its reported uptime implies. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.

Where does My Rust server | Powered by AMP sit?

No region is published by My Rust server | Powered by AMP. Rust Data does not look up where the machine stands; it shows where a server says it is. 24.216.36.70:28015 is its address.

Rules, settings, map

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

You will not find a gather rate in the string My Rust server | Powered by AMP. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.

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

Size 4,500, seed 6738: the procedural map on My Rust server | Powered by AMP, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

On what schedule does My Rust server | Powered by AMP wipe?

A rhythm cannot be read from the wipes of My Rust server | Powered by AMP on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 24 days 8 hours ago.

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

The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 2.

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. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How should you read the server tags on My Rust server | Powered by AMP?

These tags are published by My Rust server | Powered by AMP and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Team limit of 8, as shipped by default; 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.

Connecting

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

Enter client.connect 24.216.36.70: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 mp100,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players The server lists 100 slots.
ts8
Group limit Team limit of 8, as shipped by default.
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 74,144 players 11,744 servers online