Working its way up from the back of the class: #15,349 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 224 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
W·····W
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap3.8 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Sun 25 OctMon 19 OctSat 17 Oct
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 25 Oct, 06:49 UTC3d ago
0
–
running
0
Mon 19 Oct, 11:05 UTC9d ago
0
–
5.8 days
0
Sat 17 Oct, 14:06 UTC11d ago
0
–
1.9 days
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
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for GAMEPLAY-AUDIT-ISOLATED. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 95.182.82.154:28715.
How reliable is GAMEPLAY-AUDIT-ISOLATED, and is it up?
At this moment, GAMEPLAY-AUDIT-ISOLATED is offline; the last time it was seen was 3 days 21 hours ago. It was up 1% of the time over the last 7 full days, 1 of 168 hours. It was first seen by Rust Server Score on 17 October 2026.
Which Rust version is GAMEPLAY-AUDIT-ISOLATED running?
You will find GAMEPLAY-AUDIT-ISOLATED on Rust network protocol 2634 and build 167781, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does GAMEPLAY-AUDIT-ISOLATED reset?
There is no next wipe to predict on GAMEPLAY-AUDIT-ISOLATED, as it wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 3 days 21 hours have passed since this world was made.
What happens on GAMEPLAY-AUDIT-ISOLATED when wipe day arrives?
Recent wipes have peaked at 0 players on average. 0 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does GAMEPLAY-AUDIT-ISOLATED place in the wider field of Rust servers?
Over the last seven days, GAMEPLAY-AUDIT-ISOLATED has #15,349 for player hours, in the top 69% of all ranked servers.
Is GAMEPLAY-AUDIT-ISOLATED a busy server?
GAMEPLAY-AUDIT-ISOLATED is offline at the moment; the last time it was seen was 3 days 21 hours ago. For the last seven days, the average number of players was 0.
Lists and filters
How should you read the tags on GAMEPLAY-AUDIT-ISOLATED?
The game's browser takes its cue from the tags GAMEPLAY-AUDIT-ISOLATED has set: gmrust (Game mode): Survival in the standard Rust style; mp0 (Max players): Its slot count is 0; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): Plugin framework: Carbon. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show GAMEPLAY-AUDIT-ISOLATED?
These Rust Server Score lists count GAMEPLAY-AUDIT-ISOLATED among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Map and rules
Which rules does GAMEPLAY-AUDIT-ISOLATED enforce, and what are its settings?
You will find no gather rate in the name of GAMEPLAY-AUDIT-ISOLATED. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. The server does not run VAC, Valve's anti-cheat.
Can you tell me which map GAMEPLAY-AUDIT-ISOLATED uses?
A procedural map, generated by the game, is what GAMEPLAY-AUDIT-ISOLATED runs.
Connecting
How should you connect to GAMEPLAY-AUDIT-ISOLATED?
To connect, start Rust, press F1, and type client.connect 95.182.82.154:28715. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp0
Max playersIts slot count is 0.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonPlugin framework: Carbon.
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).