Rust Data

rustdata.spaceservers51.38.155.251:28952.ipynb

Run all rust-data · live

‹ All servers

Online 51.38.155.251:28951 checked 10m ago

blahblahblah

moddedoxide

Connect

srv = rust.server("51.38.155.251:28952")
print(srv.connect_command)

Right now

srv.summary()
players now 0/75 # 0% full
7-day average 0 # peak 4
rank #6,059 # top 27%
last wipe 5d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5219:0004:0013:0022:0007:0016:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
010020030040019:0004:0013:0022:0007:0016: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 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
15k10k15k20k17 Oct19 Oct22 Oct24 Oct27 Oct29 Oct

Top 27% 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 gap1.2 daysbetween real wipes
on rhythm40%of its recent wipes
wipe-day peak3players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sun 25 OctSat 24 OctThu 22 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 25 Oct, 17:36 UTC4d ago 2 NaN running 1
1 Sat 24 Oct, 12:32 UTC5d ago 2 NaN 1.2 days 1
2 Thu 22 Oct, 15:35 UTC7d ago 4 NaN 1.9 days 0
3 Wed 21 Oct, 12:59 UTC8d ago 4 NaN 1.1 days 0
4 Tue 20 Oct, 21:56 UTC8d ago 4 NaN 0.6 days 0
5 Sun 18 Oct, 11:39 UTC11d ago 1 held half 2.4 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

1000 · seed 50000
Map of blahblahblah
map
Custom Map
size
1000
seed
50000

Server

srv.info()
address
51.38.155.251:28951
region
–
max players
75
group limit
8, the default
wipe schedule
–
last wipe
24 Oct 2026, 16:02 UTC
hostname
–
first seen
17 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 · 151 on average144/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average133/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average198/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 95 on average83/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 89 on average227/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 84 on average346/350

Quick answers

From the figures on this page.

Population

How does blahblahblah compare in the rankings?

Player hours over seven days put blahblahblah at #6,059, in the top 27% of the ranked set.

How many players does blahblahblah hold at once?

The sample now reads 0 players for blahblahblah, out of 75 slots. Over the last seven days it averaged 0 players and peaked at 4. The 48-hour sample puts the busiest hour at 20:00 UTC, averaging 1 players.

About the server

What does performance look like on blahblahblah?

Averaged over 48 hours: 239 server fps, never under 233. Entity numbers reached 6,046, and that includes buildings, deployables and the rest. A high of 2,548 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on blahblahblah?

The build is Rust network protocol 2635 and build 168909 on Linux, run by blahblahblah. Joining needs the same protocol on your game; Steam handles the update.

Is blahblahblah up, and what does its uptime show?

Online is the state at the latest refresh for blahblahblah. A restart about 4 hours ago is what its reported uptime implies. 115 of 168 hours up over the last 7 full days, or 68%. Rust Data logged it first on 17 October 2026.

Which location does blahblahblah run from?

For blahblahblah, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 51.38.155.251:28951 is its address.

Rules, settings, map

What rules and settings are recorded for blahblahblah?

You will not find a gather rate in the string blahblahblah. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.

Which map has blahblahblah selected?

Size 1,000, seed 50000: the procedural map on blahblahblah, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: Custom Map.

Wipe data

When does blahblahblah wipe, and on what schedule?

blahblahblah 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 5 days 2 hours ago, and that is the one in play.

On blahblahblah, what happens on wipe day?

Recent wipes averaged 3 players at their peak. 3 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.

Tags, lists

Where does blahblahblah appear among Rust Data lists and filters?

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

Which meanings do the tags on blahblahblah hold?

These tags are published by blahblahblah and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp75 (Max players): 75 slots in total; 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): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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.

Join steps

What is the way to join blahblahblah?

In Rust, F1 opens the console: type client.connect 51.38.155.251:28951. 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 mp75,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival play, standard Rust.
mp75
Max players 75 slots in total.
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 The server runs build 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^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 102,658 players 11,891 servers online