Offline 77.213.122.114:28015 checked 2d ago
UnityVault Local Test
Connect
srv = rust.server("77.213.122.114:28017")
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 22% 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 24 Oct, 19:07 UTC4d ago | 1 | NaN | running | 1 |
# 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
- 77.213.122.114:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 19:07 UTC
- hostname
- –
- first seen
- 21 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 | 171/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 186/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 80/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 87 on average | 255/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 350/350 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does UnityVault Local Test rank?
Player hours over seven days put UnityVault Local Test at #4,903, in the top 22% of the ranked set.
How many players does UnityVault Local Test hold at once?
The current row shows UnityVault Local Test offline; the last response was 2 days 19 hours ago. Over the last seven days it averaged 1 players and peaked at 3.
Server facts
What is the Rust version on UnityVault Local Test?
Version Rust network protocol 2635 and build 168909 on Windows is reported by UnityVault Local Test. Steam updates your game for you, but the protocol must match to join.
How reliable is UnityVault Local Test, and is it up?
UnityVault Local Test is offline at this refresh; the last response came 2 days 19 hours ago. Over the last 7 full days the hours up number 52 of 168, 31%. Rust Data logged it first on 21 October 2026.
Where does UnityVault Local Test sit?
There is no region published for UnityVault Local Test. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 77.213.122.114:28015 is its address.
Settings and map
Which rules apply on UnityVault Local Test, and what settings?
You will not find a gather rate in the string UnityVault Local Test. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: 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. VAC, Valve's anti-cheat, is enabled.
What is the map on UnityVault Local Test?
A procedural map runs on UnityVault Local Test, generated by the game.
Wipe schedule
When does UnityVault Local Test wipe, and on what schedule?
A rhythm cannot be read from the wipes of UnityVault Local 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. This world was created 4 days 21 hours ago.
What is wipe day on UnityVault Local Test like?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Where does UnityVault Local Test appear among Rust Data lists and filters?
These Rust Data lists include UnityVault Local Test: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on UnityVault Local Test?
These tags are published by UnityVault Local Test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): Slot count: 5; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into UnityVault Local Test?
In Rust, F1 opens the console: type client.connect 77.213.122.114:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.