On the class lists: C− (58), with population over 48 hours and no performance mark.
Players now0/ 100% full
7-day average0peak 1
Rank#6,881top 31%
Last wipe26d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 0 of 10 on average. Plenty of space to grow.
Standingrank on player hours
69/ 100
C+
Working its way up from the back of the class: #6,881 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
98/ 100
A+
Runs smoothly: 59 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
66/ 100
C+
Climbing fast: up 2,175 places this week.
A steady term.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 31% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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 peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 11 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 11:14 UTC26d ago
1
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for LPL-RustDockerServer. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 134.228.179.43:28015 is the address to use.
How reliable is LPL-RustDockerServer, and is it up?
Right now, LPL-RustDockerServer is online. The uptime it reports puts the last restart at about 2 days 23 hours ago. It was up 99% of the time over the last 7 full days, 167 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
Does LPL-RustDockerServer perform well?
It never fell below 53 server fps in the last 48 hours, averaging 59. At its peak, it held 123,861 entities, including buildings, deployables and all else in the world. Memory use reached up to 4,385 MB. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is LPL-RustDockerServer on?
You will find LPL-RustDockerServer on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does LPL-RustDockerServer wipe, and how often?
There are too few wipes on record for LPL-RustDockerServer to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. It has been running its current world for 26 days 19 hours.
What happens on LPL-RustDockerServer when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 11 hours after the latest wipe began, the crowd hit its peak.
Population
What position does LPL-RustDockerServer hold in the rankings?
In the top 31% of all ranked servers, LPL-RustDockerServer sits at #6,881 for player hours over the last seven days.
How many players does LPL-RustDockerServer usually have?
With 10 slots available, LPL-RustDockerServer currently has 0 players. It peaked at 1 and averaged 0 players over the last seven days.
Tags
What is meant by the tags on LPL-RustDockerServer?
The game's browser takes its cue from the tags LPL-RustDockerServer has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does LPL-RustDockerServer appear in the Rust Server Score lists and filters?
These Rust Server Score lists count LPL-RustDockerServer among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
How is LPL-RustDockerServer set up, and what rules does it keep?
The name of LPL-RustDockerServer gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map LPL-RustDockerServer uses?
A procedural map of size 4,500 and seed 317670913, generated by the game, is what LPL-RustDockerServer runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
What is the way to join LPL-RustDockerServer?
To connect, start Rust, press F1, and type client.connect 134.228.179.43:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
A steady term. Strongest in performance (A+); population is the one to work on (F).