Rust Data

rustdata.spaceservers133.88.119.159:28017.ipynb

Run all rust-data · live

‹ All servers

Online 133.88.119.159:28015 checked 11m ago

RustServer_17001

Connect

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

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
00.250.50.75111:0020:0005:0013:0023:0008:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
025507510011:0020:0005:0013:0023:0008: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 25 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
15k10k15k20k25 Sep2 Oct9 Oct15 Oct22 Oct29 Oct

Top 68% 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 gap2.4 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 2 OctThu 1 OctMon 28 Sep
00.250.50.751+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, 09:30 UTC27d ago 1 NaN running 0
1 Thu 1 Oct, 09:25 UTC28d ago 1 NaN 1 days 0
2 Mon 28 Sep, 10:13 UTC30d ago 1 held half 3 days 0
3 Sat 26 Sep, 01:47 UTC33d ago 2 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

4000 · seed 2026680033
Map of RustServer_17001
map
Procedural Map
size
4000
seed
2026680033
Open on RustMaps

Server

srv.info()
address
133.88.119.159:28015
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 09:30 UTC
hostname
–
first seen
25 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 · 519 on average368/400
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average328/350
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average34/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 276 on average34/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 275 on average48/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 244 on average166/200

Quick answers

From the figures on this page.

Population data

How does RustServer_17001 compare in the rankings?

Over the last seven days RustServer_17001 sits at #15,178 on player hours, in the top 68% of ranked servers.

How many players does RustServer_17001 hold at once?

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

About the server

What does performance look like on RustServer_17001?

The 48-hour average is 69 server fps, with a low of 41. Buildings, deployables and all else in the world took the count as high as 93,460 entities. The memory field tops out at 2,842 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is RustServer_17001 on?

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

Is RustServer_17001 up, and what does its uptime show?

Online is the state at the latest refresh for RustServer_17001. A restart about 2 days 13 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 145 of 168, 86%. Its earliest recorded date in Rust Data is 25 September 2026.

Which location does RustServer_17001 run from?

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

Settings and map

Which settings and rules does RustServer_17001 run?

No gather rate appears in the name: RustServer_17001. 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. Combat and raiding between players: both allowed. The server browser lists it under Community. Anti-cheat status: VAC on.

What is the map on RustServer_17001?

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

Wipe data

On what schedule does RustServer_17001 wipe?

No next wipe can be predicted for RustServer_17001, which wipes at irregular times. 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 27 days ago, and that is the one in play.

What is wipe day on RustServer_17001 like?

Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 1 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Tags and filters

Where does RustServer_17001 appear among Rust Data lists and filters?

The Rust Data lists that RustServer_17001 fits are: Rust community servers, unfiltered. These filters bring it up 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_17001?

These tags are published by RustServer_17001 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $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.

How to join

What is the way to join RustServer_17001?

The manual route: launch Rust, F1, then client.connect 133.88.119.159: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 50 slots in total.
ts8
Group limit Team limit of 8, as shipped by default.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$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 53,885 players 11,698 servers online