Rust Data

rustdata.spaceservers24.113.60.221:28017.ipynb

Run all rust-data · live

‹ All servers

Online 24.113.60.221:28015 checked 10m ago

Test

moddedcarbon

Connect

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

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak 2
rank #7,682 # top 35%
last wipe 20h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
00.511.5203:0007:0010:0014:0017:0022:00Wiped Wed 28 Oct, 03:08 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
05010015020003:0007:0010:0014:0017:0022:00Wiped Wed 28 Oct, 03:08 UTCWIPE

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 27 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
15k10k15k20k27 Sep3 Oct9 Oct16 Oct22 Oct28 Oct

Top 35% 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 gap13 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak4players, last three wipes
crowd held50%else halves by day 8

The first 48 hours of its last wipes

Sun 11 OctFri 2 Oct
01234+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 28 Oct, 03:08 UTC20h ago NaN NaN running 0
1 Sun 11 Oct, 03:49 UTC17d ago 3 halved by day 8 17 days 3
2 Fri 2 Oct, 04:27 UTC26d ago 5 held half 9 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 62803
Map of Test
map
Procedural Map
size
4500
seed
62803
Open on RustMaps

Server

srv.info()
address
24.113.60.221:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
28 Oct 2026, 03:08 UTC
hostname
–
first seen
27 Sep 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 157 on average55/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average123/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average46/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average54/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average7/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average8/1000

Quick answers

From the figures on this page.

Player counts

How does Test compare in the rankings?

Over the last seven days Test sits at #7,682 on player hours, in the top 35% of ranked servers.

What population does Test carry?

The sample now reads 0 players for Test, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 2. The 48-hour sample puts the busiest hour at 05:00 UTC, averaging 2 players.

About the server

What does performance look like on Test?

Server fps over the last 48 hours averages 153; the floor is 113. The entity count peaked at 119,613, covering buildings, deployables and the rest of the world. A high of 4,516 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What is the Rust version on Test?

Version Rust network protocol 2635 and build 168909 on Windows is reported by Test. The protocol has to match before you can join, and Steam does the updating.

How reliable is Test, and is it online now?

Online is the state at the latest refresh for Test. A restart about 18 hours ago is what its reported uptime implies. Uptime of 59% across the last 7 full days: 99 hours of 168. Its earliest recorded date in Rust Data is 27 September 2026.

Which location does Test run from?

There is no region published for Test. Rust Data does not look up where the machine stands; it shows where a server says it is. 24.113.60.221:28015 is its address.

Rules, settings, map

What rules and settings are recorded for Test?

You will not find a gather rate in the string Test. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.

What is the map on Test?

The game generates the map on Test: procedural, size 4,500, seed 62803. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does Test wipe, and on what schedule?

Test wipes on no fixed rhythm, so there is nothing to predict. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 20 hours ago, and that is the one in play.

On Test, what happens on wipe day?

Across recent wipes the busiest point averaged 4 players. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 50% of recent wipes. The drop under half arrived by day 8 in the other cases.

Lists and tags

Which Rust Data filters and lists contain Test?

The Rust Data lists that Test fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.

Which meanings do the tags on Test hold?

Read by the game's server browser, the tags Test publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; 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): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way to join Test?

Enter client.connect 24.113.60.221: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 mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players The server lists 50 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
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 The region field is empty.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon Runs on Carbon for plugins.

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 53,534 players 11,735 servers online