RUST METRICSFlight deck · live data
Data live Servers11,615 Players36,116 Populated2,895 Fresh wipes 3 h67 Scan5 min
‹ All servers185.54.238.72:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 185.54.238.72:28015 checked 4d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

Players now

0% 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,178top 64%
Last wipe4d 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
15k10k15k20k20 Sep24 Sep16 Oct21 Oct25 Oct29 Oct

Top 64% 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 gap8 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 6

The first 48 hours of its last wipes

Sat 24 OctFri 16 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 24 Oct, 22:07 UTC4d ago 1 – running 0
Fri 16 Oct, 22:11 UTC12d ago 1 halved by day 6 8 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

Reset cycle

What should you expect from wipe day on TEST?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in. Above half that peak the crowd stayed until the next wipe in 0% of recent wipes. It fell below half by day 6 when it didn't.

What wipe timing does TEST follow?

To tell the rhythm of TEST, too few of its wipes 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 4 days 8 hours ago.

Tag meanings

Which tags does TEST carry, and what do they mean?

Tags published by TEST, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show TEST?

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

Occupancy

What position does TEST hold among Rust servers?

Player hours over seven days put TEST at #14,178, in the top 64% of all ranked servers.

What player count does TEST carry?

TEST is not responding; status offline, last seen 4 days 8 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Server details

Which location does TEST run from?

No region tag on TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 185.54.238.72:28015.

What Rust version is TEST on?

Rust network protocol 2635 and build 168909 on Windows is the build TEST runs. Check: protocol. To join, your game must match; Steam handles the update.

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

Check: connection. TEST is offline at this moment. Last contact was 4 days 8 hours ago. Reading: 2% uptime over the last 7 full days. It was up 4 of 168 hours. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on TEST?

Reading the name gives no gather rate for TEST. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on TEST?

The game generates a procedural map for TEST.

Join

How can you get onto TEST?

Press F1 in Rust and enter client.connect 185.54.238.72:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build The server runs game build 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.