Offline 95.31.211.231:30000 checked 26d ago
VMHub Rust Test
Connect
srv = rust.server("95.31.211.231:30001")
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, measured since 27 Sep. 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 12:01 UTC27d ago | 0 | NaN | running | 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.
display(srv.map, srv.info())Map
3000 · seed 27642026
- map
- Procedural Map
- size
- 3000
- seed
- 27642026
Server
srv.info()- address
- 95.31.211.231:30000
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 12:01 UTC
- hostname
- –
- first seen
- 27 Sep 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 · 149 on average | 162/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 184/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 74/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 14/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 22/1000 |
Quick answers
From the figures on this page.
Population
How does VMHub Rust Test compare in the rankings?
Over the last seven days VMHub Rust Test sits at #15,967 on player hours, in the top 70% of ranked servers.
How many players does VMHub Rust Test hold at once?
VMHub Rust Test returns no live count at this refresh, having last been seen 26 days 6 hours ago.
Server facts
What Rust version does VMHub Rust Test run?
Version Rust network protocol 2634 and build 166586 on Linux is reported by VMHub Rust Test. Steam updates your game for you, but the protocol must match to join.
How reliable is VMHub Rust Test, and is it up?
The latest sample has VMHub Rust Test offline, with a last sighting 26 days 6 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 27 September 2026.
In which location is VMHub Rust Test hosted?
For VMHub Rust Test, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 95.31.211.231:30000 is its address.
Settings and map
What rules and settings are recorded for VMHub Rust Test?
The name VMHub Rust Test carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
What is the map on VMHub Rust Test?
The game generates the map on VMHub Rust Test: procedural, size 3,000, seed 27642026. Size and seed fix the map, so RustMaps can show it, linked from this page.
Wipe schedule
On what schedule does VMHub Rust Test wipe?
The record for VMHub Rust Test 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. The world it runs now was generated 27 days ago.
On VMHub Rust Test, what happens on wipe day?
Recent wipes averaged 0 players at their peak. Peak population on the latest wipe came 0 hours in.
Lists and tags
Where does VMHub Rust Test appear among Rust Data lists and filters?
The Rust Data lists that VMHub Rust Test fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on VMHub Rust Test hold?
Read by the game's server browser, the tags VMHub Rust Test publishes are: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to VMHub Rust Test?
The manual route: launch Rust, F1, then client.connect 95.31.211.231:30000. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you. https://vmhub.ru is the website recorded for it.