Rust Data

rustdata.spaceservers153.68.126.170:28016.ipynb

Run all rust-data · live

‹ All servers

Online 153.68.126.170:28015 checked 4m ago

RustDockerServer

Connect

srv = rust.server("153.68.126.170:28016")
print(srv.connect_command)

Right now

srv.summary()
players now 0/10 # 0% full
7-day average 0 # peak –
rank #15,339 # top 69%
last wipe 24d ago # no schedule published
next wipe – # too few wipes seen yet

Players

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

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020023:0008:0017:0002:0011: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 20 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 Sep5 Oct13 Oct20 Oct28 Oct

Top 69% 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 peak0players, last three wipes

The first 48 hours of its last wipes

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sun 4 Oct, 07:17 UTC24d ago 0 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

4500 · seed 1337
Map of RustDockerServer
map
Procedural Map
size
4500
seed
1337
Open on RustMaps

Server

srv.info()
address
153.68.126.170:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
4 Oct 2026, 07:17 UTC
hostname
–
first seen
20 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 · 554 on average416/500
1Rustoria.co - EU East LongEU · groups of 12+ · monthly · 318 on average277/300
2Rusty Moose |EU Main|EU · groups of 12+ · weekly · 295 on average42/250
3Rustoria.co - EU MainEU · groups of 16+ · weekly · 294 on average35/250
4Rustafied.com - EU FridayEU · groups of 16+ · weekly · 273 on average75/100
5Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 252 on average94/200

Quick answers

From the figures on this page.

Population data

Against other Rust servers, how does RustDockerServer rank?

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

What population does RustDockerServer carry?

The sample now reads 0 players for RustDockerServer, out of 10 slots. Over the last seven days it averaged 0 players.

About the server

How smoothly does RustDockerServer run?

The 48-hour average is 159 server fps, with a low of 141. Buildings, deployables and all else in the world took the count as high as 121,005 entities. Memory peaked at 3,883 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is RustDockerServer on?

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

Is RustDockerServer up, and what does its uptime show?

RustDockerServer reports itself online at the current refresh. A restart about 3 days 8 hours ago is what its reported uptime implies. Over the last 7 full days the hours up number 168 of 168, 100%. Its earliest recorded date in Rust Data is 20 September 2026.

In which location is RustDockerServer hosted?

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

Rules, settings, map

What rules and settings are recorded for RustDockerServer?

You will not find a gather rate in the string RustDockerServer. Eight players per group: that is the game's default, and it applies here. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.

What is the map on RustDockerServer?

RustDockerServer runs a procedural map of size 4,500 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipes and dates

On what schedule does RustDockerServer wipe?

The record for RustDockerServer 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. This world was created 24 days 15 hours ago.

What is wipe day on RustDockerServer like?

Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.

Tags, lists

Which Rust Data filters and lists contain RustDockerServer?

On Rust Data, RustDockerServer appears in these lists: 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.

Which meanings do the tags on RustDockerServer hold?

These tags are published by RustDockerServer and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 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): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. 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 RustDockerServer?

Enter client.connect 153.68.126.170: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 mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Rust survival in its standard form.
mp10
Max players 10 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 The network layer is RakNet, standard for the game.
$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 60,429 players 11,767 servers online