RUST METRICSFlight deck · live data
Data live Servers11,753 Players57,310 Populated3,407 Fresh wipes 3 h132 Scan5 min
‹ All servers177.89.208.52:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server

Offline 177.89.208.52:28015 checked 4d 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 avg7-day peak
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 1
Rank#13,900top 63%
Last wipe5d 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 Oct22 Oct23 Oct25 Oct26 Oct28 Oct

Top 63% 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 peak1players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 23 Oct, 22:04 UTC5d ago 1 – 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

Reset cycle

What happens on Test Server when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 18 hours.

How often does Test Server wipe, and when?

Its rhythm cannot be told from the wipes of Test Server on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 5 days ago the current world was made.

Lists and filters

Which tags does Test Server carry, and what do they mean?

Tags published by Test Server, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Test Server?

On Rust Metrics, Test Server sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.

Population

What position does Test Server hold among Rust servers?

Player hours over seven days put Test Server at #13,900, in the top 63% of all ranked servers.

What is the population on Test Server?

Status for Test Server: offline. Last seen 4 days 6 hours ago. Check: players over seven days. Average 0, peak 1.

Operator and location

Where does Test Server sit?

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

What Rust version is Test Server on?

Reading: Test Server, Rust network protocol 2635 and build 168909, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is Test Server up, and how often does it stay up?

Check: connection. Test Server is offline at this moment. Last contact was 4 days 6 hours ago. Reading: 2% uptime over the last 7 full days. It was up 3 of 168 hours. Check: first contact. Rust Metrics logged it on 20 October 2026.

Rules and settings

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: standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Test Server?

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

How to join

How can you get onto Test Server?

Check: join. Open Rust, press F1, then enter client.connect 177.89.208.52: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,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.