RUST METRICSFlight deck · live data
Data live Servers11,753 Players57,310 Populated3,407 Fresh wipes 3 h132 Scan5 min
‹ All servers87.192.107.253:28015
Offline Full Queue Fresh wipe Wipe due No query

Test

Offline 87.192.107.253:28015 checked 3d ago

COM 1 · connect
Launch Rust and join

Server instruments

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

Players now

100% 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,336top 65%
Last wipe3d 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
15k10k15k20k25 Oct26 Oct27 Oct28 Oct

Top 65% 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 peak1players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 25 Oct, 15:07 UTC3d ago 1 – running 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

Reset cycle

What happens on Test when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does Test follow?

Its rhythm cannot be told from the wipes of Test on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 3 days 7 hours ago the current world was made.

Tags

How should you read the tags on Test?

These are the tags Test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs169082 (Build): The server runs game build 169082; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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.

Where does Test appear in Rust Metrics lists and filters?

These Rust Metrics lists carry Test: 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; Last wipe: In the last week.

Player count

What position does Test hold among Rust servers?

Ranking for Test: #14,336 on seven-day player hours, top 65% of all ranked servers.

How full does Test get?

Reading for Test: offline at this moment; last seen 3 days 7 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Server

What location is Test hosted in?

No region comes from Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 87.192.107.253:28015.

What Rust version is Test on?

Rust network protocol 2635 and build 169082 on Windows is the build Test runs. To get in, your game needs the same protocol; Steam applies the update.

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

Test reports offline. The last reading came 3 days 7 hours ago. Uptime for the last 2 full days: 0 of 48 hours, or 0%. Check: first contact. Rust Metrics logged it on 25 October 2026.

Map and rules

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

Reading the name gives no gather rate for Test. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. 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 on?

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

Connection

How do you connect to Test?

To join: start Rust, press F1 and type client.connect 87.192.107.253: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?,v2635,gmrust,cs169082,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players Slots: 1.
ts8
Group limit Team cap of 8, which is the game default.
v2635
Protocol Your game must run protocol 2635 to get in.
cs169082
Build The server runs game build 169082.
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.