RUST METRICSFlight deck · live data
Data live Servers11,786 Players66,925 Populated3,511 Fresh wipes 3 h190 Scan5 min
‹ All servers87.167.183.73:28015
Offline Full Queue Fresh wipe Wipe due No query

Testserver

Offline 87.167.183.73:28015 checked 22d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 0 /2

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,966top 72%
Last wipe26d 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
15k10k15k20k20 Sep1 Oct4 Oct8 Oct11 Oct14 Oct

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

wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 31 hours in, with 1 in the queue.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 14:50 UTC26d ago 2+1 queue – running 1

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 should you expect from wipe day on Testserver?

The busiest point of its recent wipes drew 2 players on average. With 1 more waiting in the queue, the crowd peaked 31 hours after the wipe on the latest wipe.

What wipe timing does Testserver follow?

To tell the rhythm of Testserver, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 26 days 21 hours ago.

Lists and filters

How should you read the tags on Testserver?

Tags published by Testserver, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): 2 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): The server runs game build 166586; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. 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?

These Rust Metrics lists carry 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.

Population

What position does Testserver hold among Rust servers?

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

How full does Testserver get?

Reading for Testserver: offline at this moment; last seen 22 days 4 hours ago.

Server details

What location is Testserver hosted in?

Reading: location. Testserver gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 87.167.183.73:28015.

What Rust version is Testserver on?

Version check: Rust network protocol 2634 and build 166586 on Windows, run by Testserver. Matching protocol is required to join. Let Steam update your game.

How reliable is Testserver, and is it online now?

Testserver reports offline. The last reading came 22 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 15 September 2026.

Settings and map

What settings and rules apply on Testserver?

No gather rate appears in the name: Testserver. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is Testserver on?

Check: map. Procedural, generated by the game, on Testserver.

Connection

How do you connect to Testserver?

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

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players 2 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166586
Build The server runs game build 166586.
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.