RUST METRICSFlight deck · live data
Data live Servers11,598 Players34,072 Populated2,891 Fresh wipes 3 h69 Scan5 min
‹ All servers84.147.150.45:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 84.147.150.45:28015 checked 27d ago

COM 1 · connect

Server instruments

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

Players now

20% 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,412top 60%
Last wipe30d 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
15k10k15k20k30 Sep1 Oct3 Oct4 Oct6 Oct7 Oct

Top 60% of all ranked servers. Ranked on player hours over the last seven days.

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

When does TestServer wipe?

The rhythm of TestServer's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 30 days 15 hours ago.

Tags

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; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does TestServer appear in Rust Metrics lists and filters?

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

Player count

What position does TestServer hold among Rust servers?

Player hours over seven days put TestServer at #14,412, in the top 60% of all ranked servers.

What is the population on TestServer?

TestServer is not responding; status offline, last seen 27 days 16 hours ago.

Server

Where does TestServer sit?

Reading: location. TestServer gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 84.147.150.45:28015.

What Rust version is TestServer on?

Reading: TestServer, Rust network protocol 2633 and build 165217, Windows. Matching protocol is required to join. Let Steam update your game.

Is TestServer up, and how often does it stay up?

Reading: offline. TestServer last answered 27 days 16 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.

Settings and map

What rules does TestServer enforce, and what are its settings?

Check: gather rate. The name TestServer does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. 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 TestServer on?

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

Join

How can you get onto TestServer?

Press F1 in Rust and enter client.connect 84.147.150.45: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 mp5,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players The server holds 5 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build The server runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.