Offline 119.252.202.62:28960 checked 20d ago
audit
Connect
srv = rust.server("119.252.202.62:28962")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())Map
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 119.252.202.62:28960
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 9 Oct 2026, 23:19 UTC
- hostname
- –
- first seen
- 9 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 14/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 35/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 8/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 36/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 86 on average | 136/200 |
Quick answers
From the figures on this page.
Player counts
What position does audit take in the server rankings?
Player hours over seven days put audit at #15,833, in the top 72% of the ranked set.
What population does audit carry?
The current row shows audit offline; the last response was 20 days 2 hours ago.
About the server
What Rust version does audit run?
The build is Rust network protocol 2634 and build 167058 on Linux, run by audit. Steam updates your game for you, but the protocol must match to join.
Is audit up, and what does its uptime show?
The latest sample has audit offline, with a last sighting 20 days 2 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 9 October 2026.
Which location does audit run from?
For audit, no region is published. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 119.252.202.62:28960 is its address.
Rules, settings, map
Which rules apply on audit, and what settings?
You will not find a gather rate in the string audit. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. Anti-cheat status: VAC off.
Wipes and dates
When does audit wipe, and on what schedule?
The record for audit holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 20 days 2 hours ago, and that is the one in play.
Lists and tags
Which lists on Rust Data hold audit, and which filters?
The Rust Data lists that audit fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on audit?
Read by the game's server browser, the tags audit publishes are: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): Slot count: 500; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167058 (Build): Build number: 167058; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join audit?
The manual route: launch Rust, F1, then client.connect 119.252.202.62:28960. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.