Offline 65.108.8.8:28015 checked 2d ago
LoA TestServer
Connect
srv = rust.server("65.108.8.8:27017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
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.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 26 Oct, 10:36 UTC2d ago | 0 | NaN | running | 0 |
| 1 | Sat 3 Oct, 20:29 UTC25d ago | 1 | halved by day 1 | 22.6 days | 0 |
| 2 | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 65.108.8.8:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 10:36 UTC
- hostname
- –
- first seen
- 29 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 153 on average | 36/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 42/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 10/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 1/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 0/1000 |
Quick answers
From the figures on this page.
Player counts
How does LoA TestServer compare in the rankings?
Player hours over seven days put LoA TestServer at #15,349, in the top 69% of the ranked set.
How many players does LoA TestServer hold at once?
Offline now for LoA TestServer, with the last sample 2 days 17 hours ago. Over the last seven days it averaged 0 players.
Server data
What Rust version does LoA TestServer run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by LoA TestServer. Joining needs the same protocol on your game; Steam handles the update.
How reliable is LoA TestServer, and is it up?
The latest sample has LoA TestServer offline, with a last sighting 2 days 17 hours ago. Over the last 7 full days the hours up number 70 of 168, 42%. The first row Rust Data holds for it is dated 29 September 2026.
Which location does LoA TestServer run from?
No region is published by LoA TestServer. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 65.108.8.8:28015.
Rules, settings, map
Which rules apply on LoA TestServer, and what settings?
You will not find a gather rate in the string LoA TestServer. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has LoA TestServer loaded?
The game generates its map: procedural, on LoA TestServer.
Wipes and dates
When does LoA TestServer wipe, and how often?
LoA TestServer wipes on no fixed rhythm, so there is nothing to predict. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 2 days 17 hours ago, and that is the one in play.
On LoA TestServer, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.
Tags, lists
Where does LoA TestServer appear among Rust Data lists and filters?
These Rust Data lists include LoA TestServer: Modded Rust servers. It appears under these 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.
How should you read the server tags on LoA TestServer?
The game's server browser reads these tags from LoA TestServer: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): Slot count: 5; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way to join LoA TestServer?
Enter client.connect 65.108.8.8:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.