Combat Bov
Key statistics
the figures behind the quote- Players now
- 1/ 5 20% full
- Change · 24h
- ▪+0 +0.0% from 1
- 7-day average
- 0 peak 1
- Rank
- #10,442 top 47%
- Rank · 7d ago
- #8,569 ▼1873 places down
- Last wipe
- 11d 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
- 4 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 3 Oct 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC. Busiest hour of the two days: 1 players.
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 47% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- wipe-day peak
- 1 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 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 3 Oct, 22:07 UTC11d ago | 1 | – | 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 | ShockRust | Blue | NoLimitno group limit · 129 on average | 22/300 | ▲+8+59.7% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 109 on average | 16/225 | ▼−4−20.3% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 91/100 | ▲+2+1.8% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 88 on average | 4/1000 | ▼−1−17.2% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 2/1000 | ▲+2 | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 73 on average | 11/700 | ▲+3+45.1% |
Quick answers
from the figures on this pageMap and Rules
How is Combat Bov configured in terms of rules and settings?
No gather rate appears in the name of Combat Bov. The default group size of 8 players applies here. It runs survival, gather, build and raid in the standard game. Combat and raiding between players are allowed. Modded is its category in the server browser; plugins or settings modify the game. Carbon plugins are running. The server has VAC, Valve's anti-cheat, switched on.
Which map is played on Combat Bov?
The game generates the procedural map on Combat Bov.
Population
Where does Combat Bov sit in the rankings?
For the last seven days, Combat Bov holds rank #10,442 on player hours, in the top 47% of all ranked servers.
How many players does Combat Bov have?
At present, Combat Bov is offline; the last sighting was 3 hours ago. Average players over seven days: 0; peak: 1. The busiest hour in the last 48 hours was 19:00 UTC, with an average of 1 players.
Wipe Schedule
How does Combat Bov handle wipe day?
Recent wipes at this server drew an average peak of 1 players. 0 hours after the latest wipe, the crowd reached its peak.
When does Combat Bov schedule its wipes?
The record holds too few of Combat Bov's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. This world has been running for 11 days 3 hours.
Server Details
What is the location of Combat Bov?
There is no region published for Combat Bov. Rust Analytics reports the location a server claims, not the machine's actual location. You can reach it at 185.54.57.12:28015.
Combat Bov runs which version of Rust?
The build is Rust network protocol 2634 and build 167781 on Windows, running on Combat Bov. Your game needs the same protocol to get in; Steam takes care of the update.
What is the uptime and reliability of Combat Bov?
Combat Bov is down. The last time we saw it was 3 hours ago. 7 full days have passed with 11% uptime, 19 of 168 hours. 3 October 2026 is when Rust Analytics first saw it.
Server Tags
How should you interpret the tags on Combat Bov?
These tags are published by Combat Bov and read by the game's server browser: gmrust (Game mode): Rust's standard survival mode; mp5 (Max players): Slot count: 5; ts8 (Group limit): Team size stays at the game default of 8; v2634 (Protocol): To join, your game needs protocol 2634; cs167781 (Build): Game build: 167781; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): The region code is absent; ^z (Modded): Categorised as Modded: plugins or settings alter gameplay; ^y (Carbon): The plugin framework here is Carbon. The top of this page and the tags both show its players now, its queue and when its world was made.
Combat Bov appears in which of the lists and filters on Rust Analytics?
The following Rust Analytics lists feature Combat Bov: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Joining the Server
How can I connect to Combat Bov?
Type client.connect 185.54.57.12: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 mp5,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
mp5
ts8
v2634
cs167781
ptrak
$r?
Mods and access
^z
^y
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.