RUST METRICSFlight deck · live data
Data live Servers11,650 Players32,278 Populated2,796 Fresh wipes 3 h79 Scan5 min
‹ All servers176.88.76.123:28015
Offline Full Queue Fresh wipe Wipe due No query

[LOCAL TEST]

Offline 176.88.76.123:28015 checked 39d ago

trio moddedcarbon
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,391no region published
Last wipe43d 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
15k10k15k20k20 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 15 Sep, 20:19 UTC43d 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 happens on [LOCAL TEST] when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 1 hours in.

How often does [LOCAL TEST] wipe, and when?

The rhythm of [LOCAL TEST]'s wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 43 days 7 hours ago the current world was made.

Tags

How should you read the tags on [LOCAL TEST]?

These are the tags [LOCAL TEST] publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts3 (Group limit): Teams are capped at 3; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Check: framework. 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 [LOCAL TEST]?

Rust Metrics lists featuring [LOCAL TEST]: Modded Rust servers, checked live and Trio servers, group limit 3. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: Trio.

Population

Where does [LOCAL TEST] sit in the rankings?

Player hours over seven days put [LOCAL TEST] at #15,391, in the top – of all ranked servers.

How full does [LOCAL TEST] get?

Status for [LOCAL TEST]: offline. Last seen 39 days 9 hours ago.

Server details

What location is [LOCAL TEST] hosted in?

No region tag on [LOCAL TEST]. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 176.88.76.123:28015.

What Rust version is [LOCAL TEST] on?

Reading: [LOCAL TEST], Rust network protocol 2633 and build 163794, Windows. Matching protocol is required to join. Let Steam update your game.

Is [LOCAL TEST] up, and how often does it stay up?

[LOCAL TEST] reports offline. The last reading came 39 days 9 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.

Map and rules

What rules does [LOCAL TEST] enforce, and what are its settings?

No gather rate appears in the name: [LOCAL TEST]. Groups stop at 3 players. The label given is trio. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. Anti-cheat reading: VAC off, Valve's system.

Which map is live on [LOCAL TEST]?

Check: map. Procedural, generated by the game, on [LOCAL TEST].

Join

What do you do to join [LOCAL TEST]?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs163794,ts3,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts3
Group limit Teams are capped at 3.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build Game build reading: 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the 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.