Offline 211.230.217.86:28015 checked 20d ago
private-homelab
Connect
srv = rust.server("211.230.217.86: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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its wipes keep no rhythm, so there is no next wipe to predict. 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 9 Oct, 08:29 UTC20d ago | 0 | NaN | running | 0 |
| 1 | Thu 8 Oct, 23:40 UTC20d ago | 0 | NaN | 0.4 days | 0 |
| 2 | Thu 8 Oct, 06:44 UTC21d ago | 0 | NaN | 0.7 days | 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
- 211.230.217.86:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Oct 2026, 08:29 UTC
- hostname
- –
- first seen
- 13 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 · 149 on average | 157/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 187/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 69/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 11/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does private-homelab rank?
Player hours over seven days put private-homelab at #15,891, in the top 72% of the ranked set.
What population does private-homelab carry?
Offline now for private-homelab, with the last sample 20 days 1 hours ago.
Server facts
What Rust version does private-homelab run?
Rust network protocol 2634 and build 167231 on Linux is what private-homelab runs. Steam updates your game for you, but the protocol must match to join.
How reliable is private-homelab, and is it online now?
private-homelab is offline at this refresh; the last response came 20 days 1 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Where does private-homelab sit?
No region is published by private-homelab. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 211.230.217.86:28015 is its address.
Settings and map
Which rules apply on private-homelab, and what settings?
The name private-homelab carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on private-homelab?
The game generates its map: procedural, on private-homelab.
Wipes and dates
On what schedule does private-homelab wipe?
No next wipe can be predicted for private-homelab, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 20 days 2 hours ago, and that is the one in play.
On private-homelab, what happens on wipe day?
The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does private-homelab appear among Rust Data lists and filters?
On Rust Data, private-homelab appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on private-homelab hold?
The game's server browser reads these tags from private-homelab: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): 1 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167231 (Build): Recorded game build: 167231; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join private-homelab?
In Rust, F1 opens the console: type client.connect 211.230.217.86:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.