Online 85.14.198.168:28015 checked 14m ago
BlaKam Testserver
Connect
srv = rust.server("85.14.198.168:28019")
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 17% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()
Its wipes keep no rhythm, so there is no next wipe to predict. 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 2, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 15:28 UTC1d ago | NaN | NaN | running | 0 |
| 1 | Fri 23 Oct, 14:41 UTC5d ago | 2 | held half | 4 days | 0 |
| 2 | Thu 22 Oct, 18:15 UTC6d ago | 2 | NaN | 0.9 days | 0 |
| 3 | Fri 16 Oct, 15:30 UTC12d ago | 2 | held half | 6.1 days | 1 |
| 4 | Sat 10 Oct, 10:38 UTC19d ago | 2 | held half | 6.2 days | 0 |
| 5 | Fri 2 Oct, 08:30 UTC27d ago | 2 | held half | 8.1 days | 1 |
| 6 | Thu 1 Oct, 18:14 UTC FW27d ago | 2 | NaN | 0.6 days | 1 |
| 7 | Sun 27 Sep, 11:04 UTC32d ago | 2 | held half | 4.3 days | 2 |
| 8 | Sat 19 Sep, 11:14 UTC40d ago | 2 | held half | 8 days | 1 |
| 9 | Fri 18 Sep, 17:40 UTC40d ago | 2 | NaN | 0.7 days | 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
5000 · seed 1972576941
- map
- Procedural Map
- size
- 5000
- seed
- 1972576941
Server
srv.info()- address
- 85.14.198.168:28015
- region
- –
- max players
- 32
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 23 Oct 2026, 14:41 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 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 254 on average | 130/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 243 on average | 231/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 107 on average | 41/200 |
| 3 | 【炮炮PVE启蒙】纯净|特色|突袭|技能 | EA · groups of 16+ · biweekly · 58 on average | 93/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 54 on average | 25/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 49 on average | 60/100 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does BlaKam Testserver rank?
Over the last seven days BlaKam Testserver sits at #3,727 on player hours, in the top 17% of ranked servers.
What population does BlaKam Testserver carry?
BlaKam Testserver reports 0 players at this refresh, with 32 slots configured. Over the last seven days it averaged 1 players and peaked at 2. Averaged by hour over 48 hours, 17:00 UTC is the busiest, at 1 players.
Server data
What does performance look like on BlaKam Testserver?
Averaged over 48 hours: 29 server fps, never under 4. The entity count peaked at 150,304, covering buildings, deployables and the rest of the world. A high of 4,232 MB of memory used. Low fps plus an entity count on the way up is the lag players report.
Which Rust version is BlaKam Testserver on?
Rust network protocol 2635 and build 168909 on Linux is what BlaKam Testserver runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is BlaKam Testserver, and is it online now?
BlaKam Testserver reports itself online at the current refresh. The uptime it reports puts the last restart about 7 hours ago. 166 of 168 hours up over the last 7 full days, or 99%. Rust Data logged it first on 13 September 2026.
Which location does BlaKam Testserver run from?
No region is published by BlaKam Testserver. Rust Data does not look up where the machine stands; it shows where a server says it is. 85.14.198.168:28015 is its address.
Map and rules
Which settings and rules does BlaKam Testserver run?
No gather rate appears in the name: BlaKam Testserver. No custom cap; the default of 8 players per group stands. Game mode pve, with this note: no combat between players. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on BlaKam Testserver?
The game generates the map on BlaKam Testserver: procedural, size 5,000, seed 1972576941. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
On what schedule does BlaKam Testserver wipe?
No next wipe can be predicted for BlaKam Testserver, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 5 days 23 hours ago.
On BlaKam Testserver, what happens on wipe day?
Recent wipes averaged 2 players at their peak. Peak population on the latest wipe came 0 hours in. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Tags, lists
Which lists on Rust Data hold BlaKam Testserver, and which filters?
The Rust Data lists that BlaKam Testserver fits are: Modded Rust servers and Rust PvE servers. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on BlaKam Testserver hold?
Read by the game's server browser, the tags BlaKam Testserver publishes are: gmvanilla (Game mode): The mode is vanilla survival; mp32 (Max players): Slot count: 32; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^p (PvE): PvE: the world is the threat, not other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^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.
How to join
How can I connect to BlaKam Testserver?
Enter client.connect 85.14.198.168:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.
