RUST METRICSFlight deck · live data
Data live Servers11,709 Players54,841 Populated3,244 Fresh wipes 3 h155 Scan5 min
‹ All servers178.168.123.153:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 178.168.123.153:28015 checked 8d ago

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#13,060top 59%
Last wipe9d 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 Sep25 Sep4 Oct8 Oct22 Oct27 Oct

Top 59% 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 gap17.5 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Tue 20 OctFri 2 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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 20 Oct, 10:07 UTC9d ago 1 – running 1
Fri 2 Oct, 21:39 UTC26d ago 1 – 17.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. 1 hours after the wipe, the crowd peaked on the latest wipe.

How often does TEST wipe, and when?

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 9 days ago.

Tag meanings

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set 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?

On Rust Metrics, TEST sits in these lists: 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; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

What position does TEST hold among Rust servers?

Player hours over seven days put TEST at #13,060, in the top 59% of all ranked servers.

How full does TEST get?

Reading for TEST: offline at this moment; last seen 8 days 21 hours ago.

Operator and location

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 178.168.123.153:28015.

What Rust version is TEST on?

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

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

Reading: offline. TEST last answered 8 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Map and rules

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

No gather rate appears in the name: TEST. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is TEST on?

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

How to join

What do you do to join TEST?

Press F1 in Rust and enter client.connect 178.168.123.153: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?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build Build 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.