audit
Offline 119.252.202.62:28960 checked 8d ago
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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
- 17/ 100
- 266/ 400
- 182/ 225
- 129/ 100
- 328/ 1000
- 23/ 700
Quick answers
Tags and listings
Where does audit appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry audit are: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on audit?
gmrust (Game mode): This is the standard Rust survival experience; mp500 (Max players): There are 500 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167058 (Build): The build number is 167058; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^z (Modded): The Modded category fits: plugins or settings are in play; ^y (Carbon): Plugins are handled by Carbon — that is the tag list audit puts out for the game's server browser. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
Where can you find audit?
No region comes from audit. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 119.252.202.62:28960.
What's the uptime like for audit?
The server audit is not reachable at the moment; the last sighting was 8 days 10 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. The first sighting by Rust Going Deep was on 9 October 2026.
What Rust version is audit on?
Rust network protocol 2634 and build 167058 is what audit runs, on Linux. Steam handles the update; you just need your game on the matching protocol to join.
Wipe schedule
What schedule does audit follow for wipes?
Too few wipes are on record for audit to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 8 days 10 hours is how long ago this world came into being.
Settings and map
Which rules and settings is audit running?
No gather rate appears in the name of audit. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. Carbon plugins are running here. VAC is off: Valve's anti-cheat is not active.
Population
Is audit busy?
The last sighting of audit was 8 days 10 hours ago; it is offline right now.
Where does audit sit in the rankings?
For player hours in the last seven days, audit ranks #15,833, within the top 72% of ranked servers.
How to join
What's the way to join audit?
To join, open Rust, hit F1, and enter client.connect 119.252.202.62:28960. Or click Launch Rust on this page to open the game through Steam and connect.