Rust Data LabData lab · live
Live readings Servers11,828 Players91,106 Populated3,754 Fresh wipes · 3h433 Sampled every 5 min

Element card · group PvE · atomic number 15,332, its rank

LiveSave-Inspect

Offline 178.126.210.193:28215 checked 27d ago

moddedoxidepve
Join the experiment
Atomic mass · players now 1/ 8 12% full Room to join
7-day average0peak –
Rank · atomic number#15,332top 67%
Last wipe28d agono schedule published
Next wipe6d 21hThu 5 Nov, 19:00 UTC FW
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
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.

Result 03

Rank

Result

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.

Reaction kinetics

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 6d 21h. The force wipe · high confidence

wipe-day peak1players, last three wipes

Coming wipes

  1. 6d 21hThu 5 Nov, 19:00 UTCFW
  2. 34d 21hThu 3 Dec, 19:00 UTCFW

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.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 17:56 UTC FW28d 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
  1. 1 Br [US] Brits PvE… 236
    [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo NA · no group limit · biweekly · 253 on average 236/ 2,000
  2. 2 Br [EU] Brits PvE… 265
    [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 243 on average 265/ 2,000
  3. 3 Ch Chrayntopia ♡ … 77
    Chrayntopia ♡ ︎PvE | RP | PvP NA · groups of 8+ · biweekly · 106 on average 77/ 200
  4. 4 纯净 【炮炮PVE启蒙】纯净|特色… 26
    【炮炮PVE启蒙】纯净|特色|突袭|技能 EA · groups of 16+ · biweekly · 59 on average 26/ 200
  5. 5 Re [PvE] Relic | … 58
    [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl groups of 30+ · monthly · 54 on average 58/ 300
  6. 6 Tr TRAVELER PVE [… 41
    TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 49 on average 41/ 100

Quick answers

from the figures on this page

Server setup

What settings and rules apply on LiveSave-Inspect?

Nothing in the name of LiveSave-Inspect gives a gather rate. Group size is capped at 50 players. pve is the game mode, other players cannot be fought. In the server browser it sits under Modded: the game is changed by plugins or settings. Oxide plugins are running on it. The VAC anti-cheat from Valve is disabled.

Server details

In what location does LiveSave-Inspect sit?

Nothing about a region is published by LiveSave-Inspect. Rust Data Lab shows a server's stated location, not a verified position of the machine. Connect at 178.126.210.193:28215.

Which Rust version is LiveSave-Inspect on?

On Windows, LiveSave-Inspect is running Rust network protocol 2634 and build 166462. Your game needs to match the protocol to join, and Steam updates it automatically.

How dependable is LiveSave-Inspect for staying online?

LiveSave-Inspect is not online at the moment; the last sighting was 27 days 5 hours ago. For the last 7 full days, 0 of 168 hours were online, giving 0% uptime. On 2 October 2026, Rust Data Lab saw it for the first time.

Wipes and resets

How often does a wipe happen on LiveSave-Inspect, and at what time?

The only wipe on LiveSave-Inspect is the monthly force wipe. On Thursday 5 November at 19:00 UTC, this server wipes again: that is the force wipe that resets all Rust servers. 28 days 3 hours ago the current world was made.

What does a typical wipe day on LiveSave-Inspect involve?

Recent wipes on average reached 1 players at their busiest. 22 hours after the latest wipe the crowd peaked, and a further 1 waited in the queue.

Tags, lists

Which meanings sit behind the tags on LiveSave-Inspect?

These are the tags LiveSave-Inspect makes public for the server browser to read: gmrust (Game mode): Standard Rust survival is the game here; mp8 (Max players): 8 is the slot count; ts50 (Group limit): The team limit is 50; v2634 (Protocol): The server runs protocol 2634, so your game needs the same version; cs166462 (Build): The game build is 166462; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): The region field is left blank; ^p (PvE): There is no player combat here, only the world's threats; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): You will find it under Modded: the game is altered by plugins or settings; modded (Modded): You will find it under Modded: the game is altered by plugins or settings; oxidation (Custom tag): A plugin or the owner set this tag; it is not standard Rust. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.

Where among the Rust Data Lab lists and filters does LiveSave-Inspect come up?

You will find LiveSave-Inspect on the following Rust Data Lab lists: Modded Rust servers, measured and Best Rust PvE servers, measured live. You can find it on the server list by applying these filters: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.

Player counts

What position does LiveSave-Inspect hold among Rust servers?

Player hours over the last week put LiveSave-Inspect at #15,332, inside the top 67% of ranked servers.

What does the current player count on LiveSave-Inspect tell you?

No live signal from LiveSave-Inspect right now, which was last seen 27 days 5 hours ago.

Getting on

How can you connect to LiveSave-Inspect?

You can connect by pressing F1 in Rust and entering client.connect 178.126.210.193:28215, or by pressing Launch Rust here, which starts the game through Steam and joins for you.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game here.
mp8
Max players 8 is the slot count.
ts50
Group limit The team limit is 50.
v2634
Protocol The server runs protocol 2634, so your game needs the same version.
cs166462
Build The game build is 166462.
ptrak
Networking This runs on RakNet, the standard layer.
$r?
Region code The region field is left blank.

Gameplay

^p
PvE There is no player combat here, only the world's threats.

Mods and access

^o
Oxide Plugins run through Oxide (uMod).
^z
Modded You will find it under Modded: the game is altered by plugins or settings.
modded
Modded You will find it under Modded: the game is altered by plugins or settings.

Other

oxidation
Custom tag A plugin or the owner set this tag; it is not standard Rust.

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.