RUST METRICSFlight deck · live data
Data live Servers11,782 Players67,928 Populated3,558 Fresh wipes 3 h196 Scan5 min
‹ All servers162.19.204.31:25588
Offline Full Queue Fresh wipe Wipe due No query

testserver

Offline 162.19.204.31:25588 checked 37d ago

moddedcarbon
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 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,482top 67%
Last wipe37d 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
15k10k15k20k21 Sep22 Sep24 Sep25 Sep27 Sep28 Sep

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

What wipe timing does testserver follow?

Its rhythm cannot be told from the wipes of testserver on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 37 days 18 hours ago the current world was made.

Tag meanings

How should you read the tags on testserver?

Tags published by testserver, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; ts6 (Group limit): Team cap: 6; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Game build reading: 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^z (Modded): Check: category. Modded, because plugins or settings alter the game; ^y (Carbon): Plugin framework in use: Carbon. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does testserver appear in Rust Metrics lists and filters?

On Rust Metrics, testserver sits in these lists: 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.

Population

Where does testserver sit in the rankings?

Ranking for testserver: #15,482 on seven-day player hours, top 67% of all ranked servers.

What is the population on testserver?

Status for testserver: offline. Last seen 37 days 18 hours ago.

Operator and location

Which location does testserver run from?

No region comes from testserver. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 162.19.204.31:25588.

What Rust version is testserver on?

Reading: testserver, Rust network protocol 2633 and build 164530, Linux. Check: protocol. To join, your game must match; Steam handles the update.

Is testserver up, and how often does it stay up?

Check: connection. testserver is offline at this moment. Last contact was 37 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 21 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does testserver enforce, and what are its settings?

No gather rate appears in the name: testserver. Group size, maximum: 6 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Carbon of them. Anti-cheat reading: VAC on, Valve's system.

What map is testserver on?

Size 2,500 and seed 1: the game generates the procedural map on testserver from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Join

What do you do to join testserver?

Press F1 in Rust and enter client.connect 162.19.204.31:25588. 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?,v2633,gmrust,cs164530,ts6,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players 10 slots in total.
ts6
Group limit Team cap: 6.
v2633
Protocol Protocol 2633: join only on the same game version.
cs164530
Build Game build reading: 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Check: category. Modded, because plugins or settings alter the game.
^y
Carbon Plugin framework in use: 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.