On the class lists: F (27), with population over 48 hours and no performance mark.
Players now0/ 50% full
7-day average0peak –
Rank#15,353top 69%
Last wipe2d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 5 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,353 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
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
49/ 100
D
Slipped a little: down 228 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); 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.
No hourly history yet.
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W···W·
·······
·······
·······
W···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap13.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Mon 26 OctSat 3 OctTue 29 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 10:36 UTC2d ago
0
–
running
0
Sat 3 Oct, 20:29 UTC25d ago
1
halved by day 1
22.6 days
0
Tue 29 Sep, 17:24 UTC29d ago
2
halved by day 1
4.1 days
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
You'll find no region listed by LoA TestServer. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 65.108.8.8:28015.
Is LoA TestServer up, and how steady is its uptime?
At this moment, LoA TestServer is offline; the last time it was seen was 2 days 15 hours ago. It was up 42% of the time over the last 7 full days, 70 of 168 hours. On 29 September 2026, Rust Server Score saw it for the first time.
What Rust version is LoA TestServer on?
Rust network protocol 2635 and build 168909 on Linux is what LoA TestServer runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does LoA TestServer wipe its map?
LoA TestServer wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 2 days 15 hours.
What should you expect from wipe day on LoA TestServer?
Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 0 hours into the latest wipe. Half the peak held until the next wipe in 0% of its recent wipes. Day 1 is when it sank below half in the wipes that did not hold.
Population
What position does LoA TestServer hold in the rankings?
Over the last seven days, LoA TestServer has #15,353 for player hours, in the top 69% of all ranked servers.
Is LoA TestServer a busy server?
The last sighting of LoA TestServer was 2 days 15 hours ago, and it is offline right now. Over the past seven days, the average player count was 0.
Tags and filters
What do LoA TestServer's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): 5 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags LoA TestServer publishes, and the game's server browser reads them. 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 lists and filters on Rust Server Score show LoA TestServer?
Rust Server Score lists that include LoA TestServer: 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; Last wipe: In the last 3 days.
Map and rules
Which rules does LoA TestServer enforce, and what are its settings?
You will find no gather rate in the name of LoA TestServer. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Oxide plugins are running on it. The server runs Valve's anti-cheat, VAC.
Which map is in play on LoA TestServer?
The game generates a procedural map for LoA TestServer.
Getting in
How do you get onto LoA TestServer?
To connect, start Rust, press F1, and type client.connect 65.108.8.8:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max players5 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find 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.
A term to build on. Strongest in momentum (D); population is the one to work on (F).