This server publishes no banner
Exhibit no. 15,332Acc. 2026.15332
LiveSave-Inspect
Rust server · in the archive since 2 October 2026
Offline 178.126.210.193:28215 checked 26d ago
The timeline
Wipes
Every wipe on record as a dated marker, the force wipes among them, and the wipes expected next. Newest first in the record below.
2 Oct Last seen 1 Oct17:56 · FW 5 Nov19:00 · FW 3 Dec19:00 · FW
a wipe on recordthe monthly force wipeexpectedlast seen, 2 Oct 2026, 15:28 UTCAll times UTC.
The record of each wipe
-
Thu 1 Oct 202617:56 UTC FW27d ago
- Peak
- 1+1 in the queue
- Crowd
- –
- Lasted
- running
- Players before
- 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.
The rhythm
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h. The force wipe · high confidence
Coming wipes
- 7d 4hThu 5 Nov, 19:00 UTCFW
- 35d 4hThu 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.
The record
Population, performance and rank
Kept in folders: players every five minutes, every hour and every day; the server answering for itself; its rank among every server ranked.
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
Top 67% of all ranked servers. Ranked on player hours over the last seven days.
Related exhibits
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Visitors' questions about this exhibit
Quick answers
Answered from the figures on this page.
Tags and filters
What do the server tags on LiveSave-Inspect mean?
You can see the tags LiveSave-Inspect publishes, read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp8 (Max players): Slot count: 8; ts50 (Group limit): A team may hold no more than 50; v2634 (Protocol): Your game must run protocol 2634 to join; cs166462 (Build): This server runs game build 166462; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^p (PvE): Player combat is off: the world is the threat; ^o (Oxide): A plugin framework, Oxide (uMod), is installed here; ^z (Modded): Under Modded: the game is changed by plugins or settings; modded (Modded): Under Modded: the game is changed by plugins or settings; oxidation (Custom tag): Standard Rust does not define this tag; the owner or a plugin added it. At the top of this page you also see the current players, the queue and when the world was made, all from the tags.
Which Rust Server History lists and filters include LiveSave-Inspect?
These Rust Server History lists include LiveSave-Inspect: Modded Rust servers: the record and Rust PvE servers, on record. These filters on the server list bring it up: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
The record
Which version of Rust does LiveSave-Inspect run?
Rust network protocol 2634 and build 166462 is the build LiveSave-Inspect runs, on Windows. The protocol must match to join, and Steam handles that update.
Is LiveSave-Inspect online, and how reliable is it?
The record shows LiveSave-Inspect offline at this moment, last seen 26 days 22 hours ago. It was up for 0 of 168 hours in the last 7 full days, 0% of the time. 2 October 2026 is when Rust Server History first saw it.
Where is LiveSave-Inspect located?
You will find no region published by LiveSave-Inspect. Rust Server History does not look up where the machine stands; it shows where a server says it is. Its entry gives 178.126.210.193:28215 as the address.
Wipe log
What does wipe day look like on LiveSave-Inspect?
At their busiest, its recent wipes drew an average of 1 players. 22 hours after the latest wipe the crowd peaked, with a queue of 1 more.
What is the wipe schedule on LiveSave-Inspect?
LiveSave-Inspect wipes with the force wipe, once a month. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, and every Rust server wipes then. Made 27 days 20 hours ago, the current world is what it runs now.
Player record
How does LiveSave-Inspect rank against other Rust servers?
Player hours over the last seven days put LiveSave-Inspect at #15,332: a place in the top 67% of all ranked servers.
How busy is LiveSave-Inspect?
The last sighting of LiveSave-Inspect in the live count was 26 days 22 hours ago; it is offline now.
Rules, map
What are the rules and settings on LiveSave-Inspect?
No gather rate is stated in the name of LiveSave-Inspect. No group may exceed 50 players. Under game mode, the entry reads pve, player combat is not allowed. Under Modded in the server browser, the game is changed by plugins or settings. Plugins in use: Oxide. VAC from Valve is switched off.
How to join
How do I join LiveSave-Inspect?
Press F1 in Rust to open the console, then enter client.connect 178.126.210.193:28215 to connect. Launch Rust from this page instead and you join through Steam with the connect already made.
The label explained
Server tags
What each tag this server publishes means.
Published as mp8,ptrak,$r?,v2634,^p,gmrust,cs166462,ts50,^o^z,oxidation,modded
Game
gmrust
mp8
ts50
v2634
cs166462
ptrak
$r?
Gameplay
^p
Mods and access
^o
^z
modded
Other
oxidation
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.