Station XX-15268 · no signal
Local RaidLab (flat, public build)
Offline 83.186.250.106:28025 checked 1d ago
- Players now
- 0/ 4
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,268
- top 68%
- Last wipe
- 10d ago
- no schedule published
- Next wipe
- –
- no wipe seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 4 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 68% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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 RaidLab (flat, public build)?
No gather rate appears in the name of Local RaidLab (flat, public build). Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Oxide. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on Local RaidLab (flat, public build)?
Local RaidLab (flat, public build) is not responding at this moment and is offline, last seen 37 hours ago. The seven-day average for this server is 0 players.
How does Local RaidLab (flat, public build) rank against other Rust servers?
Over the last seven days, Local RaidLab (flat, public build) recorded enough player hours to reach #15,268 worldwide, placing it in the top 68% of all ranked servers.
Operator and location
How reliably does Local RaidLab (flat, public build) stay online?
Local RaidLab (flat, public build) is down at the moment; the last recorded contact was 37 hours ago. 55 of 120 hours in the last 5 full days were up time, 46% of the total. Its earliest appearance in the records of Rust Server Trends dates to 23 October 2026.
Which region does Local RaidLab (flat, public build) run from?
Nothing about a region comes from Local RaidLab (flat, public build). Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 83.186.250.106:28025.
What build of Rust does Local RaidLab (flat, public build) use?
Rust network protocol 2635 and build 168909 on Linux is what Local RaidLab (flat, public build) runs. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
On what timetable does Local RaidLab (flat, public build) run its wipes?
The rhythm of Local RaidLab (flat, public build) cannot yet be told: too few of its wipes are on record. 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 10 days 16 hours.
Server tags
What do the server tags on Local RaidLab (flat, public build) mean?
Tags published by Local RaidLab (flat, public build) and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp4 (Max players): 4 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Local RaidLab (flat, public build) appear?
The Rust Server Trends lists that take in Local RaidLab (flat, public build) are: Modded Rust servers, tracked live and Rust build and creative servers, live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Connecting
What steps get you onto Local RaidLab (flat, public build)?
Enter client.connect 83.186.250.106:28025 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.