RUST METRICSFlight deck · live data
Data live Servers11,898 Players103,740 Populated4,020 Fresh wipes 3 h406 Scan5 min
‹ All servers31.54.137.255:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server

Offline 31.54.137.255:28015 checked 12d ago

moddedcarbon
COM 1 · connect

Server instruments

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

Players now

10% 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#14,607top 67%
Last wipe12d 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
15k10k15k20k17 Oct18 Oct20 Oct21 Oct23 Oct24 Oct

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

How often does Test Server wipe, and when?

To tell the rhythm of Test Server, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 12 days 6 hours ago the current world was made.

Lists and filters

How should you read the tags on Test Server?

These are the tags Test Server publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Carbon handles the plugins here. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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

Rust Metrics lists featuring Test Server: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

Where does Test Server sit in the rankings?

Player hours over seven days put Test Server at #14,607, in the top 67% of all ranked servers.

How full does Test Server get?

Status for Test Server: offline. Last seen 12 days 4 hours ago.

Operator and location

Where does Test Server sit?

No region tag on Test Server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 31.54.137.255: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.

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

Test Server reports offline. The last reading came 12 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 17 October 2026.

Settings and map

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

Check: gather rate. The name Test Server does not state one. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Carbon plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is Test Server on?

Procedural map on Test Server, made by the game's generator.

Connection

How can you get onto Test Server?

Press F1 in Rust and enter client.connect 31.54.137.255: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 mp10,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players 10 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Carbon handles the plugins here.

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.