On the class lists: D (45), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 3
Rank#8,753top 40%
Last wipe20d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
60/ 100
C
Working its way up from the back of the class: #8,753 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
76/ 100
B
Mostly smooth: 46 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
25/ 100
F
Lost ground: down 4,303 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in uptime (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
No five-minute samples in the last two hours.
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 40% 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 peak3players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 18 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 8 Oct, 15:20 UTC20d ago
3
–
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 LL2. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 82.200.52.69:28015.
Is LL2 up, and how steady is its uptime?
The server is up: LL2 is online now. According to its reported uptime, the last restart was about 3 days 2 hours ago. It was up 98% of the time over the last 7 full days, 164 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
How well does LL2 run?
It averaged 46 server fps over the last 48 hours, with a low of 21. Buildings, deployables and everything else in the world added up to as many as 152,616 entities. Memory use reached up to 4,291 MB. When fps is low and entities climb, that is lag to players.
On what Rust version does LL2 sit?
You will find LL2 on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does LL2 wipe its map?
There are too few wipes on record for LL2 to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 20 days 4 hours have passed since this world was made.
What happens on LL2 when wipe day arrives?
The average peak on its recent wipes was 3 players. The crowd on the latest wipe was largest 18 hours after it began.
Player numbers
Where does LL2 sit among Rust servers?
Over the last seven days, LL2 has #8,753 for player hours, in the top 40% of all ranked servers.
What does the population on LL2 look like?
LL2 is showing 0 players right now, with 100 slots in total. It peaked at 3 and averaged 0 players over the last seven days. Over the last 48 hours, the peak hour was 11:00 UTC, averaging 1 players.
Tags
What is meant by the tags on LL2?
You'll see LL2 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp100 (Max players): Its slot count is 100; 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): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature LL2?
Rust Server Score lists that include LL2: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
What settings and rules apply on LL2?
You will find no gather rate in the name of LL2. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on LL2?
A procedural map of size 5,000 and seed 1337, generated by the game, is what LL2 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to LL2?
To connect, start Rust, press F1, and type client.connect 82.200.52.69:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://ya.ru/?nr=1&redirect_ts=1793149350.00000.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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 term to build on. Strongest in uptime (A); population is the one to work on (F).