combat
Offline 5.3.223.53:28015 checked 17d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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- 659/700
- 418/475
- 37/250
- 56/250
- 222/200
- 112/150
Quick answers
from the figures on this pageReset cycle
What wipe timing does combat follow?
The rhythm of combat's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 17 days 19 hours ago.
Lists and filters
How should you read the tags on combat?
Tags published by combat, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167398 (Build): Game build reading: 167398; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does combat appear in Rust Metrics lists and filters?
Rust Metrics lists featuring combat: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does combat sit in the rankings?
Player hours over seven days put combat at #15,883, in the top 72% of all ranked servers.
What is the population on combat?
combat is not responding; status offline, last seen 17 days 19 hours ago.
Operator and location
Where does combat sit?
No region comes from combat. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 5.3.223.53:28015.
What Rust version is combat on?
Rust network protocol 2634 and build 167398 on Windows is the build combat runs. Check: protocol. To join, your game must match; Steam handles the update.
Is combat up, and how often does it stay up?
Reading: offline. combat last answered 17 days 19 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 10 October 2026, recorded by Rust Metrics.
Map and rules
How is combat configured, and what rules are in force?
No gather rate appears in the name: combat. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on combat?
Check: map. Procedural, generated by the game, on combat.
How to join
How can you get onto combat?
To join: start Rust, press F1 and type client.connect 5.3.223.53:28015. Or press Launch Rust here and Steam opens the game and connects you.