On the class lists: F (21), with population over 48 hours and no performance mark.
Players now1/ 1001% full
7-day average1peak 1
Rank#8,712top 39%
Last wipe27d agomonthly schedule
Next wipe7d 9hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 100 on average. Plenty of space to grow.
Standingrank on player hours
61/ 100
C
Working its way up from the back of the class: #8,712 on player hours.
Uptimehours on the list, last 48
4/ 100
F
Attendance needs work: on the list only 2 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 90 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
40/ 100
F
Slipped a little: down 1,688 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in performance (A+); wipes are 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
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
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 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 39% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 9h.
The force wipe · high confidence
usual gap12.3 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 2
Coming wipes
7d 9hThu 5 Nov, 19:00 UTCFW
35d 9hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Thu 1 OctSat 19 Sep
Players each hour, from the hour of the wipe. The latest peaked at 2, 23 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 18:25 UTCFW27d ago
2
–
running
1
Sat 19 Sep, 12:17 UTC39d ago
1
halved by day 2
12.3 days
1
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
You'll find no region listed by Lili Test. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 79.137.67.68:28015.
How dependable is Lili Test, and is it online at the moment?
You cannot join now: Lili Test is offline, last seen 40 hours ago. About 49 minutes ago, it restarted, based on the uptime it reports. It was up 9 of 168 hours over the last 7 full days, which is 5% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Does Lili Test perform well?
It never fell below 90 server fps in the last 48 hours, averaging 90. Up to 70,762 entities were in the world, covering buildings, deployables and the rest. At its highest, it used 1,502 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does Lili Test sit?
Rust network protocol 2635 and build 168909 on Linux is what Lili Test runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does Lili Test wipe its map?
The force wipe each month is the only wipe Lili Test takes. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. It has been running its current world for 27 days 14 hours. Its tags list a monthly wipe schedule.
What should you expect from wipe day on Lili Test?
Across its recent wipes, the busiest moments averaged 2 players. 23 hours after the latest wipe began, the crowd hit its peak. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 2 is when it sank below half in the wipes that did not hold.
Population
Where does Lili Test place in the wider field of Rust servers?
Over the last seven days, Lili Test has #8,712 for player hours, in the top 39% of all ranked servers.
What does the population on Lili Test look like?
The last sighting of Lili Test was 40 hours ago, and it is offline right now. It peaked at 1 and averaged 1 players over the last seven days. The busiest time in the last 48 hours was 17:00 UTC, with an average of 0 players.
Tags and filters
How should you read the tags on Lili Test?
gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Its slot count is 100; ts8 (Group limit): The limit is 8 per team, the default the game ships with; 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; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags Lili Test publishes, and the game's server browser reads them. 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 Lili Test appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Lili Test among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Map and rules
What settings and rules apply on Lili Test?
The name of Lili Test gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map Lili Test uses?
Lili Test runs a game-generated procedural map at size 3,500, seed 1783023111. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
What is the way to join Lili Test?
To connect, start Rust, press F1, and type client.connect 79.137.67.68:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^m,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersIts slot count is 100.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
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.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^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 performance (A+); wipes are the one to work on (F).