RUST METRICSFlight deck · live data
Data live Servers11,614 Players33,332 Populated2,810 Fresh wipes 3 h68 Scan5 min
‹ All servers78.189.164.73:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server

Offline 78.189.164.73:28015 checked 41d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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#14,380no region published
Last wipe41d agono schedule published
Next wipe–no wipe 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 Sep21 Sep22 Sep23 Sep24 Sep
PLAN

Wipe schedule

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
No wipe seen yet.

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 Test Server follow?

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. 41 days 15 hours ago the current world was made.

Tag meanings

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

These are the tags Test Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): Game build reading: 164530; 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 Test Server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Test Server: 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 Test Server hold among Rust servers?

Ranking for Test Server: #14,380 on seven-day player hours, top – of all ranked servers.

What player count does Test Server carry?

Test Server is not responding; status offline, last seen 41 days 12 hours ago.

Operator and location

What location is Test Server hosted in?

No region comes from Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 78.189.164.73:28015.

What Rust version is Test Server on?

Version check: Rust network protocol 2633 and build 164530 on Windows, run by Test Server. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is Test Server, and is it online now?

Test Server reports offline. The last reading came 41 days 12 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 17 September 2026.

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; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is Test Server on?

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

Connection

How can you get onto Test Server?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build Game build reading: 164530.
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.