RUST METRICSFlight deck · live data
Data live Servers11,644 Players43,541 Populated3,049 Fresh wipes 3 h97 Scan5 min
‹ All servers106.72.203.130:28015
Offline Full Queue Fresh wipe Wipe due No query

Testserver

Offline 106.72.203.130: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 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,338top 69%
Last wipe1d 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
15k10k15k20k27 Oct28 Oct29 Oct

Top 69% 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 27 Oct, 15:38 UTC1d ago – – 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 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. 40 hours ago the current world was made.

Lists and filters

How should you read the tags on Testserver?

These are the tags Testserver publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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 Testserver?

Rust Metrics lists featuring Testserver: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 3 days.

Player count

Where does Testserver sit in the rankings?

Player hours over seven days put Testserver at #15,338, in the top 69% of all ranked servers.

What player count does Testserver carry?

Testserver is not responding; status offline, last seen 40 hours ago. Seven-day reading: 0 players on average.

Server details

What location is Testserver hosted in?

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 106.72.203.130:28015.

What Rust version is Testserver on?

Rust network protocol 2635 and build 168909 on Linux is the build Testserver runs. To get in, your game needs the same protocol; Steam applies the update.

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

Check: connection. Testserver is offline at this moment. Last contact was 40 hours ago. Reading: 0% uptime over the last 1 full day. It was up 0 of 24 hours. Check: first contact. Rust Metrics logged it on 27 October 2026.

Rules and settings

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

No gather rate appears in the name: Testserver. 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. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is Testserver on?

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

Connection

How do you connect to Testserver?

Check: join. Open Rust, press F1, then enter client.connect 106.72.203.130:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

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

Game

gmvanilla
Game mode Survival on vanilla settings.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.