RUST METRICSFlight deck · live data
Data live Servers11,692 Players54,249 Populated3,144 Fresh wipes 3 h123 Scan5 min
‹ All servers109.252.54.224:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 109.252.54.224:28015 checked 28d ago

teams off hardcore
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 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#15,343top 67%
Last wipe28d 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 Sep28 Sep1 Oct5 Oct9 Oct

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

The first 48 hours of its last wipes

Fri 2 OctFri 18 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 00:01 UTC28d ago 1 – running 0
Fri 18 Sep, 11:08 UTC41d ago 1 halved by day 6 13.5 days 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

Reset cycle

What happens on TEST when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. It fell below half by day 6 when it didn't.

When does TEST wipe?

The rhythm of TEST'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 in play was created 28 days 1 hours ago.

Tags

How should you read the tags on TEST?

Check: tags. The game's server browser reads gmhardcore (Game mode): A harsher set of rules: hardcore; mp10 (Max players): Slots: 10; ts0 (Group limit): No teams here: the setting is switched off; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166494 (Build): The server runs game build 166494; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from TEST. 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?

Rust Metrics lists featuring TEST: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: Hardcore.

Occupancy

What position does TEST hold among Rust servers?

Ranking for TEST: #15,343 on seven-day player hours, top 67% of all ranked servers.

What player count does TEST carry?

Status for TEST: offline. Last seen 28 days ago.

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. Check: address. It reads 109.252.54.224:28015.

What Rust version is TEST on?

Rust network protocol 2634 and build 166494 on Windows is the build TEST runs. Matching protocol is required to join. Let Steam update your game.

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

TEST reports offline. The last reading came 28 days ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Map and rules

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

No gather rate appears in the name: TEST. Check: group limit. None published. The mode is hardcore. Note the following: Facepunch's most punishing mode. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is TEST on?

Procedural map on TEST, made by the game's generator.

Join

What do you do to join TEST?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmhardcore,cs166494,ts0

Game

gmhardcore
Game mode A harsher set of rules: hardcore.
mp10
Max players Slots: 10.
ts0
Group limit No teams here: the setting is switched off.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166494
Build The server runs game build 166494.
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.