Offline 178.126.210.193:28215 checked 26d ago
LiveSave-Inspect
Connect
srv = rust.server("178.126.210.193:28216")
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 bestTop 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 4h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 4h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 22 hours in, with 1 in the queue.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 17:56 UTC FW27d ago | 1+1 queue | 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
- 178.126.210.193:28215
- region
- –
- max players
- 8
- group limit
- 50 max
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 17:56 UTC
- hostname
- –
- first seen
- 2 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 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 254 on average | 132/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 243 on average | 249/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 107 on average | 46/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 58 on average | 89/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 54 on average | 27/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 49 on average | 55/100 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does LiveSave-Inspect rank?
Player hours over seven days put LiveSave-Inspect at #15,332, in the top 67% of the ranked set.
What population does LiveSave-Inspect carry?
The current row shows LiveSave-Inspect offline; the last response was 26 days 23 hours ago.
Server facts
What is the Rust version on LiveSave-Inspect?
Rust network protocol 2634 and build 166462 on Windows is what LiveSave-Inspect runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is LiveSave-Inspect, and is it up?
Offline now for LiveSave-Inspect, last seen 26 days 23 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 2 October 2026.
Where does LiveSave-Inspect sit?
There is no region published for LiveSave-Inspect. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 178.126.210.193:28215 is its address.
Settings and map
Which settings and rules does LiveSave-Inspect run?
No gather rate appears in the name: LiveSave-Inspect. 50 players is the maximum per group. Recorded as pve, no combat between players. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. The VAC field reads off.
Wipes and dates
On what schedule does LiveSave-Inspect wipe?
A single wipe each month, the force wipe, is all LiveSave-Inspect does. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 27 days 20 hours ago.
On LiveSave-Inspect, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. On the latest wipe the peak came 22 hours after the wipe, with a queue of 1.
Tags, lists
Which Rust Data filters and lists contain LiveSave-Inspect?
The Rust Data lists that LiveSave-Inspect fits are: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on LiveSave-Inspect hold?
Read by the game's server browser, the tags LiveSave-Inspect publishes are: gmrust (Game mode): Rust survival in its standard form; mp8 (Max players): Slot count: 8; ts50 (Group limit): Team size tops out at 50; v2634 (Protocol): To join, your game must run protocol 2634; cs166462 (Build): Recorded game build: 166462; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded; modded (Modded): Plugins or settings alter the game, so it sits under Modded; oxidation (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. 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.
How to join
What is the way to join LiveSave-Inspect?
In Rust, F1 opens the console: type client.connect 178.126.210.193:28215. Launch Rust on this page does the same by opening the game through Steam and connecting.