Born To Kill Test
Key statistics
the figures behind the quote- Players now
- 0/ 100 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,962 top 71%
- Rank · 7d ago
- #16,953 ▲991 places up
- Last wipe
- 10d ago no schedule published
- Next wipe
- – too few wipes seen yet
- Group limit
- 8 8, the default
- Gather rate
- – no rate in the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 4 Oct 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- wipe-day peak
- 0 players, last three wipes
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| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 4 Oct, 19:48 UTC10d ago | 0 | – | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | [EU] RustEZ Pure PvE | Low Decay | No Killing | No RaidingEU · groups of 8+ · monthly · 60 on average | 61/200 | ▼−7−9.9% | |
| 2 | [US] RustEZ Pure PvE | Low Decay | No Killing | No RaidingNA · groups of 8+ · monthly · 50 on average | 27/200 | ▼−1−5.0% | |
| 3 | ABYSS | PvE | US | Vanilla | Noob FriendlyNA · groups of 8+ · monthly · 37 on average | 20/200 | ▪+0−2.4% | |
| 4 | JP Infinity Connect PvEEA · groups of 8+ · monthly · 31 on average | 50/300 | ▲+10+24.0% | |
| 5 | 【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍EA · groups of 30+ · monthly · 28 on average | 45/200 | ▲+7+17.9% | |
| 6 | Stillwater Shores PVE | PVPNA · groups of 30+ · monthly · 19 on average | 13/100 | ▲+2+16.4% |
Quick answers
from the figures on this pageServer Rules
What settings and rules are in place on Born To Kill Test?
No gather rate appears in the name of Born To Kill Test. Groups can contain a maximum of 8 players, the default for the game. pve is the mode, player-versus-player combat is absent. You will find it under Community in the server browser: it is a community server. The server has VAC, Valve's anti-cheat, switched on.
What is the current map on Born To Kill Test?
Born To Kill Test uses a procedural map, which the game generates.
Activity
What is the rank of Born To Kill Test?
In the top 71% of all ranked servers, Born To Kill Test is #15,962 on player hours over the last seven days.
What is the population on Born To Kill Test?
At present, Born To Kill Test is offline; the last sighting was 10 days 18 hours ago.
Wipe Cycle
What can you expect on wipe day for Born To Kill Test?
An average of 0 players marked the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd reached its peak.
How often does Born To Kill Test wipe?
No rhythm can be told for Born To Kill Test yet: too few of its wipes are on record. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. 10 days 19 hours ago the current world was created.
Server Info
What is the location of Born To Kill Test?
For Born To Kill Test, no region is published. Where a server says it is, Rust Analytics shows; where the machine stands, it does not look up. 95.147.224.99:28015 is its address.
Born To Kill Test runs which version of Rust?
The build is Rust network protocol 2634 and build 166652 on Windows, running on Born To Kill Test. Joining requires the same protocol on your game, which Steam updates.
What is the uptime and reliability of Born To Kill Test?
Offline at this moment: Born To Kill Test. Last seen 10 days 18 hours ago. 7 full days have passed with 0% uptime, 0 of 168 hours. First sighting by Rust Analytics: 4 October 2026.
Server Tags
How should you interpret the tags on Born To Kill Test?
The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): It holds 100 slots; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs166652 (Build): Build 166652; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): Region code: none set; ^p (PvE): No fighting between players: the world is the threat, which Born To Kill Test publishes. The tags also carry its current players, queue and world creation time; this page shows them at the top.
On Rust Analytics, which lists and filters feature Born To Kill Test?
These Rust Analytics lists include Born To Kill Test: Rust community servers and Best Rust PvE servers. These filters bring it up 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; Last wipe: In the last 2 weeks.
Connection
What steps do I take to join Born To Kill Test?
Type client.connect 95.147.224.99:28015 after pressing F1 in Rust to open the console. The Launch Rust button on this page does the same, opening Rust through Steam and connecting you.
Server tags
what each one meansPublished as mp100,ptrak,$r?,v2634,^p,gmrust,cs166652,ts8
Game
gmrust
mp100
ts8
v2634
cs166652
ptrak
$r?
Gameplay
^p
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.