Station XX-15332 · no signal
LiveSave-Inspect
Offline 178.126.210.193:28215 checked 26d ago
- Players now
- 1/ 8
- 12% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,332
- top 67%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- 7d 9h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 8 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 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 9h. The force wipe · high confidence
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 7d 9hThu 5 Nov, 19:00 UTCFW
- 35d 9hThu 3 Dec, 19:00 UTCFW
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 17:56 UTC FW27d ago | M0.0▲rising | 1+1 queue | – | running | 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 settings and rules apply on LiveSave-Inspect?
The name of LiveSave-Inspect gives no gather rate. 50 players is the most a group can hold. In pve mode, no combat against other players. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. Anti-cheat is off: VAC, from Valve.
Population
How many players are recorded on LiveSave-Inspect right now?
LiveSave-Inspect is not responding at this moment and is offline, last seen 26 days 18 hours ago.
How does LiveSave-Inspect rank against other Rust servers?
Over the last seven days, LiveSave-Inspect recorded enough player hours to reach #15,332 worldwide, placing it in the top 67% of all ranked servers.
Operator and location
How reliably does LiveSave-Inspect stay online?
LiveSave-Inspect is down at the moment; the last recorded contact was 26 days 18 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 2 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does LiveSave-Inspect run from?
Nothing about a region comes from LiveSave-Inspect. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 178.126.210.193:28215.
Which Rust version is LiveSave-Inspect running?
LiveSave-Inspect is running Rust network protocol 2634 and build 166462 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe schedule
What does wipe day look like on LiveSave-Inspect?
On average, the busiest point of its recent wipes drew 1 players. 22 hours after the latest wipe the crowd peaked, with 1 waiting in the queue.
How often does LiveSave-Inspect wipe, and on which days?
At the force wipe each month LiveSave-Inspect wipes, and at no other time. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. The present world dates from 27 days 15 hours.
Server tags
What do the server tags on LiveSave-Inspect mean?
These are the tags LiveSave-Inspect publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp8 (Max players): Slots: 8; ts50 (Group limit): Teams are capped at 50 players; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166462 (Build): Game build: 166462; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^p (PvE): You won't fight other players here; the world is what threatens you; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; modded (Modded): The game is changed by plugins or settings, placing it under Modded; oxidation (Custom tag): The owner or a plugin applied this tag, which isn't part of standard Rust. 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 LiveSave-Inspect appear?
You will find LiveSave-Inspect on the following Rust Server Trends lists: Modded Rust servers, tracked live 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.
Join the server
What steps get you onto LiveSave-Inspect?
You can connect by pressing F1 in Rust and typing client.connect 178.126.210.193:28215 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.