Station XX-15863 · no signal
combat
Offline 134.19.177.230:26069 checked 18d ago
- Players now
- 0/ 200
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,863
- top 72%
- Last wipe
- 19d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 200 slots
- Motion · 24 h
- M –not enough readings
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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 1.1 daysbetween real wipes
- wipe-day peak
- 2players, 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 9 Oct, 21:36 UTC19d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 8 Oct, 19:01 UTC20d ago | M0.0▲rising | 2 | – | 1.1 days | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageServer rules
Which map is running on combat?
combat runs a procedural map of size 5,000 with seed 69737, produced by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on combat?
You will find no gather rate in the name of combat. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on combat right now?
combat is not responding at this moment and is offline, last seen 18 days 21 hours ago.
How does combat rank against other Rust servers?
Over the last seven days, combat recorded enough player hours to reach #15,863 worldwide, placing it in the top 72% of all ranked servers.
Server facts
How reliably does combat stay online?
No contact with combat right now, and the last recorded contact was 18 days 21 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 8 October 2026 is when Rust Server Trends first recorded it.
Where in the world is combat hosted?
Nothing about a region comes from combat. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 134.19.177.230:26069 is the address it uses.
Which Rust version is combat running?
On Linux, combat runs Rust network protocol 2634 and build 167398. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on combat?
2 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.
How often does combat wipe, and on which days?
Too few wipes of combat are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. The present world dates from 19 days 19 hours.
Server tags
What do the server tags on combat mean?
The game's server browser reads the tags combat publishes: gmrust (Game mode): Survival in standard Rust; mp200 (Max players): Slots: 200; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167398 (Build): Game build: 167398; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does combat appear?
You will find combat on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How to join
What steps get you onto combat?
Enter client.connect 134.19.177.230:26069 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.