RUST METRICSFlight deck · live data
Data live Servers11,624 Players39,995 Populated3,014 Fresh wipes 3 h93 Scan5 min
‹ All servers138.124.85.71:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 138.124.85.71:28015 checked 22d ago

teams off hardcore
COM 1 · connect

Server instruments

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

Players now

10% 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#14,799top 66%
Last wipe26d 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 Sep29 Sep3 Oct8 Oct12 Oct

Top 66% 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 held100%of its cycles kept half the crowd

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 UTC26d ago 1 – running 0
Fri 18 Sep, 11:08 UTC39d ago 1 held half 13.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?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.

How often does TEST wipe, and when?

To tell the rhythm of TEST, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 26 days 7 hours ago.

Lists and filters

How should you read the tags on TEST?

These are the tags TEST publishes, and the server browser reads them: gmhardcore (Game mode): A harsher set of rules: hardcore; mp10 (Max players): Slots: 10; ts0 (Group limit): Teams are off on this server; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166494 (Build): Game build reading: 166494; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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; Game mode: Hardcore.

Player count

What position does TEST hold among Rust servers?

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

How full does TEST get?

Reading for TEST: offline at this moment; last seen 22 days 13 hours ago.

Server details

Which location does TEST run from?

No region tag on TEST. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 138.124.85.71:28015.

What Rust version is TEST on?

Reading: TEST, Rust network protocol 2634 and build 166494, Windows. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on TEST, and is it online?

TEST reports offline. The last reading came 22 days 13 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.

Rules and settings

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

No gather rate appears in the name: TEST. The group limit is not published. The mode is hardcore. Note the following: Facepunch's most punishing mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is TEST on?

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

Connection

How can you get onto TEST?

Check: join. Open Rust, press F1, then enter client.connect 138.124.85.71:28015. Alternatively, use Launch Rust on this page: Steam opens Rust 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 Teams are off on this server.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166494
Build Game build reading: 166494.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.