combat
Key statistics
the figures behind the quote- Players now
- 0/ 200 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak 2
- Rank
- #10,035 top 45%
- Rank · 7d ago
- – not ranked a week ago
- Last wipe
- 5d 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
- 5 player hours, last seven days
- Map
- 5000 Procedural Map · seed 69737
- First seen
- 8 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, measured since 8 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 45% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yet- usual gap
- 1.1 days between real wipes
- wipe-day peak
- 2 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 |
|---|---|---|---|---|
| Fri 9 Oct, 21:36 UTC5d ago | 1 | – | running | 0 |
| Thu 8 Oct, 19:01 UTC6d ago | 2 | – | 1.1 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.
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 · 128 on average | 43/300 | ▲+29+212.1% | |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 13.10EU · groups of 16+ · weekly · 108 on average | 44/225 | ▲+3+8.0% | |
| 3 | МИНИ-КАРТА 2Х | STORM | FPS+ 14.10EU · groups of 8+ · weekly · 90 on average | 93/100 | ▲+3+3.0% | |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 10.10EU · groups of 16+ · monthly · 88 on average | 8/1000 | ▼−8−49.5% | |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 08.10EU · groups of 16+ · monthly · 76 on average | 4/1000 | ▼−1−23.8% | |
| 6 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 11.10EU · groups of 16+ · monthly · 72 on average | 20/700 | ▼−3−12.7% |
Quick answers
from the figures on this pageServer Rules
How is combat configured in terms of rules and settings?
The name of combat carries no gather rate. 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. The server browser lists it as Modded: plugins or settings change the game. Oxide plugins are running. The server has VAC, Valve's anti-cheat, switched on.
Which map is played on combat?
combat uses a procedural map of size 5,000 with seed 69737, generated by the game. Because size and seed determine the map, RustMaps offers a view of it from this page.
Population
Where does combat sit in the rankings?
In the top 45% of all ranked servers, combat is #10,035 on player hours over the last seven days.
How full is combat?
At present, combat is offline; the last sighting was 4 days 2 hours ago. The mean over the last seven days is 0 players, reaching 2 at its highest.
Wipe Frequency
What can you expect on wipe day for combat?
Recent wipes at this server drew an average peak of 2 players. 0 hours after the latest wipe, the crowd reached its peak.
When does combat schedule its wipes?
No rhythm can be told for combat 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. Its world now is 5 days 1 hours old.
Server Details
What is the server location for combat?
No region is published by combat. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 134.19.177.230:26069.
combat is on which Rust version?
The version in use at combat: Rust network protocol 2634 and build 167398, on Linux. The protocol has to match for you to join, and Steam applies that update.
What is the uptime and reliability of combat?
combat is down. The last time we saw it was 4 days 2 hours ago. The last 5 full days give 37% uptime, 44 hours on out of 120. First sighting by Rust Analytics: 8 October 2026.
Server Tags
What is the meaning of the tags on combat?
These tags are published by combat and read by the game's server browser: gmrust (Game mode): Survival in the standard Rust format; mp200 (Max players): Slot count: 200; ts8 (Group limit): 8 per team: the default setting, unchanged; v2634 (Protocol): To join, your game needs protocol 2634; cs167398 (Build): It runs build 167398; ptrak (Networking): Runs on RakNet, Rust's default network layer; $r? (Region code): Region code: none set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Modded listing: the game is changed by plugins or settings. The top of this page and the tags both show its players now, its queue and when its world was made.
combat appears in which of the lists and filters on Rust Analytics?
The following Rust Analytics lists feature combat: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How to Join
What is the process to join combat?
Type client.connect 134.19.177.230:26069 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 mp200,ptrak,$r?,v2634,gmrust,cs167398,ts8,^o^z
Game
gmrust
mp200
ts8
v2634
cs167398
ptrak
$r?
Mods and access
^o
^z
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.