Online 87.210.143.224:28015 checked 5m ago
RaidLab
Connect
srv = rust.server("87.210.143.224:28017")
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 3% 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 | |
|---|---|---|---|---|---|
| 0 | Wed 28 Oct, 01:17 UTC2d ago | NaN | NaN | running | 0 |
| 1 | Thu 22 Oct, 23:57 UTC7d ago | NaN | NaN | NaN | 0 |
| 2 | Thu 22 Oct, 17:48 UTC7d ago | NaN | NaN | NaN | 0 |
# 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 87.210.143.224:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 01:59 UTC
- hostname
- –
- first seen
- 15 Sep 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 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 17/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 31/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 9/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 40/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 160/200 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does RaidLab rank?
Rank #616 on seven-day player hours for RaidLab, within the top 3% of all ranked servers.
How many players does RaidLab hold at once?
RaidLab reports 200 players at this refresh, with 50 slots configured. Over the last seven days it averaged 34 players and peaked at 201. The 48-hour sample puts the busiest hour at 02:00 UTC, averaging 200 players.
About the server
What is the Rust version on RaidLab?
The build is Rust network protocol 2635 and build 168909 on Windows, run by RaidLab. The protocol has to match before you can join, and Steam does the updating.
How reliable is RaidLab, and is it online now?
Online is the state at the latest refresh for RaidLab. Over the last 7 full days the hours up number 117 of 168, 70%. The first row Rust Data holds for it is dated 15 September 2026.
Which location does RaidLab run from?
For RaidLab, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 87.210.143.224:28015.
Map and rules
Which rules apply on RaidLab, and what settings?
No gather rate appears in the name: RaidLab. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. Anti-cheat status: VAC off.
Which map has RaidLab loaded?
A procedural map runs on RaidLab, generated by the game.
Wipes and dates
When does RaidLab wipe, and on what schedule?
A rhythm cannot be read from the wipes of RaidLab on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 6 days 23 hours ago.
Tags, lists
Where does RaidLab appear among Rust Data lists and filters?
The Rust Data lists that RaidLab fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week; Players now: At least 200; Average players: 25+ on average.
Which meanings do the tags on RaidLab hold?
Read by the game's server browser, the tags RaidLab publishes are: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): Slot count: 50; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join RaidLab?
The manual route: launch Rust, F1, then client.connect 87.210.143.224:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. A queue is likely, since it is full at this refresh.