RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h4 Scan5 min
‹ All servers90.154.73.69:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server

Offline 90.154.73.69:28015 checked 16d 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,682top 71%
Last wipe19d 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
15k10k15k20k30 Sep4 Oct7 Oct11 Oct14 Oct18 Oct

Top 71% 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 gap7.1 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Fri 9 OctFri 2 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 9 Oct, 16:49 UTC19d ago 1 – running 1
Fri 2 Oct, 13:42 UTC26d ago 1 held half 7.1 days 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 happens on Test Server when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 1 hours in. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

What wipe timing does Test Server follow?

To tell the rhythm of Test Server, 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 in play was created 19 days 3 hours ago.

Tags

How should you read the tags on Test Server?

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): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166586 (Build): Build 166586; ptrak (Networking): This is RakNet, Rust's usual network layer; $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.

Where does Test Server appear in Rust Metrics lists and filters?

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

Population

What position does Test Server hold among Rust servers?

Ranking for Test Server: #15,682 on seven-day player hours, top 71% of all ranked servers.

What is the population on Test Server?

Status for Test Server: offline. Last seen 16 days 22 hours ago.

Server

What location is Test Server hosted in?

No region tag on Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 90.154.73.69:28015.

What Rust version is Test Server on?

Reading: Test Server, Rust network protocol 2634 and build 166586, 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 16 days 22 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 30 September 2026, recorded by Rust Metrics.

Map and rules

What rules does Test Server enforce, and what are its settings?

No gather rate appears in the name: Test Server. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. 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 do you connect to Test Server?

Press F1 in Rust and enter client.connect 90.154.73.69:28015. 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?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166586
Build Build 166586.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.