Skip to the page
Network live 11,649 servers online 46,030 players aboard 109 wiped in the last 3 hours Every time in UK time and UTC · refreshed every five minutes
Rust Wipe TrackerRust wipes, tracked like parcels
Tracking details

LiveSave-Inspect

Offline 178.126.210.193:28215 checked 26d ago

moddedoxidepve
Tracking number · connect
Wipe progress · wiped 27d ago
  1. Wipedunder 6 hours
  2. Fillingthe first day
  3. Peakthe first days
  4. Settledlater on
  5. Due againnext wipe close
Next wipe · ETA Thu 5 Nov, 19:00 UK Thu 5 Nov, 19:00 UTC FW in 7d 10h · high confidence
1/ 8 players now 12% full
07-day averagepeak –
#15,332ranktop 67%
27d agolast wipeno schedule published
7d 10hnext wipeThu 5 Nov, 19:00 UTC FW
Delivery history

Players, performance and rank

Players

No hourly history yet.

Hourly average and peak, UTC.

Server performance

This server has not answered a direct query in the last 48 hours.

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
RankRank in region
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 67% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

force wipes only
Next delivery expected

Next wipe Thursday 5 November, 19:00 UTC · 19:00 UK, in 7d 10h.

The force wipe · high confidence
1wipe-day peakplayers, last three wipes

Coming wipes

  1. 7d 10hThu 5 Nov, 19:00 UTC19:00 UKFW
  2. 35d 10hThu 3 Dec, 19:00 UTC19:00 UKFW

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 22 hours in, with 1 in the queue.

Wipes

every wipe as a delivery, newest first
  1. Thu 5 Nov, 19:00 UTC FW19:00 UK · in 7d 10h
    Next wipe expected · the force wipe
  2. Thu 1 Oct, 17:56 UTC FW 18:56 UK · 27d ago
    Force wipe delivered
    Peak
    1 +1 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.

Similar parcels

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 252 on average 130 / 2000
  2. [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 242 on average 105 / 2000
  3. Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 106 on average 44 / 200
  4. 【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 58 on average 66 / 200
  5. [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 54 on average 25 / 300
  6. TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 50 on average 24 / 100
Help desk

Quick answers

From the figures on this page.

Player activity

What is the ranking of LiveSave-Inspect against other Rust servers?

In the top 67% of all ranked servers sits LiveSave-Inspect, at #15,332 on hours played over seven days.

How many players are on LiveSave-Inspect right now?

The last sighting of LiveSave-Inspect was 26 days 17 hours ago; it is offline right now.

Map and rules

Which settings and rules apply on LiveSave-Inspect?

The name of LiveSave-Inspect gives no gather rate. A group holds no more than 50 players. It runs pve, other players cannot be fought. The server browser lists it as Modded, because plugins or settings alter the game. Oxide supplies the plugins. VAC, Valve's anti-cheat, is switched off.

About the server

What is the location of LiveSave-Inspect?

No region is published by LiveSave-Inspect. A server tells Rust Wipe Tracker where it is, and that is what is shown; the machine's real location is not checked. You will find it at 178.126.210.193:28215.

Is LiveSave-Inspect up, and how good is its uptime?

The current status for LiveSave-Inspect is offline, last seen 26 days 17 hours ago. 0% is the uptime for the last 7 full days, up for 0 of 168 hours. The first sighting of it by Rust Wipe Tracker came on 2 October 2026.

What Rust version is LiveSave-Inspect using?

Rust network protocol 2634 and build 166462 on Windows is what LiveSave-Inspect runs. To join, your game must be on the same protocol; Steam handles that update for you.

Map resets

How does LiveSave-Inspect handle its wipe days?

The average busiest point of its recent wipes was 1 players. With 1 more in the queue, the latest wipe peaked 22 hours in.

On what schedule does LiveSave-Inspect reset its map?

Once a month is all LiveSave-Inspect wipes, along with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next one. The world it is running was made 27 days 14 hours.

Tags and listings

On Rust Wipe Tracker, which lists and filters is LiveSave-Inspect part of?

These Rust Wipe Tracker lists take LiveSave-Inspect: Modded Rust servers and Best Rust PvE servers. You will find it under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

What is the meaning of the server tags on LiveSave-Inspect?

gmrust (Game mode): The game mode is standard Rust survival; mp8 (Max players): It holds 8 slots; ts50 (Group limit): Team size caps at 50; v2634 (Protocol): To join, your game must match protocol 2634; cs166462 (Build): It runs game build 166462; ptrak (Networking): Standard network layer here: RakNet; $r? (Region code): A region code isn't set; ^p (PvE): There's no player combat; the world itself is the threat; ^o (Oxide): Oxide (uMod), a plugin framework, is installed here; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing; modded (Modded): The game is changed by plugins or settings, hence the Modded listing; oxidation (Custom tag): The owner or a plugin set this non-standard tag are the tags LiveSave-Inspect publishes, and the server browser takes them as read. Players now, the queue and the world's creation time sit at the top of this page and come from the tags as well.

Getting started

What steps do you take to join LiveSave-Inspect?

Use Launch Rust on this page to join, which opens Rust through Steam and connects you, or start Rust, press F1 and enter client.connect 178.126.210.193:28215.

Server tags

what each one means

Published as mp8,ptrak,$r?,v2634,^p,gmrust,cs166462,ts50,^o^z,oxidation,modded

Game

gmrust
Game mode The game mode is standard Rust survival.
mp8
Max players It holds 8 slots.
ts50
Group limit Team size caps at 50.
v2634
Protocol To join, your game must match protocol 2634.
cs166462
Build It runs game build 166462.
ptrak
Networking Standard network layer here: RakNet.
$r?
Region code A region code isn't set.

Gameplay

^p
PvE There's no player combat; the world itself is the threat.

Mods and access

^o
Oxide Oxide (uMod), a plugin framework, is installed here.
^z
Modded The game is changed by plugins or settings, hence the Modded listing.
modded
Modded The game is changed by plugins or settings, hence the Modded listing.

Other

oxidation
Custom tag The owner or a plugin set this non-standard tag.

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.