Offline 51.254.174.133:21565 checked 23d ago
PimpMyRust QA — native audit
Connect
srv = rust.server("51.254.174.133:21566")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
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, measured since 6 Oct. 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 71% 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
1000 · seed 1
- map
- Procedural Map
- size
- 1000
- seed
- 1
Server
srv.info()- address
- 51.254.174.133:21565
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 6 Oct 2026, 15:52 UTC
- hostname
- –
- first seen
- 6 Oct 2026
About this server · in its own words
print(srv.description)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 | 62/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 112/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 36/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 119/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 347/350 |
Quick answers
From the figures on this page.
Population data
How does PimpMyRust QA — native audit compare in the rankings?
Player hours over seven days put PimpMyRust QA — native audit at #15,990, in the top 71% of the ranked set.
How many players does PimpMyRust QA — native audit hold at once?
PimpMyRust QA — native audit returns no live count at this refresh, having last been seen 23 days 4 hours ago.
Server facts
What Rust version does PimpMyRust QA — native audit run?
Rust network protocol 2634 and build 166652 on Linux is what PimpMyRust QA — native audit runs. The protocol has to match before you can join, and Steam does the updating.
Is PimpMyRust QA — native audit up, and what does its uptime show?
The latest sample has PimpMyRust QA — native audit offline, with a last sighting 23 days 4 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 6 October 2026.
Where does PimpMyRust QA — native audit sit?
There is no region published for PimpMyRust QA — native audit. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 51.254.174.133:21565.
Map and rules
Which settings and rules does PimpMyRust QA — native audit run?
You will not find a gather rate in the string PimpMyRust QA — native audit. The group limit sits at the default of 8 players. Recorded as survival, gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on PimpMyRust QA — native audit?
Size 1,000, seed 1: the procedural map on PimpMyRust QA — native audit, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe data
When does PimpMyRust QA — native audit wipe, and how often?
A rhythm cannot be read from the wipes of PimpMyRust QA — native audit on record, which are too few. 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 23 days 5 hours ago, and that is the one in play.
Lists and tags
Which lists on Rust Data hold PimpMyRust QA — native audit, and which filters?
These Rust Data lists include PimpMyRust QA — native audit: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on PimpMyRust QA — native audit?
These tags are published by PimpMyRust QA — native audit and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp0 (Max players): The server lists 0 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
What is the way into PimpMyRust QA — native audit?
Enter client.connect 51.254.174.133:21565 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.