RUST METRICSFlight deck · live data
Data live Servers11,881 Players95,949 Populated4,100 Fresh wipes 3 h162 Scan5 min
‹ All servers60.142.115.227:28015
Offline Full Queue Fresh wipe Wipe due No query

Carbon Local Dev

Offline 60.142.115.227:28015 checked 41d ago

moddedcarbon
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 1 /5

Players now

20% full 7-day avg
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 average0peak –
Rank#13,927no region published
Last wipe45d 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep
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

What wipe timing does Carbon Local Dev follow?

Its rhythm cannot be told from the wipes of Carbon Local Dev on record: there are too few. 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 45 days 20 hours ago.

Tag meanings

How should you read the tags on Carbon Local Dev?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon from Carbon Local Dev. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Carbon Local Dev?

On Rust Metrics, Carbon Local Dev sits in these lists: 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.

Player count

What position does Carbon Local Dev hold among Rust servers?

Ranking for Carbon Local Dev: #13,927 on seven-day player hours, top – of all ranked servers.

What is the population on Carbon Local Dev?

Status for Carbon Local Dev: offline. Last seen 41 days 12 hours ago.

Server

Which location does Carbon Local Dev run from?

No region tag on Carbon Local Dev. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 60.142.115.227:28015.

What Rust version is Carbon Local Dev on?

Rust network protocol 2633 and build 163794 on Windows is the build Carbon Local Dev runs. Check: protocol. To join, your game must match; Steam handles the update.

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

Reading: offline. Carbon Local Dev last answered 41 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

What settings and rules apply on Carbon Local Dev?

Reading the name gives no gather rate for Carbon Local Dev. 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. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Carbon. VAC is on. That is Valve's anti-cheat.

Which map is live on Carbon Local Dev?

Check: map. Procedural, generated by the game, on Carbon Local Dev.

How to join

How can you get onto Carbon Local Dev?

To join: start Rust, press F1 and type client.connect 60.142.115.227:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2633,gmrust,cs163794,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players The server holds 5 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build The server runs game build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^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.