Rust StatisticsWorking papers on every public Rust server · 60,383 players now

LoA TestServer

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 3d ago · 65.108.8.8:28015

Abstract

We describe the public Rust server LoA TestServer, reached at 65.108.8.8:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,323 of all servers, the top 69%. It last wiped 3d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/50% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,323top 69%
Last wipe3d agono schedule published
Next wipe3–no rhythm it keeps

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

The server stands in the top 69% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k29 Sep5 Oct11 Oct17 Oct23 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: 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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
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
Mon 26 OctSat 3 OctTue 29 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Mon 26 Oct, 10:363d ago 0 – running 0
Sat 3 Oct, 20:2925d ago 1 halved by day 1 22.6 d 0
Tue 29 Sep, 17:2429d ago 2 halved by day 1 4.1 d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 5: The map: Procedural Map.
Table 4: The server's published settings.
Address65.108.8.8:28015
Region–
Max players5
Group limit8, the default
Wipe schedule–
Last wipe26 Oct 2026, 10:36 UTC
Hostname–
First seen29 Sep 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and next Rust wipe times [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 149 on average154/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average120/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average186/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average78/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average8/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average22/1000

Appendix AQuick answers

From the figures on this page.

Server details

A.1What location does LoA TestServer have?

A region is not published by LoA TestServer. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 65.108.8.8:28015.

A.2How reliable is LoA TestServer, and is it currently online?

Right now, LoA TestServer is offline, and the last time it was seen was 3 days ago. Its uptime over the last full days (7 days) was 42%, with 70 of 168 hours online. The first record of it by Rust Statistics dates to 29 September 2026.

A.3What version of Rust is run on LoA TestServer?

LoA TestServer is running Rust network protocol 2635 and build 168909 on the Linux operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.4What schedule does LoA TestServer follow for wipes?

No next wipe can be predicted for LoA TestServer since its wipes occur at irregular intervals. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 3 days have passed since the current world was generated.

A.5How would you describe wipe day on LoA TestServer?

Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 0 hours after the latest wipe. Half the peak was sustained until the next wipe in 0% of recent wipes. If not, the population dropped below half by day 1.

Population

A.6What position does LoA TestServer occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts LoA TestServer at #15,323, within the top 69% of ranked servers.

A.7What is the population level of LoA TestServer?

At this moment LoA TestServer is offline, having last been seen 3 days ago. The seven-day average for this server is 0 players.

Tags and filters

A.8What is the meaning of the tags on LoA TestServer?

The game's server browser reads gmrust (Game mode): Rust survival, in its standard form; mp5 (Max players): The slot count is 5; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): The region code is unset; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game, which LoA TestServer publishes as its tags. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

A.9Where can LoA TestServer be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that LoA TestServer fits. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Rules, settings, map

A.10Under what rules and settings does LoA TestServer operate?

The name of LoA TestServer states no gather rate. The group cap is 8 players, which is the default in the game. The mode is survival, which means gather, build and raid: the standard game. Fighting and raiding between players are both permitted. The server browser lists it as Modded, where plugins or settings alter the game. Oxide plugins are running. VAC, Valve's anti-cheat, is enabled.

A.11What map is in use on LoA TestServer?

On LoA TestServer the terrain is procedural, built by the game itself.

Connection

A.12How do you connect to LoA TestServer?

Enter client.connect 65.108.8.8:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp5,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Rust survival, in its standard form.
mp5Max players. The slot count is 5.
ts8Group limit. 8 per team, the value the game sets by default.
v2635Protocol. Your game must run protocol 2635 to connect.
cs168909Build. Build 168909 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. The region code is unset.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).
^zModded. Modded listing: plugins or settings modify the game.

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.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.