Station XX-15891 · no signal
private-homelab
Offline 211.230.217.86:28015 checked 20d ago
- Players now
- 0/ 1
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,891
- top 72%
- Last wipe
- 20d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 1 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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 0.5 daysbetween real wipes
- on rhythm
- 0%of its recent 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 |
|---|---|---|---|---|---|---|
| Fri 9 Oct, 08:29 UTC20d ago | M0.0■steady | 0 | – | running | 0 | |
| Thu 8 Oct, 23:40 UTC20d ago | M0.0■steady | 0 | – | 0.4 days | 0 | |
| Thu 8 Oct, 06:44 UTC21d ago | M0.0■steady | 0 | – | 0.7 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 pageMap and rules
Which map is running on private-homelab?
private-homelab uses a procedural map, which the game generates.
Which settings and rules apply on private-homelab?
You will find no gather rate in the name of private-homelab. Groups hold up to 8 players, which is the default for the game. In survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. 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.
Population
What is the current population on private-homelab?
A reading taken now finds private-homelab offline; the most recent activity was 20 days 11 hours ago.
How does private-homelab rank against other Rust servers?
On player hours for the past week, private-homelab sits at #15,891, which puts it inside the top 72% of every ranked server.
Operator and location
How reliably does private-homelab stay online?
private-homelab is down at the moment; the last recorded contact was 20 days 11 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. Its earliest appearance in the records of Rust Server Trends dates to 13 September 2026.
Which region does private-homelab run from?
No region is published by private-homelab. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 211.230.217.86:28015.
What build of Rust does private-homelab use?
private-homelab is running Rust network protocol 2634 and build 167231 on a machine with Linux. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on private-homelab?
The recent wipes averaged a busiest count of 0 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does private-homelab run its wipes?
There is no next wipe to predict at private-homelab, since its wipes fall at irregular times. 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 20 days 12 hours.
Server tags
What do the server tags on private-homelab mean?
The game's server browser reads the tags private-homelab publishes: gmrust (Game mode): The game mode is standard Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs167231 (Build): Game build: 167231; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does private-homelab appear?
The Rust Server Trends lists that take in private-homelab are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Join the server
How do you connect to private-homelab?
You can connect by pressing F1 in Rust and typing client.connect 211.230.217.86:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects 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.