RUST METRICSFlight deck · live data
Data live Servers11,872 Players96,217 Populated4,094 Fresh wipes 3 h158 Scan5 min
‹ All servers80.0.6.38:28015
Offline Full Queue Fresh wipe Wipe due No query

Carbon Test Server

Offline 80.0.6.38:28015 checked 43d 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 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,034no 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
No rank history yet.
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

Wipe timing

How often does Carbon Test Server wipe, and when?

The rhythm of Carbon Test Server's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 45 days 19 hours ago the current world was made.

Tag meanings

How should you read the tags on Carbon Test Server?

These are the tags Carbon Test Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Carbon Test Server?

Rust Metrics lists featuring Carbon Test Server: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Population

Where does Carbon Test Server sit in the rankings?

Ranking for Carbon Test Server: #13,034 on seven-day player hours, top – of all ranked servers.

How full does Carbon Test Server get?

Carbon Test Server is not responding; status offline, last seen 43 days 23 hours ago.

Server details

Which location does Carbon Test Server run from?

No region comes from Carbon Test Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 80.0.6.38:28015.

What Rust version is Carbon Test Server on?

Reading: Carbon Test Server, Rust network protocol 2633 and build 163794, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is Carbon Test Server up, and how often does it stay up?

Carbon Test Server reports offline. The last reading came 43 days 23 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

How is Carbon Test Server configured, and what rules are in force?

Reading the name gives no gather rate for Carbon Test Server. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. 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. Check: plugins. It runs Carbon of them. VAC is on. That is Valve's anti-cheat.

Which map is live on Carbon Test Server?

The game generates a procedural map for Carbon Test Server.

Join

What do you do to join Carbon Test Server?

Press F1 in Rust and enter client.connect 80.0.6.38:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Game build reading: 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: 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.