RUST METRICSFlight deck · live data
Data live Servers11,880 Players89,250 Populated4,029 Fresh wipes 3 h158 Scan5 min
‹ All servers94.134.192.52:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 94.134.192.52:28015 checked 3d 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 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#14,326top 65%
Last wipe25d 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
15k10k15k20k24 Oct25 Oct26 Oct27 Oct

Top 65% 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

What wipe timing does TestServer follow?

The rhythm of TestServer's wipes cannot be told yet: too few 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 25 days 12 hours ago.

Lists and filters

How should you read the tags on TestServer?

These are the tags TestServer publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show TestServer?

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,326, in the top 65% of all ranked servers.

How full does TestServer get?

Reading for TestServer: offline at this moment; last seen 3 days 12 hours ago. Check: players over seven days. Average 0, peak 1.

Operator and location

Where does TestServer sit?

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

What Rust version is TestServer on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by TestServer. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on TestServer, and is it online?

TestServer reports offline. The last reading came 3 days 12 hours ago. Reading: 0% uptime over the last 2 full days. It was up 0 of 48 hours. Check: first contact. Rust Metrics logged it on 24 October 2026.

Settings and map

What settings and rules apply on TestServer?

Reading the name gives no gather rate for TestServer. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is TestServer on?

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

Connection

What do you do to join TestServer?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players Slots: 5.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is 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.