Station XX-16001 · no signal
Local Test Server
Offline 2.134.73.108:28015 checked 24d ago
- Players now
- 0/ 15
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,001
- top 71%
- Last wipe
- 24d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 15 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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 71% 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
- 1.8 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Sun 4 Oct, 11:37 UTC24d ago | M0.0▲rising | 1 | – | running | 0 | |
| Fri 2 Oct, 17:24 UTC26d ago | M0.0▲rising | 1 | – | 1.8 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 pageRules and settings
Which map is running on Local Test Server?
The procedural map on Local Test Server is size 2,000 with seed 12345, generated by the game. Size and seed produce the same map, so RustMaps can show it from this page.
Which settings and rules apply on Local Test Server?
No gather rate appears in the name of Local Test Server. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on Local Test Server right now?
A reading taken now finds Local Test Server offline; the most recent activity was 24 days 10 hours ago.
How does Local Test Server rank against other Rust servers?
Over the last seven days, Local Test Server recorded enough player hours to reach #16,001 worldwide, placing it in the top 71% of all ranked servers.
Server details
How reliably does Local Test Server stay online?
As recorded now, Local Test Server is not reachable, the last contact having been 24 days 10 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 13 September 2026 is when Rust Server Trends first recorded it.
Where in the world is Local Test Server hosted?
Nothing about a region comes from Local Test Server. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 2.134.73.108:28015 is the address it uses.
What build of Rust does Local Test Server use?
Local Test Server is running Rust network protocol 2634 and build 166586 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on Local Test Server?
The recent wipes averaged a busiest count of 1 players. 2 hours into the latest wipe, the crowd reached its peak.
On what timetable does Local Test Server run its wipes?
On record so far are too few of Local Test Server's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 24 days 13 hours is how long the current world has been running.
Lists and tags
What do the server tags on Local Test Server mean?
Tags published by Local Test Server and read by the game's server browser include gmrust (Game mode): The game mode is standard Rust survival; mp15 (Max players): 15 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs166586 (Build): The game build is 166586; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $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. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Local Test Server appear?
The Rust Server Trends lists that take in Local Test Server 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.
How to join
What steps get you onto Local Test Server?
To join, enter client.connect 2.134.73.108:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.