Station XX-5306 · no signal
Combat Local - Carbon Dev
Offline 176.115.149.159:28015 checked 1d ago
- Players now
- 1/ 10
- 10% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 1
- peak 2
- Rank
- #5,306
- top 24%
- Last wipe
- 2d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 10 slots
- Motion · 24 h
- M0.0■steady+0 players
- Sharpest hour
- +0into Wed 22:00 UTC
- Peak · 48 h
- 1most players in any hour
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 24% 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
- 0.3 daysbetween real wipes
- wipe-day peak
- 1players, 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 |
|---|---|---|---|---|---|---|
| Tue 27 Oct, 21:20 UTC2d ago | M0.0▲rising | 1 | – | running | 0 | |
| Tue 27 Oct, 15:13 UTC2d ago | M0.0■steady | 1 | – | 0.3 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 pageRules and settings
Which settings and rules apply on Combat Local - Carbon Dev?
You will find no gather rate in the name of Combat Local - Carbon Dev. 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. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. The server has VAC on, Valve's anti-cheat.
Population
How many players are recorded on Combat Local - Carbon Dev right now?
Combat Local - Carbon Dev is not responding at this moment and is offline, last seen 25 hours ago. Averaged across the last seven days the population was 1 players, reaching a peak of 2. The last 48 hours show their highest activity at 09:00 UTC, averaging 1 players.
How does Combat Local - Carbon Dev rank against other Rust servers?
On player hours for the past week, Combat Local - Carbon Dev sits at #5,306, which puts it inside the top 24% of every ranked server.
Server details
How reliably does Combat Local - Carbon Dev stay online?
As recorded now, Combat Local - Carbon Dev is not reachable, the last contact having been 25 hours ago. Of the 96 hours in the last 4 full days, it was up for 38, or 40% of the time. On 24 October 2026 it was recorded for the first time by Rust Server Trends.
Which region does Combat Local - Carbon Dev run from?
No region is published by Combat Local - Carbon Dev. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 176.115.149.159:28015.
Which Rust version is Combat Local - Carbon Dev running?
Combat Local - Carbon Dev is running Rust network protocol 2635 and build 168909 on a machine with Windows. 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 Local - Carbon Dev?
On average, the busiest point of its recent wipes drew 1 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does Combat Local - Carbon Dev run its wipes?
The rhythm of Combat Local - Carbon Dev cannot yet be told: too few of its wipes are on record. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 2 days 2 hours.
Tags
What do the server tags on Combat Local - Carbon Dev mean?
Tags published by Combat Local - Carbon Dev and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does Combat Local - Carbon Dev appear?
These Rust Server Trends lists include Combat Local - Carbon Dev: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
How to join
What steps get you onto Combat Local - Carbon Dev?
You can connect by pressing F1 in Rust and typing client.connect 176.115.149.159:28015 into the console. Another route is to use Launch Rust and join from this page, which opens the game 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.