LiveSave-Inspect
Offline 178.126.210.193:28215 checked 26d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 67% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 6h. The force wipe · high confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 7d 6h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 35d 6h | 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| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 17:56 UTC FW27d ago | 1+1 queue | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| Server | Profile | Players now |
|---|---|---|
| [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 253 on average | 113 / 2000 |
| [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 242 on average | 186 / 2000 |
| Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 107 on average | 35 / 200 |
| 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 58 on average | 102 / 200 |
| [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 54 on average | 16 / 300 |
| TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 50 on average | 56 / 100 |
Quick answers
from the figures on this pageWipe cycle
The wipe schedule for LiveSave-Inspect: what is it?
With the force wipe, once a month, LiveSave-Inspect wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world now in play was created 27 days 18 hours ago.
Wipe day on LiveSave-Inspect: what should you expect?
The average busiest count over recent wipes is 1 players. 22 hours after the latest wipe the crowd peaked, with 1 more queued.
Server
What is the hosting location of LiveSave-Inspect?
No region appears in what LiveSave-Inspect publishes. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. You will find it at 178.126.210.193:28215.
What Rust build does LiveSave-Inspect run?
The platform is Windows, with Rust network protocol 2634 and build 166462 running on LiveSave-Inspect. Joining requires the same protocol on your game; Steam handles the update.
Is LiveSave-Inspect up, and how steady is its uptime?
The current status is offline for LiveSave-Inspect, with the last sighting 26 days 21 hours ago. Uptime over the last full days (7) was 0%, or 0 of 168 hours. 2 October 2026 is when Rust Server Analytics first recorded it.
Tags
Which meanings do the tags on LiveSave-Inspect carry?
gmrust (Game mode): Rust survival, standard ruleset; mp8 (Max players): Capacity of 8 slots; ts50 (Group limit): Team size is capped at 50; v2634 (Protocol): Protocol 2634 is required: your game must match to connect; cs166462 (Build): Game build: 166462; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): No region code has been set; ^p (PvE): No fighting between players, with the world as the threat; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The Modded section, because plugins or settings modify play; modded (Modded): The Modded section, because plugins or settings modify play; oxidation (Custom tag): Not one of Rust's standard tags; the owner or a plugin applied it are the tags LiveSave-Inspect publishes, and the game's server browser reads them. At the top of this page you can see the player count, queue and world age, all of which the tags also hold.
On Rust Server Analytics, which lists and filters feature LiveSave-Inspect?
These Rust Server Analytics lists include LiveSave-Inspect: Modded Rust servers: live data and PvE Rust servers by live population. 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.
Player numbers
Against other Rust servers, how does LiveSave-Inspect compare?
The seven-day player-hours rank for LiveSave-Inspect is #15,332, inside the top 67% of all ranked servers.
What is the population of LiveSave-Inspect?
LiveSave-Inspect is offline at this refresh; the last contact was 26 days 21 hours ago.
Map and rules
How is LiveSave-Inspect configured, and what rules apply?
Gather rate is not mentioned in the name of LiveSave-Inspect. A maximum of 50 players per group applies. pve is the game mode, no fighting other players. In the server browser it sits under Modded, where plugins or settings alter the game. Oxide plugins are run. The server runs with VAC, Valve's anti-cheat, disabled.
How to join
How can a player join LiveSave-Inspect?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 178.126.210.193:28215.