Station XX-12181 · no signal
LocalServer
Offline 5.18.103.76:28015 checked 22d ago
- Players now
- 2/ 1
- 200% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #12,181
- top 54%
- Last wipe
- 22d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 2of 1 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 54% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 2.9 daysbetween real wipes
- on rhythm
- 100%of its recent 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 2, 2 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 5 Oct, 16:28 UTC22d ago | M0.3▲rising | 2 | – | running | 0 | |
| Fri 2 Oct, 17:34 UTC25d ago | M0.0■steady | 0 | – | 3 days | 0 | |
| Tue 29 Sep, 20:34 UTC28d ago | M0.0■steady | 0 | – | 2.9 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 map is running on LocalServer?
The map on LocalServer is procedural, produced by the game.
Which settings and rules apply on LocalServer?
The name of LocalServer gives no gather rate. Groups hold up to 8 players, which is the default for the game. survival is the game mode, gather, build and raid in the standard game. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.
Population
What is the current population on LocalServer?
A reading taken now finds LocalServer offline; the most recent activity was 22 days 5 hours ago.
How does LocalServer rank against other Rust servers?
Over the last seven days, LocalServer recorded enough player hours to reach #12,181 worldwide, placing it in the top 54% of all ranked servers.
Operator and location
How reliably does LocalServer stay online?
No contact with LocalServer right now, and the last recorded contact was 22 days 5 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 27 September 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is LocalServer hosted?
No region is published by LocalServer. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 5.18.103.76:28015 is the address it uses.
Which Rust version is LocalServer running?
On Windows, LocalServer runs Rust network protocol 2634 and build 166494. 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 LocalServer?
The recent wipes averaged a busiest count of 1 players. 2 hours after the latest wipe, the crowd peaked.
On what timetable does LocalServer run its wipes?
No next wipe can be predicted for LocalServer, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 22 days 10 hours.
Tags
What do the server tags on LocalServer mean?
The game's server browser reads the tags LocalServer publishes: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): The server has 1 slots; 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; cs166494 (Build): Game build: 166494; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it 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 LocalServer appear?
You will find LocalServer on the following Rust Server Trends lists: 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
How do you connect to LocalServer?
To join, enter client.connect 5.18.103.76: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.