RUST METRICSFlight deck · live data
Data live Servers11,623 Players45,630 Populated3,138 Fresh wipes 3 h94 Scan5 min
‹ All servers92.208.27.3:28015
Offline Full Queue Fresh wipe Wipe due No query

phx testserver

Offline 92.208.27.3:28015 checked 26d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

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#16,275top 69%
Last wipe27d 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
15k10k15k20k29 Sep1 Oct3 Oct4 Oct6 Oct8 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.

usual gap1 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Wed 30 SepTue 29 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 30 Sep, 14:04 UTC27d ago 1 – running 1
Tue 29 Sep, 15:07 UTC28d ago 1 – 1 days 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

Reset cycle

What happens on phx testserver when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

How often does phx testserver wipe, and when?

To tell the rhythm of phx testserver, 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. The world in play was created 27 days 18 hours ago.

Lists and filters

Which tags does phx testserver carry, and what do they mean?

These are the tags phx testserver publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166452 (Build): Game build reading: 166452; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show phx testserver?

Rust Metrics lists featuring phx testserver: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does phx testserver hold among Rust servers?

Ranking for phx testserver: #16,275 on seven-day player hours, top 69% of all ranked servers.

How full does phx testserver get?

Reading for phx testserver: offline at this moment; last seen 26 days 15 hours ago.

Operator and location

Which location does phx testserver run from?

No region comes from phx testserver. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 92.208.27.3:28015.

What Rust version is phx testserver on?

Rust network protocol 2634 and build 166452 on Windows is the build phx testserver runs. To get in, your game needs the same protocol; Steam applies the update.

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

phx testserver reports offline. The last reading came 26 days 15 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 29 September 2026, recorded by Rust Metrics.

Map and rules

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

Reading the name gives no gather rate for phx testserver. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on phx testserver?

Check: map. Procedural, generated by the game, on phx testserver.

Connection

How do you connect to phx testserver?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs166452,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players 5 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166452
Build Game build reading: 166452.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

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.