RUST METRICSFlight deck · live data
Data live Servers11,680 Players38,014 Populated2,926 Fresh wipes 3 h94 Scan5 min
‹ All servers213.182.203.86:28015
Offline Full Queue Fresh wipe Wipe due No query

Combat Local - Carbon Dev

Offline 213.182.203.86:28015 checked 4d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% full 7-day avg7-day peak
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average1peak 1
Rank#11,541top 52%
Last wipe4d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k24 Oct25 Oct26 Oct27 Oct28 Oct29 Oct

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

PLAN

Wipe schedule

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

When does Combat Local - Carbon Dev wipe?

The rhythm of Combat Local - Carbon Dev's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 4 days 14 hours ago the current world was made.

Lists and filters

How should you read the tags on Combat Local - Carbon Dev?

Tags published by Combat Local - Carbon Dev, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Check: framework. Carbon. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Combat Local - Carbon Dev appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Combat Local - Carbon Dev: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.

Population

What position does Combat Local - Carbon Dev hold among Rust servers?

Player hours over seven days put Combat Local - Carbon Dev at #11,541, in the top 52% of all ranked servers.

What is the population on Combat Local - Carbon Dev?

Status for Combat Local - Carbon Dev: offline. Last seen 4 days 4 hours ago. Check: players over seven days. Average 1, peak 1.

Server details

Which location does Combat Local - Carbon Dev run from?

No region comes from Combat Local - Carbon Dev. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 213.182.203.86:28015.

What Rust version is Combat Local - Carbon Dev on?

Reading: Combat Local - Carbon Dev, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Combat Local - Carbon Dev, and is it online?

Check: connection. Combat Local - Carbon Dev is offline at this moment. Last contact was 4 days 4 hours ago. Uptime for the last 4 full days: 0 of 96 hours, or 0%. Reading: first seen 24 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does Combat Local - Carbon Dev enforce, and what are its settings?

Check: gather rate. The name Combat Local - Carbon Dev does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Carbon plugins are running. Anti-cheat reading: VAC on, Valve's system.

How to join

How can you get onto Combat Local - Carbon Dev?

Check: join. Open Rust, press F1, then enter client.connect 213.182.203.86:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^y
Carbon Check: framework. Carbon.

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.