RUST METRICSFlight deck · live data
Data live Servers11,633 Players40,937 Populated2,826 Fresh wipes 3 h115 Scan5 min
‹ All servers62.118.106.193:28015
Offline Full Queue Fresh wipe Wipe due No query

Sector 17 - Carbon Test

Offline 62.118.106.193:28015 checked 2d ago

moddedcarbon
COM 1 · connect

Server instruments

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

Players now

0% 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 average0peak 1
Rank#13,006top 58%
Last wipe15d 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
15k10k15k20k27 Oct28 Oct29 Oct30 Oct

Top 58% 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

What wipe timing does Sector 17 - Carbon Test follow?

Its rhythm cannot be told from the wipes of Sector 17 - Carbon Test 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. 15 days 19 hours ago the current world was made.

Tags

Which tags does Sector 17 - Carbon Test carry, and what do they mean?

These are the tags Sector 17 - Carbon Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 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 Sector 17 - Carbon Test appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Sector 17 - Carbon Test: 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 Sector 17 - Carbon Test hold among Rust servers?

Ranking for Sector 17 - Carbon Test: #13,006 on seven-day player hours, top 58% of all ranked servers.

How full does Sector 17 - Carbon Test get?

Reading for Sector 17 - Carbon Test: offline at this moment; last seen 2 days 13 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Operator and location

Which location does Sector 17 - Carbon Test run from?

Reading: location. Sector 17 - Carbon Test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 62.118.106.193:28015.

What Rust version is Sector 17 - Carbon Test on?

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

What is the uptime on Sector 17 - Carbon Test, and is it online?

Check: connection. Sector 17 - Carbon Test is offline at this moment. Last contact was 2 days 13 hours ago. Uptime for the last 2 full days: 0 of 48 hours, or 0%. Check: first contact. Rust Metrics logged it on 27 October 2026.

Rules and settings

What rules does Sector 17 - Carbon Test enforce, and what are its settings?

No gather rate appears in the name: Sector 17 - Carbon Test. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Carbon of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is Sector 17 - Carbon Test on?

The game generates a procedural map for Sector 17 - Carbon Test.

Connection

How do you connect to Sector 17 - Carbon Test?

Press F1 in Rust and enter client.connect 62.118.106.193: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 mp5,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players 5 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 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.