Rust Data

rustdata.spaceservers134.228.179.43:28016.ipynb

Run all rust-data · live

‹ All servers

Online 134.228.179.43:28015 checked 8m ago

LPL-RustDockerServer

moddedoxide

Connect

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

Right now

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

Players

srv.players.plot(range="48h")
AveragePeak
0123421:0006:0015:0001:0010:0019:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02040608021:0006:0015:0001:0010:0019: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 Oct13 Oct21 Oct29 Oct

Top 31% 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 peak1players, last three wipes

The first 48 hours of its last wipes

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Fri 2 Oct, 11:14 UTC27d ago 1 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 317670913
Map of LPL-RustDockerServer
map
Procedural Map
size
4500
seed
317670913
Open on RustMaps

Server

srv.info()
address
134.228.179.43:28015
region
–
max players
10
group limit
8, the default
wipe schedule
–
last wipe
2 Oct 2026, 11:14 UTC
hostname
–
first seen
13 Sep 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 average75/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average126/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average137/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 96 on average44/700
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10EU · groups of 16+ · monthly · 91 on average133/700
5RustSpain.com | EU MainEU · groups of 12+ · weekly · 85 on average348/350

Quick answers

From the figures on this page.

Population data

What position does LPL-RustDockerServer take in the server rankings?

Player hours over seven days put LPL-RustDockerServer at #6,862, in the top 31% of the ranked set.

How full does LPL-RustDockerServer run?

The sample now reads 0 players for LPL-RustDockerServer, out of 10 slots. Over the last seven days it averaged 0 players and peaked at 1.

About the server

What does performance look like on LPL-RustDockerServer?

Server fps over the last 48 hours averages 59; the floor is 56. Buildings, deployables and all else in the world took the count as high as 123,478 entities. The memory field tops out at 4,653 MB. Low fps plus an entity count on the way up is the lag players report.

Which Rust version is LPL-RustDockerServer on?

Version Rust network protocol 2635 and build 168909 on Linux is reported by LPL-RustDockerServer. Steam updates your game for you, but the protocol must match to join.

How reliable is LPL-RustDockerServer, and is it online now?

LPL-RustDockerServer reports itself online at the current refresh. The uptime it reports puts the last restart about 3 days 13 hours ago. 167 of 168 hours up over the last 7 full days, or 99%. Its earliest recorded date in Rust Data is 13 September 2026.

Where does LPL-RustDockerServer sit?

There is no region published for LPL-RustDockerServer. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 134.228.179.43:28015 is its address.

Settings and map

What rules and settings are recorded for LPL-RustDockerServer?

You will not find a gather rate in the string LPL-RustDockerServer. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. Anti-cheat status: VAC on.

What is the map on LPL-RustDockerServer?

Size 4,500, seed 317670913: the procedural map on LPL-RustDockerServer, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.

Wipes and dates

When does LPL-RustDockerServer wipe, and on what schedule?

A rhythm cannot be read from the wipes of LPL-RustDockerServer on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 27 days 9 hours ago, and that is the one in play.

On LPL-RustDockerServer, what happens on wipe day?

Recent wipes averaged 1 players at their peak. 11 hours after the latest wipe, the crowd reached its peak.

Tags, lists

Which lists on Rust Data hold LPL-RustDockerServer, and which filters?

On Rust Data, LPL-RustDockerServer appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on LPL-RustDockerServer?

These tags are published by LPL-RustDockerServer and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.

Join steps

How can I connect to LPL-RustDockerServer?

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

Game

gmrust
Game mode Survival play, standard Rust.
mp10
Max players Slot count: 10.
ts8
Group limit Unchanged from default, teams hold up to 8.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Modded listing: the game is changed by plugins or settings.

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 96,179 players 11,824 servers online