Offline 85.190.163.189:10100 checked 20d ago
PK Test Server
Connect
srv = rust.server("85.190.163.189:10101")
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 6d 19h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 19h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 19h | 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, 17:53 UTC FW28d 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
3500 · seed 6738
- map
- Procedural Map
- size
- 3500
- seed
- 6738
Server
srv.info()- address
- 85.190.163.189:10100
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 17:53 UTC
- hostname
- –
- first seen
- 13 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 | 33/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 127/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 120 on average | 65/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 20/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 67/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 267/310 |
Quick answers
From the figures on this page.
Player counts
How does PK Test Server compare in the rankings?
Rank #15,854 on seven-day player hours for PK Test Server, within the top 72% of all ranked servers.
How many players does PK Test Server hold at once?
The current row shows PK Test Server offline; the last response was 20 days 22 hours ago.
About the server
Which Rust version is PK Test Server on?
The build is Rust network protocol 2634 and build 167231 on Windows, run by PK Test Server. Steam updates your game for you, but the protocol must match to join.
How reliable is PK Test Server, and is it up?
PK Test Server is offline at this refresh; the last response came 20 days 22 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 13 September 2026.
Which location does PK Test Server run from?
No region is published by PK Test Server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 85.190.163.189:10100.
Settings and map
What rules and settings are recorded for PK Test Server?
The name PK Test Server carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
What is the map on PK Test Server?
The game generates the map on PK Test Server: procedural, size 3,500, seed 6738. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe schedule
When does PK Test Server wipe, and on what schedule?
A single wipe each month, the force wipe, is all PK Test Server does. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. A new world was started 28 days 5 hours ago, and that is the one in play.
On PK Test Server, what happens on wipe day?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which Rust Data filters and lists contain PK Test Server?
These Rust Data lists include PK Test Server: 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.
How should you read the server tags on PK Test Server?
These tags are published by PK Test Server and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp20 (Max players): The server lists 20 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167231 (Build): Build number: 167231; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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
How can I connect to PK Test Server?
The manual route: launch Rust, F1, then client.connect 85.190.163.189:10100. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.
