Station XX-12420 · no signal
Local Test
Offline 145.224.108.94:28015 checked 2d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak 1
- Rank
- #12,420
- top 56%
- Last wipe
- 3d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 56% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 0.5 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 26 Oct, 07:29 UTC3d ago | M0.0▼falling | 0 | – | running | 1 | |
| Sun 25 Oct, 19:40 UTC3d ago | M0.0▲rising | 1 | – | 0.5 days | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageMap and rules
Which settings and rules apply on Local Test?
The name of Local Test gives no gather rate. Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Oxide. The server has VAC on, Valve's anti-cheat.
Live population
How many players are recorded on Local Test right now?
No players are recorded on Local Test at this moment; it is offline, and the last sighting was 2 days 21 hours ago. Across seven days this server recorded an average of 0 players and a peak of 1.
How does Local Test rank against other Rust servers?
The last seven days of player hours place Local Test at #12,420, in the top 56% of all ranked servers.
Server details
How reliably does Local Test stay online?
As recorded now, Local Test is not reachable, the last contact having been 2 days 21 hours ago. Of the 72 hours in the last 3 full days, it was up for 11, or 15% of the time. 25 October 2026 is when Rust Server Trends first recorded it.
Which region does Local Test run from?
No region is published by Local Test. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 145.224.108.94:28015 is the address it uses.
Which Rust version is Local Test running?
On Windows, Local Test runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on Local Test?
On average, the busiest point of its recent wipes drew 0 players. The peak on the most recent wipe came 0 hours after the wipe.
On what timetable does Local Test run its wipes?
Too few wipes of Local Test are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 3 days 7 hours is how long the current world has been running.
Lists and tags
What do the server tags on Local Test mean?
These are the tags Local Test publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp10 (Max players): 10 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Local Test appear?
The Rust Server Trends lists that take in Local Test are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Connecting
How do you connect to Local Test?
Enter client.connect 145.224.108.94:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.