Station XX-6796 · no signal
RustLocalControl
Offline 80.55.38.89:28025 checked 1d ago
- Players now
- 1/ 1
- 100% full
- Motion · 24 h
- M0.0▲rising
- +1 players on the day
- 7-day average
- 1
- peak 1
- Rank
- #6,796
- top 31%
- Last wipe
- 22d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 1 slots
- Motion · 24 h
- M0.0▲rising+1 players
- Sharpest hour
- +1into Tue 18:00 UTC
- Peak · 48 h
- 1most players in any hour
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 31% 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.
- 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 |
|---|---|---|---|---|---|---|
| Tue 6 Oct, 08:06 UTC22d ago | M0.0▲rising | 1 | – | running | 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 RustLocalControl?
RustLocalControl uses a procedural map, which the game generates.
Which settings and rules apply on RustLocalControl?
The name of RustLocalControl gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, gather, build and raid in the standard game. You can raid and fight other players here. 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 off.
Population
What is the current population on RustLocalControl?
RustLocalControl is not responding at this moment and is offline, last seen 27 hours ago. Averaged across the last seven days the population was 1 players, reaching a peak of 1. Averaged over the last 48 hours, the busiest hour was 18:00 UTC at 1 players.
How does RustLocalControl rank against other Rust servers?
On player hours for the past week, RustLocalControl sits at #6,796, which puts it inside the top 31% of every ranked server.
Server details
How reliably does RustLocalControl stay online?
No contact with RustLocalControl right now, and the last recorded contact was 27 hours ago. 27 of 168 hours in the last 7 full days were up time, 16% of the total. On 6 October 2026 it was recorded for the first time by Rust Server Trends.
Where in the world is RustLocalControl hosted?
A region is not published by RustLocalControl. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 80.55.38.89:28025.
What build of Rust does RustLocalControl use?
RustLocalControl is running Rust network protocol 2635 and build 168909 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on RustLocalControl?
The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 0 hours after the wipe.
How often does RustLocalControl wipe, and on which days?
The rhythm of RustLocalControl cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 22 days 15 hours is how long the current world has been running.
Lists and tags
What do the server tags on RustLocalControl mean?
Tags published by RustLocalControl and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp1 (Max players): 1 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; 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): A plugin framework, Oxide (uMod), runs 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 RustLocalControl appear?
These Rust Server Trends lists include RustLocalControl: 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 RustLocalControl?
You can connect by pressing F1 in Rust and typing client.connect 80.55.38.89:28025 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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.