Station XX-15420 · no signal
GAMEPLAY-AUDIT-ISOLATED
Offline 95.182.82.154:28715 checked 2d ago
- Players now
- 0/ ?
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,420
- top 69%
- Last wipe
- 2d 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 69% 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
- 3.8 daysbetween real wipes
- on rhythm
- 0%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 |
|---|---|---|---|---|---|---|
| Sun 25 Oct, 06:49 UTC2d ago | M0.0■steady | 0 | – | – | running | 0 |
| Mon 19 Oct, 11:05 UTC8d ago | M0.0■steady | 0 | – | 5.8 days | 0 | |
| Sat 17 Oct, 14:06 UTC10d ago | M0.0■steady | 0 | – | 1.9 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 GAMEPLAY-AUDIT-ISOLATED?
The map on GAMEPLAY-AUDIT-ISOLATED is procedural, produced by the game.
Which settings and rules apply on GAMEPLAY-AUDIT-ISOLATED?
You will find no gather rate in the name of GAMEPLAY-AUDIT-ISOLATED. The group limit is 8 players, the game's default. survival is the game mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. The server has VAC off, Valve's anti-cheat.
Population
How many players are recorded on GAMEPLAY-AUDIT-ISOLATED right now?
A reading taken now finds GAMEPLAY-AUDIT-ISOLATED offline; the most recent activity was 2 days 20 hours ago. The population averaged 0 players over the past week.
How does GAMEPLAY-AUDIT-ISOLATED rank against other Rust servers?
On player hours for the past week, GAMEPLAY-AUDIT-ISOLATED sits at #15,420, which puts it inside the top 69% of every ranked server.
Server details
How reliably does GAMEPLAY-AUDIT-ISOLATED stay online?
GAMEPLAY-AUDIT-ISOLATED is down at the moment; the last recorded contact was 2 days 20 hours ago. Of the 168 hours in the last 7 full days, it was up for 1, or 1% of the time. Its earliest appearance in the records of Rust Server Trends dates to 17 October 2026.
Where in the world is GAMEPLAY-AUDIT-ISOLATED hosted?
A region is not published by GAMEPLAY-AUDIT-ISOLATED. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 95.182.82.154:28715 is the address it uses.
Which Rust version is GAMEPLAY-AUDIT-ISOLATED running?
GAMEPLAY-AUDIT-ISOLATED is running Rust network protocol 2634 and build 167781 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on GAMEPLAY-AUDIT-ISOLATED?
0 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.
How often does GAMEPLAY-AUDIT-ISOLATED wipe, and on which days?
No next wipe can be predicted for GAMEPLAY-AUDIT-ISOLATED, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 2 days 20 hours.
Lists and tags
What do the server tags on GAMEPLAY-AUDIT-ISOLATED mean?
Tags published by GAMEPLAY-AUDIT-ISOLATED and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp0 (Max players): Slots: 0; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does GAMEPLAY-AUDIT-ISOLATED appear?
You will find GAMEPLAY-AUDIT-ISOLATED on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
Connecting
How do you connect to GAMEPLAY-AUDIT-ISOLATED?
To join, enter client.connect 95.182.82.154:28715 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.