Station XX-16765 · no signal
LivingIsland persistence validation
Offline 82.8.134.228:28115 checked 17d ago
- Players now
- 0/ ?
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,765
- top 70%
- Last wipe
- 17d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of ? 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
- usual gap
- 0.4 daysbetween real wipes
- on rhythm
- 33%of its recent wipes
- wipe-day peak
- 0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW15d ago | – | – | – | – | running | – |
| Tue 3 Nov, 20:21 UTC17d ago | M0.0■steady | 0 | – | – | 0 | |
| Tue 3 Nov, 06:08 UTC18d ago | M0.0■steady | 0 | – | 0.6 days | 0 | |
| Mon 2 Nov, 19:44 UTC18d ago | M0.0■steady | 0 | – | 0.4 days | 0 | |
| Mon 2 Nov, 12:30 UTC19d ago | M0.0■steady | 0 | – | 0.3 days | 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 pageRules and settings
Which map is running on LivingIsland persistence validation?
The map on LivingIsland persistence validation is procedural, produced by the game.
Which settings and rules apply on LivingIsland persistence validation?
No gather rate appears in the name of LivingIsland persistence validation. Groups hold up to 8 players, which is the default for the game. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Listed as Modded in the server browser, it changes the game through plugins or settings. Carbon is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
How many players are recorded on LivingIsland persistence validation right now?
A reading taken now finds LivingIsland persistence validation offline; the most recent activity was 17 days 13 hours ago.
How does LivingIsland persistence validation rank against other Rust servers?
Over the last seven days, LivingIsland persistence validation recorded enough player hours to reach #16,765 worldwide, placing it in the top 70% of all ranked servers.
Operator and location
How reliably does LivingIsland persistence validation stay online?
LivingIsland persistence validation is down at the moment; the last recorded contact was 17 days 13 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 1 November 2026.
Where in the world is LivingIsland persistence validation hosted?
A region is not published by LivingIsland persistence validation. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 82.8.134.228:28115 is the address it uses.
What build of Rust does LivingIsland persistence validation use?
On Windows, LivingIsland persistence validation runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.
Wipe day
What does wipe day look like on LivingIsland persistence validation?
The recent wipes averaged a busiest count of 0 players. 0 hours into the latest wipe, the crowd reached its peak.
On what timetable does LivingIsland persistence validation run its wipes?
No next wipe can be predicted for LivingIsland persistence validation, which wipes at irregular times. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 17 days 14 hours.
Tags
What do the server tags on LivingIsland persistence validation mean?
These are the tags LivingIsland persistence validation publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp0 (Max players): 0 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): Game protocol 2635: to join, your game must match this version; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. 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 LivingIsland persistence validation appear?
You will find LivingIsland persistence validation on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Join the server
How do you connect to LivingIsland persistence validation?
Enter client.connect 82.8.134.228:28115 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust 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.