Offline 212.70.99.192:28085 checked 9d ago
Vigil Big Test
Connect
srv = rust.server("212.70.99.192:28087")
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 69% 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
- 212.70.99.192:28085
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 19 Oct 2026, 03:28 UTC
- hostname
- –
- first seen
- 19 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 · 157 on average | 94/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.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 · 116 on average | 102/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 82/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 28/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 18/1000 |
Quick answers
From the figures on this page.
Population data
How does Vigil Big Test compare in the rankings?
Player hours over seven days put Vigil Big Test at #15,297, in the top 69% of the ranked set.
How full does Vigil Big Test run?
The current row shows Vigil Big Test offline; the last response was 9 days 18 hours ago.
About the server
Which Rust version is Vigil Big Test on?
Rust network protocol 2634 and build 167781 on Windows is what Vigil Big Test runs. Joining needs the same protocol on your game; Steam handles the update.
Is Vigil Big Test up, and what does its uptime show?
Offline now for Vigil Big Test, last seen 9 days 18 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 19 October 2026.
Which location does Vigil Big Test run from?
For Vigil Big Test, 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. 212.70.99.192:28085 is its address.
Settings and map
Which rules apply on Vigil Big Test, and what settings?
The name Vigil Big Test carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and 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. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Vigil Big Test selected?
A procedural map runs on Vigil Big Test, generated by the game.
Wipe data
When does Vigil Big Test wipe, and on what schedule?
A rhythm cannot be read from the wipes of Vigil Big Test 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 9 days 18 hours ago, and that is the one in play.
Tags and filters
Where does Vigil Big Test appear among Rust Data lists and filters?
On Rust Data, Vigil Big Test 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; Last wipe: In the last 2 weeks.
How should you read the server tags on Vigil Big Test?
Read by the game's server browser, the tags Vigil Big Test publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): The server runs build 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Connecting
How can I connect to Vigil Big Test?
The manual route: launch Rust, F1, then client.connect 212.70.99.192:28085. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.