Rust Server TrendsSeismic network · station log
Recording Stations11,752 Players57,724 Active3,422 Wipes · 3 h129 48 h

Station XX-6708 · recording

LPL-RustDockerServer

Online 134.228.179.43:28015 checked 9m ago

moddedoxide
Connect
Players now
0/ 10
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 1
Rank
#6,708
top 30%
Last wipe
26d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-6708 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 10 slots
Motion · 24 h
M0.0steady+0 players
Channel 1 · calibrated

Players

AveragePeak
0123423:0008:0017:0002:0011:0021:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

02040608023: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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 30% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak
1players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 2 Oct, 11:14 UTC26d ago M0.0rising 1 – running 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 157 on average
66/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
127/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average
63/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 91 on average
55/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
17/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
10/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on LPL-RustDockerServer?

The procedural map on LPL-RustDockerServer is size 4,500 with seed 317670913, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.

Which settings and rules apply on LPL-RustDockerServer?

No gather rate appears in the name of LPL-RustDockerServer. Groups hold up to 8 players, which is the default for the game. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. The server has VAC on, Valve's anti-cheat.

Player counts

What is the current population on LPL-RustDockerServer?

A reading taken now shows 0 players on LPL-RustDockerServer, which has 10 slots. Averaged across the last seven days the population was 0 players, reaching a peak of 1.

How does LPL-RustDockerServer rank against other Rust servers?

The last seven days of player hours place LPL-RustDockerServer at #6,708, in the top 30% of all ranked servers.

Server facts

How reliably does LPL-RustDockerServer stay online?

As recorded now, LPL-RustDockerServer is running. Going by the uptime figure it reports, it restarted about 2 days 15 hours ago. It was up 100% of the time across the last 7 full days: 168 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.

How well does LPL-RustDockerServer perform under load?

Its average server fps over the last 48 hours was 59, and it never dropped below 53. The world held up to 123,861 entities at its peak, buildings and deployables included. Memory use peaked at 4,310 MB. Low fps together with a growing entity count is what players experience as lag.

Which region does LPL-RustDockerServer run from?

Nothing about a region comes from LPL-RustDockerServer. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 134.228.179.43:28015.

Which Rust version is LPL-RustDockerServer running?

LPL-RustDockerServer is running Rust network protocol 2635 and build 168909 on a machine with Linux. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe schedule

What does wipe day look like on LPL-RustDockerServer?

The recent wipes averaged a busiest count of 1 players. 11 hours after the latest wipe, the crowd peaked.

On what timetable does LPL-RustDockerServer run its wipes?

On record so far are too few of LPL-RustDockerServer's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 26 days 11 hours is how long the current world has been running.

Tags

What do the server tags on LPL-RustDockerServer mean?

Tags published by LPL-RustDockerServer and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp10 (Max players): 10 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.

On which Rust Server Trends lists does LPL-RustDockerServer appear?

These Rust Server Trends lists include LPL-RustDockerServer: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How to join

What steps get you onto LPL-RustDockerServer?

Enter client.connect 134.228.179.43:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players 10 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been set.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.