RUST METRICSFlight deck · live data
Data live Servers11,894 Players99,159 Populated3,939 Fresh wipes 3 h396 Scan5 min
‹ All servers5.106.230.17:28505
Offline Full Queue Fresh wipe Wipe due No query

My Carbon Test Server

Offline 5.106.230.17:28505 checked 18d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

Players now

0% 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#15,790top 71%
Last wipe18d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k10 Oct12 Oct13 Oct15 Oct16 Oct18 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 17 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 10 Oct, 18:03 UTC18d ago 1 – running 0

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 schedule

What should you expect from wipe day on My Carbon Test Server?

An average of 1 players came at the busiest on its recent wipes. 17 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does My Carbon Test Server follow?

Its rhythm cannot be told from the wipes of My Carbon Test Server on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 18 days 23 hours ago the current world was made.

Tag meanings

How should you read the tags on My Carbon Test Server?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Build 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from My Carbon Test Server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does My Carbon Test Server appear in Rust Metrics lists and filters?

Rust Metrics lists featuring My Carbon Test Server: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does My Carbon Test Server sit in the rankings?

Player hours over seven days put My Carbon Test Server at #15,790, in the top 71% of all ranked servers.

How full does My Carbon Test Server get?

Status for My Carbon Test Server: offline. Last seen 18 days 3 hours ago.

Operator and location

Which location does My Carbon Test Server run from?

No region tag on My Carbon Test Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 5.106.230.17:28505.

What Rust version is My Carbon Test Server on?

Reading: My Carbon Test Server, Rust network protocol 2634 and build 167398, Windows. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on My Carbon Test Server, and is it online?

My Carbon Test Server reports offline. The last reading came 18 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 10 October 2026.

Rules and settings

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

Check: gather rate. The name My Carbon Test Server does not state one. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC off, Valve's system.

Which map is live on My Carbon Test Server?

The game generates a procedural map for My Carbon Test Server.

How to join

How can you get onto My Carbon Test Server?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build Build 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

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.