Offline 31.77.232.53:28150 checked 16d ago
VendorAuditTest
Connect
srv = rust.server("31.77.232.53:28151")
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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 31.77.232.53:28150
- region
- –
- max players
- –
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 8 Oct 2026, 12:26 UTC
- hostname
- –
- first seen
- 11 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 · 159 on average | 44/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 51/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 20/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 6/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does VendorAuditTest rank?
Over the last seven days VendorAuditTest sits at #15,843 on player hours, in the top 72% of ranked servers.
What population does VendorAuditTest carry?
Offline now for VendorAuditTest, with the last sample 16 days 18 hours ago.
Server data
Which Rust version is VendorAuditTest on?
Rust network protocol 2634 and build 167231 on Linux is what VendorAuditTest runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is VendorAuditTest, and is it online now?
Offline now for VendorAuditTest, last seen 16 days 18 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 11 October 2026.
In which location is VendorAuditTest hosted?
No region is published by VendorAuditTest. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 31.77.232.53:28150 is its address.
Rules, settings, map
What rules and settings are recorded for VendorAuditTest?
You will not find a gather rate in the string VendorAuditTest. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has VendorAuditTest selected?
VendorAuditTest runs a procedural map, which the game generates.
Wipe data
On what schedule does VendorAuditTest wipe?
Too few wipes are on record for VendorAuditTest to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 19 days 15 hours ago.
Lists and tags
Which lists on Rust Data hold VendorAuditTest, and which filters?
On Rust Data, VendorAuditTest appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on VendorAuditTest?
These tags are published by VendorAuditTest and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp0 (Max players): The server lists 0 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167231 (Build): Build number: 167231; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way into VendorAuditTest?
In Rust, F1 opens the console: type client.connect 31.77.232.53:28150. Launch Rust on this page does the same by opening the game through Steam and connecting.