Station XX-13208 · no signal
Local Test Server
Offline 5.10.43.1:28015 checked 34d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #13,208
- top 61%
- Last wipe
- 34d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 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 61% 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.3 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, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 23 Sep, 20:52 UTC34d ago | M0.0■steady | 1 | – | running | 1 | |
| Wed 23 Sep, 13:15 UTC34d ago | M0.0■steady | 1 | – | 0.3 days | 1 |
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?
Local Test Server uses a procedural map, which the game generates.
Which settings and rules apply on Local Test Server?
No gather rate appears in the name of Local Test Server. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. 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 Server right now?
A reading taken now finds Local Test Server offline; the most recent activity was 34 days 13 hours ago.
How does Local Test Server rank against other Rust servers?
The last seven days of player hours place Local Test Server at #13,208, in the top 61% of all ranked servers.
Server facts
How reliably does Local Test Server stay online?
Local Test Server is down at the moment; the last recorded contact was 34 days 13 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 23 September 2026.
Which region does Local Test Server run from?
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. You reach it at 5.10.43.1:28015.
Which Rust version is Local Test Server running?
Local Test Server is running Rust network protocol 2633 and build 165217 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe day
What does wipe day look like on Local Test Server?
1 players, on average, was the busiest crowd at its recent wipes. 0 hours into the latest wipe, the crowd reached its peak.
How often does Local Test Server wipe, and on which days?
On record so far are too few of Local Test Server's wipes to tell its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 34 days 15 hours.
Server 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; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $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 Server appear?
These Rust Server Trends lists include Local Test Server: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto Local Test Server?
Enter client.connect 5.10.43.1: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.