RUST METRICSFlight deck · live data
Data live Servers11,810 Players75,437 Populated3,743 Fresh wipes 3 h107 Scan5 min
‹ All servers5.241.136.251:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server

Offline 5.241.136.251:28015 checked 30d ago

COM 1 · connect

Server instruments

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

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#16,965top 71%
Last wipe30d 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
15k10k15k20k28 Sep29 Sep1 Oct2 Oct4 Oct5 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.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 28 Sep, 13:02 UTC30d ago 0 – running 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

Wipe schedule

What happens on Test Server when wipe day comes?

An average of 0 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does Test Server follow?

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

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): The game mode is plain Rust survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Default limit in force: 8 per team; 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): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

Rust Metrics lists featuring 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.

Player count

Where does Test Server sit in the rankings?

Player hours over seven days put Test Server at #16,965, in the top 71% of all ranked servers.

What player count does Test Server carry?

Test Server is not responding; status offline, last seen 30 days 5 hours ago.

Operator and location

Where does Test Server sit?

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

What Rust version is Test Server on?

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

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

Reading: offline. Test Server last answered 30 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 27 September 2026, recorded by Rust Metrics.

Settings and map

How is Test Server configured, and what rules are in force?

No gather rate appears in the name: Test Server. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is Test Server on?

Check: map. Procedural, generated by the game, on Test Server.

Join

What do you do to join Test Server?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players The server holds 1 slots.
ts8
Group limit Default limit in force: 8 per team.
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 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.