Offline 95.147.224.99:28015 checked 24d ago
Born To Kill Test
Connect
srv = rust.server("95.147.224.99: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 71% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 19:48 UTC24d 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 95.147.224.99:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 19:48 UTC
- hostname
- –
- first seen
- 4 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 | ABYSS | PvE | US | Vanilla | Noob Friendly | NA · groups of 8+ · monthly · 54 on average | 69/200 |
| 1 | [EU] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | EU · groups of 8+ · monthly · 33 on average | 9/200 |
| 2 | [US] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | NA · groups of 8+ · monthly · 31 on average | 36/200 |
| 3 | 【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 | EA · groups of 30+ · monthly · 22 on average | 16/200 |
| 4 | [PvE] Skyline PvE - No Raiding/Killing, No Decay, Noob Friendly | groups of 8+ · monthly · 21 on average | 22/150 |
| 5 | [EU/GER] Rust Norddeutschland PVE | EU · groups of 8+ · biweekly · 16 on average | 1/100 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does Born To Kill Test rank?
Rank #15,962 on seven-day player hours for Born To Kill Test, within the top 71% of all ranked servers.
How many players does Born To Kill Test hold at once?
Offline now for Born To Kill Test, with the last sample 24 days 6 hours ago.
Server facts
What is the Rust version on Born To Kill Test?
Version Rust network protocol 2634 and build 166652 on Windows is reported by Born To Kill Test. Steam updates your game for you, but the protocol must match to join.
Is Born To Kill Test up, and what does its uptime show?
The latest sample has Born To Kill Test offline, with a last sighting 24 days 6 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 4 October 2026.
In which location is Born To Kill Test hosted?
No region is published by Born To Kill Test. Rust Data does not look up where the machine stands; it shows where a server says it is. 95.147.224.99:28015 is its address.
Settings and map
Which rules apply on Born To Kill Test, and what settings?
The name Born To Kill Test carries no gather rate. The group limit sits at the default of 8 players. Game mode pve, with this note: player combat is not allowed. The server browser lists it under Community. VAC, Valve's anti-cheat, is enabled.
Which map has Born To Kill Test selected?
The game generates its map: procedural, on Born To Kill Test.
Wipe data
On what schedule does Born To Kill Test wipe?
A rhythm cannot be read from the wipes of Born To Kill 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 24 days 7 hours ago, and that is the one in play.
On Born To Kill Test, what happens on wipe day?
The average peak over recent wipes is 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Where does Born To Kill Test appear among Rust Data lists and filters?
These Rust Data lists include Born To Kill Test: Rust community servers, unfiltered and Rust PvE servers. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
How should you read the server tags on Born To Kill Test?
The game's server browser reads these tags from Born To Kill Test: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): 100 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^p (PvE): PvE: the world is the threat, not other players. 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
What is the way into Born To Kill Test?
Enter client.connect 95.147.224.99:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.