Offline 83.186.250.106:28025 checked 1d ago
Local RaidLab (flat, public build)
Connect
srv = rust.server("83.186.250.106:28026")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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 best
srv.rank.plot(invert=True) # 1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# Peak: the most players in the first 48 hours. 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.
display(srv.map, srv.info())
Map
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 83.186.250.106:28025
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 04:49 UTC
- hostname
- –
- first seen
- 23 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | [EU] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | EU · groups of 8+ · 116 on average | 125/999 |
| 1 | [NA] Builders Sanctuary 3.0 Creative | Sandbox | Minigames | | NA · groups of 8+ · 91 on average | 32/999 |
| 2 | [AU] Rusticated.com - Creative Sandbox | Build | Never Wipes | OC · groups of 8+ · 53 on average | 82/150 |
| 3 | Atlas // CSL - Ranked | Battlefield | Aimtrain | Scrims | FFA | EU · groups of 30+ · weekly · 37 on average | 15/100 |
| 4 | AQRUX RUST BUILD | CREATIVE | SANDBOX | EU · groups of 8+ · monthly · 24 on average | 38/100 |
| 5 | KoalaKopters - Minicopter / Helicopter Training|Arena|Dogfight | groups of 8+ · 23 on average | 24/100 |
Quick answers
From the figures on this page.
Population
What position does Local RaidLab (flat, public build) take in the server rankings?
Over the last seven days Local RaidLab (flat, public build) sits at #15,323 on player hours, in the top 69% of ranked servers.
How full does Local RaidLab (flat, public build) run?
Local RaidLab (flat, public build) returns no live count at this refresh, having last been seen 26 hours ago. Over the last seven days it averaged 0 players.
About the server
What Rust version does Local RaidLab (flat, public build) run?
Rust network protocol 2635 and build 168909 on Linux is what Local RaidLab (flat, public build) runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is Local RaidLab (flat, public build), and is it online now?
Local RaidLab (flat, public build) is offline at this refresh; the last response came 26 hours ago. Uptime of 46% across the last 5 full days: 55 hours of 120. The first row Rust Data holds for it is dated 23 October 2026.
Where does Local RaidLab (flat, public build) sit?
No region is published by Local RaidLab (flat, public build). Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 83.186.250.106:28025.
Settings and map
Which settings and rules does Local RaidLab (flat, public build) run?
No gather rate appears in the name: Local RaidLab (flat, public build). Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Wipes and dates
When does Local RaidLab (flat, public build) wipe, and on what schedule?
Too few wipes are on record for Local RaidLab (flat, public build) to reveal its rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 10 days 6 hours ago.
Tags, lists
Which Rust Data filters and lists contain Local RaidLab (flat, public build)?
These Rust Data lists include Local RaidLab (flat, public build): Modded Rust servers and Servers with build or creative tags. These filters bring it up 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.
How should you read the server tags on Local RaidLab (flat, public build)?
Read by the game's server browser, the tags Local RaidLab (flat, public build) publishes are: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): 4 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way into Local RaidLab (flat, public build)?
The manual route: launch Rust, F1, then client.connect 83.186.250.106:28025. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.