Station XX-15400 · no signal
Local RaidLab (flat, public build)
Offline 83.190.130.89:28025 checked 4d ago
- Players now
- 0/ 4
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,400
- top 69%
- Last wipe
- 9d ago
- no schedule published
- Next wipe
- –
- too few wipes 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 69% 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.6 daysbetween real wipes
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 19 Oct, 04:49 UTC9d ago | M0.0■steady | 0 | – | running | 0 | |
| Sun 18 Oct, 15:11 UTC9d ago | M0.0■steady | 0 | – | 0.6 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 settings and rules apply on Local RaidLab (flat, public build)?
No gather rate appears in the name of Local RaidLab (flat, public build). The group limit is 8 players, the game's default. survival is the game 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.
Player counts
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 4 days 20 hours ago. Averaged across the last seven days, the population was 0 players.
How does Local RaidLab (flat, public build) rank against other Rust servers?
On player hours for the past week, Local RaidLab (flat, public build) sits at #15,400, which puts it inside the top 69% of every ranked server.
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 4 days 20 hours ago. 24 of 168 hours in the last 7 full days were up time, 14% of the total. On 4 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does Local RaidLab (flat, public build) run from?
Nothing about a region comes from Local RaidLab (flat, public build). The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 83.190.130.89:28025 is the address it uses.
What build of Rust does Local RaidLab (flat, public build) use?
On Linux, Local RaidLab (flat, public build) runs Rust network protocol 2634 and build 167781. 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 Local RaidLab (flat, public build)?
The recent wipes averaged a busiest count of 0 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does Local RaidLab (flat, public build) run its wipes?
On record so far are too few of Local RaidLab (flat, public build)'s wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. The present world dates from 9 days 3 hours.
Lists and 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): You'll find standard Rust survival here; mp4 (Max players): The server has 4 slots; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed 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?
These Rust Server Trends lists include Local RaidLab (flat, public build): Modded Rust servers, tracked live and Rust build and creative servers, 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; Last wipe: In the last 2 weeks.
Join the server
How do you connect to Local RaidLab (flat, public build)?
To join, enter client.connect 83.190.130.89:28025 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.