Offline 185.189.255.239:35200 checked 21d ago
Test KZV
Connect
srv = rust.server("185.189.255.239:35210")
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 17 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 best
Top 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()
Next wipe Thursday 5 November, 19:00 UTC, in 7d 5h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 5h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 5h | Thu 3 Dec, 19:00 UTC | FW 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 | Thu 1 Oct, 21:01 UTC FW27d 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())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 84/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 29/1000 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 84 on average | 273/700 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 73 on average | 107/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10 | EU · groups of 16+ · monthly · 67 on average | 20/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 66 on average | 402/1000 |
Quick answers
From the figures on this page.
Population data
How does Test KZV compare in the rankings?
Player hours over seven days put Test KZV at #15,901, in the top 72% of the ranked set.
How full does Test KZV run?
The current row shows Test KZV offline; the last response was 21 days 16 hours ago.
Server data
What is the Rust version on Test KZV?
The build is Rust network protocol 2634 and build 166494 on Windows, run by Test KZV. Joining needs the same protocol on your game; Steam handles the update.
Is Test KZV up, and what does its uptime show?
The latest sample has Test KZV offline, with a last sighting 21 days 16 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 13 September 2026.
Where does Test KZV sit?
There is no region published for Test KZV. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 185.189.255.239:35200.
Map and rules
Which settings and rules does Test KZV run?
You will not find a gather rate in the string Test KZV. 10 players is the maximum per group. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Which map has Test KZV selected?
Size 3,500, seed 516156: the procedural map on Test KZV, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. Custom Map is what the map name field says.
Wipes and dates
When does Test KZV wipe, and how often?
Once a month Test KZV wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. A new world was started 27 days 16 hours ago, and that is the one in play. Its tags carry a monthly wipe schedule.
What is wipe day on Test KZV like?
Across recent wipes the busiest point averaged 0 players. Peak population on the latest wipe came 0 hours in.
Lists and tags
Which lists on Rust Data hold Test KZV, and which filters?
These Rust Data lists include Test KZV: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on Test KZV?
Read by the game's server browser, the tags Test KZV publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): 50 slots in total; ts10 (Group limit): No team may exceed 10; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166494 (Build): The server runs build 166494; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^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
What is the way into Test KZV?
The manual route: launch Rust, F1, then client.connect 185.189.255.239:35200. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.
