Rust Data

rustdata.spaceservers133.88.120.27:28017.ipynb

Run all rust-data · live

‹ All servers

Online 133.88.120.27:28015 checked 42m ago

RustServer_9257

Connect

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

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,284 # top 69%
last wipe 27d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123402:0011:0021:0005:0014:0023:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020002:0011:0021:0005:0014:0023: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 Sep6 Oct14 Oct22 Oct30 Oct

Top 69% 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 gap8.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 3

The first 48 hours of its last wipes

Fri 2 OctTue 15 SepTue 15 Sep
00.511.52+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 13:47 UTC27d ago 1 NaN running 0
1 Tue 15 Sep, 21:28 UTC44d ago 2 halved by day 3 16.7 days 0
2 Tue 15 Sep, 11:02 UTC44d ago 2 NaN 0.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

3000 · seed 5670
Map of RustServer_9257
map
Procedural Map
size
3000
seed
5670
Open on RustMaps

Server

srv.info()
address
133.88.120.27:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 13:47 UTC
hostname
–
first seen
14 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 · 491 on average84/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average115/200
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 284 on average397/450
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average21/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average476/525
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 253 on average362/425

Quick answers

From the figures on this page.

Player counts

What position does RustServer_9257 take in the server rankings?

Rank #15,284 on seven-day player hours for RustServer_9257, within the top 69% of all ranked servers.

How full does RustServer_9257 run?

RustServer_9257 reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players.

Server data

How well does RustServer_9257 perform?

Server fps over the last 48 hours averages 103; the floor is 86. Entity numbers reached 47,166, and that includes buildings, deployables and the rest. A high of 2,387 MB of memory used. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is RustServer_9257 on?

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

Is RustServer_9257 up, and what does its uptime show?

Online is the state at the latest refresh for RustServer_9257. The uptime it reports puts the last restart about 6 days 1 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. The first row Rust Data holds for it is dated 14 September 2026.

Which location does RustServer_9257 run from?

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

Settings and map

Which settings and rules does RustServer_9257 run?

You will not find a gather rate in the string RustServer_9257. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. The server browser lists it under Community. Anti-cheat status: VAC on.

Which map has RustServer_9257 selected?

The game generates the map on RustServer_9257: procedural, size 3,000, seed 5670. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

When does RustServer_9257 wipe, and on what schedule?

RustServer_9257 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 27 days 11 hours ago, and that is the one in play.

On RustServer_9257, what happens on wipe day?

Recent wipes averaged 2 players at their peak. 1 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 3.

Lists and tags

Which Rust Data filters and lists contain RustServer_9257?

The Rust Data lists that RustServer_9257 fits are: 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.

How should you read the server tags on RustServer_9257?

These tags are published by RustServer_9257 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): Slot count: 50; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

How to join

How can I connect to RustServer_9257?

The manual route: launch Rust, F1, then client.connect 133.88.120.27: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 mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players Slot count: 50.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol Protocol 2635 is required; a different game version cannot connect.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$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 60,014 players 11,706 servers online