RUST METRICSFlight deck · live data
Data live Servers11,691 Players35,842 Populated2,916 Fresh wipes 3 h97 Scan5 min
‹ All servers115.186.228.97:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Test Server [Carbon]

Offline 115.186.228.97:28015 checked 1d ago

COM 1 · connect

Server instruments

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

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#6,355top 29%
Last wipe3d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

AveragePeak
0123405:0012:0014:0016:0018:0020:00

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 Sep24 Sep28 Sep2 Oct25 Oct29 Oct

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

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 25 Oct, 13:40 UTC3d 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 timing

What should you expect from wipe day on Local Test Server [Carbon]?

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

How often does Local Test Server [Carbon] wipe, and when?

The rhythm of Local Test Server [Carbon]'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. 3 days 13 hours ago the current world was made.

Tags

How should you read the tags on Local Test Server [Carbon]?

Tags published by Local Test Server [Carbon], 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): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Local Test Server [Carbon] appear in Rust Metrics lists and filters?

On Rust Metrics, Local Test Server [Carbon] sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Population

Where does Local Test Server [Carbon] sit in the rankings?

Ranking for Local Test Server [Carbon]: #6,355 on seven-day player hours, top 29% of all ranked servers.

How full does Local Test Server [Carbon] get?

Status for Local Test Server [Carbon]: offline. Last seen 30 hours ago. Check: players over seven days. Average 0, peak 1.

Server

Where does Local Test Server [Carbon] sit?

No region comes from Local Test Server [Carbon]. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 115.186.228.97:28015.

What Rust version is Local Test Server [Carbon] on?

Rust network protocol 2635 and build 168909 on Windows is the build Local Test Server [Carbon] runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Local Test Server [Carbon], and is it online?

Local Test Server [Carbon] reports offline. The last reading came 30 hours ago. Uptime for the last 7 full days: 48 of 168 hours, or 29%. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Map and rules

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

Reading the name gives no gather rate for Local Test Server [Carbon]. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on Local Test Server [Carbon]?

The game generates a procedural map for Local Test Server [Carbon].

Connection

What do you do to join Local Test Server [Carbon]?

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

PLACARDS

Server tags

what each one means

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

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 Your game must run protocol 2635 to get in.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.