RUST METRICSFlight deck · live data
Data live Servers11,644 Players37,516 Populated2,896 Fresh wipes 3 h65 Scan5 min
‹ All servers94.134.192.252:28015
Offline Full Queue Fresh wipe Wipe due No query

TestServer

Offline 94.134.192.252:28015 checked 28d 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,529top 61%
Last wipe53d 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
15k10k15k20k29 Sep30 Sep2 Oct3 Oct5 Oct6 Oct

Top 61% 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?

To tell the rhythm of TestServer, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 53 days 13 hours ago the current world was made.

Tag meanings

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): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does TestServer appear in Rust Metrics lists and filters?

Rust Metrics lists featuring TestServer: 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 TestServer hold among Rust servers?

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

What player count does TestServer carry?

Reading for TestServer: offline at this moment; last seen 28 days 13 hours ago.

Server details

Which location does TestServer run from?

Reading: location. TestServer gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 94.134.192.252:28015.

What Rust version is TestServer on?

Version check: Rust network protocol 2633 and build 165217 on Windows, run by TestServer. To get in, your game needs the same protocol; Steam applies the update.

How reliable is TestServer, and is it online now?

Reading: offline. TestServer last answered 28 days 13 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 29 September 2026.

Map and rules

How is TestServer configured, and what rules are in force?

Check: gather rate. The name TestServer does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is TestServer on?

The game generates a procedural map for TestServer.

Connection

How do you connect to TestServer?

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

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 Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.