RUST METRICSFlight deck · live data
Data live Servers11,899 Players103,131 Populated3,962 Fresh wipes 3 h371 Scan5 min
‹ All servers193.141.60.251:28017
Offline Full Queue Fresh wipe Wipe due No query

Test Rust

Offline 193.141.60.251:28017 checked 27d ago

pve
COM 1 · connect

Server instruments

no direct query in 48 hours
0 5 10 15 20 PAX 1 /20

Players now

5% 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#13,894top 60%
Last wipe27d 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 Sep30 Sep2 Oct4 Oct6 Oct8 Oct

Top 60% 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.

usual gap3.5 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Thu 1 OctMon 28 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 20:56 UTC FW27d ago 1 – running 0
Mon 28 Sep, 09:43 UTC31d ago 0 – 3.5 days 0

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 should you expect from wipe day on Test Rust?

At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 1 hours.

When does Test Rust wipe?

Its rhythm cannot be told from the wipes of Test Rust 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. The world it runs now was made 27 days 21 hours ago.

Tag meanings

How should you read the tags on Test Rust?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^p (PvE): No fighting between players: the world itself is the hazard from Test Rust. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

Rust Metrics lists featuring Test Rust: Rust community servers: live readings and Rust PvE servers. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.

Population

What position does Test Rust hold among Rust servers?

Player hours over seven days put Test Rust at #13,894, in the top 60% of all ranked servers.

How full does Test Rust get?

Status for Test Rust: offline. Last seen 27 days 19 hours ago.

Server details

Where does Test Rust sit?

Reading: location. Test Rust gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 193.141.60.251:28017.

What Rust version is Test Rust on?

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

What is the uptime on Test Rust, and is it online?

Reading: offline. Test Rust last answered 27 days 19 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 28 September 2026.

Settings and map

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

Reading the name gives no gather rate for Test Rust. 8 players per group, the default value. pve, other players are not fought — that is the game mode. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is Test Rust on?

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

Connection

What do you do to join Test Rust?

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

PLACARDS

Server tags

what each one means

Published as mp20,ptrak,$r?,v2633,^p,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp20
Max players The server holds 20 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

Gameplay

^p
PvE No fighting between players: the world itself is the hazard.

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.