Rust Server TrendsSeismic network · station log
Recording Stations11,810 Players75,437 Active3,743 Wipes · 3 h107 48 h

Station XX-13089 · no signal

Combat Local - Carbon Dev

Offline 167.17.58.31:28015 checked 2d ago

moddedcarbon
Connect
Players now
1/ 10
10% full
Motion · 24 h
M –
too few hourly readings
7-day average
1
peak 1
Rank
#13,089
top 59%
Last wipe
2d ago
no schedule published
Next wipe
–
no wipe seen yet
Seismic record · station XX-13089 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 10 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Oct27 Oct28 Oct

Top 59% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 157 on average
109/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
130/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 116 on average
132/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 91 on average
102/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
32/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
29/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which settings and rules apply on Combat Local - Carbon Dev?

You will find no gather rate in the name of Combat Local - Carbon Dev. The group limit is 8 players, the game's default. It plays in survival mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. VAC, Valve's anti-cheat, is switched on.

Player counts

What is the current population on Combat Local - Carbon Dev?

Combat Local - Carbon Dev is not responding at this moment and is offline, last seen 2 days 3 hours ago. The seven-day average is 1 players, with a peak of 1.

How does Combat Local - Carbon Dev rank against other Rust servers?

On player hours for the past week, Combat Local - Carbon Dev sits at #13,089, which puts it inside the top 59% of every ranked server.

Server facts

How reliably does Combat Local - Carbon Dev stay online?

No contact with Combat Local - Carbon Dev right now, and the last recorded contact was 2 days 3 hours ago. It was up 0% of the time across the last 1 full day: 0 of 24 hours. Its earliest appearance in the records of Rust Server Trends dates to 26 October 2026.

Which region does Combat Local - Carbon Dev run from?

A region is not published by Combat Local - Carbon Dev. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 167.17.58.31: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. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

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. 2 days 3 hours is how long the current world has been running.

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): Survival in standard Rust; mp10 (Max players): Slots: 10; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): Game build: 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. Current players, queue length and world creation time sit in the tags as well, and appear 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. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.

Connecting

How do you connect to Combat Local - Carbon Dev?

You can connect by pressing F1 in Rust and typing client.connect 167.17.58.31: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.

Instrument codes

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Survival in standard Rust.
mp10
Max players Slots: 10.
ts8
Group limit Teams max out at 8, the default set by the game.
v2635
Protocol To connect, your game must be on the same protocol, 2635.
cs168909
Build Game build: 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Mods and access

^z
Modded Plugins or settings alter the game, so it's listed under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

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.

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.