Rust Data

rustdata.spaceservers51.81.48.22:28045.ipynb

Run all rust-data · live

‹ All servers

Online 51.81.48.22:28044 checked 12m ago

PUBLIC

modded

Connect

srv = rust.server("51.81.48.22:28045")
print(srv.connect_command)

Right now

srv.summary()
players now 2/100 # 2% full
7-day average 1 # peak 29
rank #3,380 # top 15%
last wipe 3h ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeakWipe
01020304005:0013:0022:0006:0015:0003:00Wiped Wed 28 Oct, 16:09 UTCWIPEWiped Wed 28 Oct, 22:39 UTCWIPE

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
Server fpsWipe
05010015020005:0013:0022:0006:0015:0003:00Wiped Wed 28 Oct, 16:09 UTCWIPEWiped Wed 28 Oct, 22:39 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 14 Oct. 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
12k4k6k8k14 Oct17 Oct20 Oct23 Oct26 Oct29 Oct

Top 15% 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 gap3.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak20players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Thu 22 OctWed 21 OctThu 15 Oct
05101520+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 20, 11 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 28 Oct, 22:39 UTC5h ago NaN NaN running 12
1 Wed 28 Oct, 16:09 UTC12h ago NaN NaN NaN 0
2 Thu 22 Oct, 03:24 UTC7d ago 20 halved by day 1 6.5 days 2
3 Wed 21 Oct, 18:57 UTC7d ago 23 NaN 0.4 days 0
4 Thu 15 Oct, 01:48 UTC14d ago 18 halved by day 1 6.7 days 2

# 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

5000 · seed 1228719711
Map of PUBLIC
map
Custom Map
size
5000
seed
1228719711

Server

srv.info()
address
51.81.48.22:28044
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
29 Oct 2026, 00:34 UTC
hostname
–
first seen
14 Oct 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 · 153 on average34/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average124/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 · 93 on average11/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average1/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average2/1000

Quick answers

From the figures on this page.

Population

How does PUBLIC compare in the rankings?

Over the last seven days PUBLIC sits at #3,380 on player hours, in the top 15% of ranked servers.

How full does PUBLIC run?

Current row: 2 players on PUBLIC, against 100 slots. Over the last seven days it averaged 1 players and peaked at 29. Peak hour in the last 48 hours: 23:00 UTC, mean 22 players.

Server data

How well does PUBLIC perform?

The 48-hour average is 130 server fps, with a low of 68. The entity count peaked at 1,058,128, covering buildings, deployables and the rest of the world. A high of 5,868 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

Which Rust version is PUBLIC on?

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

How reliable is PUBLIC, and is it up?

Online is the state at the latest refresh for PUBLIC. A restart about 2 hours ago is what its reported uptime implies. Uptime of 98% across the last 7 full days: 164 hours of 168. Its earliest recorded date in Rust Data is 14 October 2026.

In which location is PUBLIC hosted?

For PUBLIC, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 51.81.48.22:28044.

Settings and map

Which rules apply on PUBLIC, and what settings?

The name PUBLIC carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. VAC is running: Valve's anti-cheat is on.

Which map has PUBLIC selected?

Size 5,000, seed 1228719711: the procedural map on PUBLIC, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Under map name you will find: Custom Map.

Wipe schedule

When does PUBLIC wipe, and on what schedule?

PUBLIC wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 3 hours ago, and that is the one in play.

On PUBLIC, what happens on wipe day?

The average peak over recent wipes is 20 players. 11 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 1 in the other cases.

Lists and tags

Where does PUBLIC appear among Rust Data lists and filters?

These Rust Data lists include PUBLIC: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z; Group limit: 5 or more; Last wipe: In the last 24 hours.

How should you read the server tags on PUBLIC?

The game's server browser reads these tags from PUBLIC: gmrust (Game mode): Survival play, standard Rust; mp100 (Max players): The server lists 100 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 PUBLIC?

Enter client.connect 51.81.48.22:28044 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,^z

Game

gmrust
Game mode Survival play, standard Rust.
mp100
Max players The server lists 100 slots.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$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.

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 32,618 players 11,652 servers online