Offline 45.28.150.181:28015 checked 9d ago
RaidLabs Development
Connect
srv = rust.server("45.28.150.181:28016")
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 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 18 Oct, 01:01 UTC9d ago | 1 | NaN | running | 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 45.28.150.181:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 18 Oct 2026, 01:01 UTC
- hostname
- –
- first seen
- 13 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 | ShockRust | Blue | NoLimit | no group limit · 163 on average | 208/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 127 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 111 on average | 187/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 34/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 85 on average | 191/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 65/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does RaidLabs Development rank?
Over the last seven days RaidLabs Development sits at #13,605 on player hours, in the top 62% of ranked servers.
How many players does RaidLabs Development hold at once?
The current row shows RaidLabs Development offline; the last response was 9 days 17 hours ago.
About the server
What Rust version does RaidLabs Development run?
The build is Rust network protocol 2634 and build 167584 on Windows, run by RaidLabs Development. Steam updates your game for you, but the protocol must match to join.
How reliable is RaidLabs Development, and is it up?
Offline now for RaidLabs Development, last seen 9 days 17 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 13 October 2026.
Where does RaidLabs Development sit?
No region is published by RaidLabs Development. 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 45.28.150.181:28015.
Settings and map
What rules and settings are recorded for RaidLabs Development?
You will not find a gather rate in the string RaidLabs Development. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. Anti-cheat status: VAC on.
Wipes and dates
When does RaidLabs Development wipe, and how often?
The record for RaidLabs Development holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 9 days 18 hours ago, and that is the one in play.
On RaidLabs Development, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Tags, lists
Which lists on Rust Data hold RaidLabs Development, and which filters?
The Rust Data lists that RaidLabs Development 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 2 weeks.
Which meanings do the tags on RaidLabs Development hold?
The game's server browser reads these tags from RaidLabs Development: gmvanilla (Game mode): Survival in vanilla form; mp20 (Max players): Slot count: 20; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167584 (Build): The server runs build 167584; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into RaidLabs Development?
Enter client.connect 45.28.150.181:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.