Rust Data

rustdata.spaceservers133.88.106.75:28017.ipynb

Run all rust-data · live

‹ All servers

Online 133.88.106.75:28015 checked 10m ago

RustServer_5018

Connect

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

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 1 # peak 6
rank #3,855 # top 17%
last wipe 5d ago # no schedule published
next wipe – # too few wipes seen yet

Players

srv.players.plot(range="48h")
AveragePeak
0123423:0008:0017:0003:0012:0021:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020023:0008:0017:0003:0012:0021: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 24 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
12k4k6k8k24 Oct25 Oct26 Oct27 Oct28 Oct29 Oct

Top 17% 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.

wipe-day peak6players, last three wipes

The first 48 hours of its last wipes

02468+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 23 Oct, 23:48 UTC5d ago 6 NaN running 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 22314
Map of RustServer_5018
map
Procedural Map
size
3000
seed
22314
Open on RustMaps

Server

srv.info()
address
133.88.106.75:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
23 Oct 2026, 23:48 UTC
hostname
–
first seen
23 Oct 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 · 503 on average159/250
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average184/250
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 282 on average604/675
3Rustafied.com - EU FridayEU · groups of 16+ · weekly · 277 on average37/100
4Rustoria.co - EU MainEU · groups of 16+ · weekly · 266 on average687/775
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 245 on average561/625

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does RustServer_5018 rank?

Player hours over seven days put RustServer_5018 at #3,855, in the top 17% of the ranked set.

How full does RustServer_5018 run?

The sample now reads 0 players for RustServer_5018, out of 50 slots. Over the last seven days it averaged 1 players and peaked at 6. Averaged by hour over 48 hours, 10:00 UTC is the busiest, at 3 players.

About the server

What does performance look like on RustServer_5018?

The 48-hour average is 103 server fps, with a low of 65. Entity numbers reached 50,943, and that includes buildings, deployables and the rest. A high of 2,595 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.

What Rust version does RustServer_5018 run?

Version Rust network protocol 2635 and build 168909 on Linux is reported by RustServer_5018. Joining needs the same protocol on your game; Steam handles the update.

Is RustServer_5018 up, and what does its uptime show?

RustServer_5018 reports itself online at the current refresh. A restart about 5 days 21 hours ago is what its reported uptime implies. Uptime of 99% across the last 5 full days: 119 hours of 120. The first row Rust Data holds for it is dated 23 October 2026.

Which location does RustServer_5018 run from?

There is no region published for RustServer_5018. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 133.88.106.75:28015 is its address.

Settings and map

Which settings and rules does RustServer_5018 run?

You will not find a gather rate in the string RustServer_5018. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Community is its browser category. Anti-cheat status: VAC on.

What is the map on RustServer_5018?

Size 3,000, seed 22314: the procedural map on RustServer_5018, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does RustServer_5018 wipe, and on what schedule?

The record for RustServer_5018 holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 5 days 23 hours ago.

What is wipe day on RustServer_5018 like?

Across recent wipes the busiest point averaged 6 players. 31 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which Rust Data filters and lists contain RustServer_5018?

On Rust Data, RustServer_5018 appears in these lists: 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; Last wipe: In the last week.

Which meanings do the tags on RustServer_5018 hold?

Read by the game's server browser, the tags RustServer_5018 publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Connecting

What is the way into RustServer_5018?

Enter client.connect 133.88.106.75: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

Game

gmrust
Game mode Rust survival in its standard form.
mp50
Max players The server lists 50 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol The server speaks protocol 2635, so match your game version.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code The region field is empty.

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 75,264 players 11,770 servers online