RUST METRICSFlight deck · live data
Data live Servers11,669 Players34,137 Populated2,836 Fresh wipes 3 h86 Scan5 min
‹ All servers42.112.71.216:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST SERVER

Offline 42.112.71.216:28015 checked 8d ago

moddedcarbon
COM 1 · connect
Launch Rust and join

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,388top 70%
Last wipe9d 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
15k10k15k20k19 Oct21 Oct22 Oct24 Oct25 Oct27 Oct

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

Wipe schedule

What wipe timing does TEST SERVER follow?

The rhythm of TEST SERVER'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. The world it runs now was made 9 days 10 hours ago.

Lists and filters

How should you read the tags on TEST SERVER?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon from TEST SERVER. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show TEST SERVER?

Rust Metrics lists featuring 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; Last wipe: In the last 2 weeks.

Occupancy

What position does TEST SERVER hold among Rust servers?

Ranking for TEST SERVER: #15,388 on seven-day player hours, top 70% of all ranked servers.

How full does TEST SERVER get?

Status for TEST SERVER: offline. Last seen 8 days 7 hours ago.

Server

Where does TEST SERVER sit?

No region tag on TEST SERVER. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 42.112.71.216:28015.

What Rust version is TEST SERVER on?

Reading: TEST SERVER, Rust network protocol 2634 and build 167781, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is TEST SERVER up, and how often does it stay up?

Check: connection. TEST SERVER is offline at this moment. Last contact was 8 days 7 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 October 2026, recorded by Rust Metrics.

Rules and settings

What settings and rules apply on TEST SERVER?

No gather rate appears in the name: TEST SERVER. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Carbon. Anti-cheat reading: VAC on, Valve's system.

Which map is live on TEST SERVER?

Procedural map on TEST SERVER, made by the game's generator.

Connection

What do you do to join TEST SERVER?

To join: start Rust, press F1 and type client.connect 42.112.71.216: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?,v2634,gmrust,cs167781,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players The server holds 50 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock 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.