RUST METRICSFlight deck · live data
Data live Servers11,718 Players59,183 Populated3,355 Fresh wipes 3 h176 Scan5 min
‹ All servers176.234.24.167:28015
Offline Full Queue Fresh wipe Wipe due No query

test

Offline 176.234.24.167:28015 checked 14d 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 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,495top 67%
Last wipe14d 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
15k10k15k20k14 Oct15 Oct17 Oct18 Oct20 Oct21 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.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

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
Wed 14 Oct, 14:02 UTC14d 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

Wipe timing

What happens on test when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

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. The world in play was created 14 days 20 hours ago.

Tag meanings

How should you read the tags on test?

These are the tags test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; 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): The server runs game build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $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.

Occupancy

What position does test hold among Rust servers?

Player hours over seven days put test at #14,495, in the top 67% of all ranked servers.

What is the population on test?

test is not responding; status offline, last seen 14 days 18 hours ago.

Operator and location

Where does test sit?

Reading: location. test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 176.234.24.167:28015.

What Rust version is test on?

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

How reliable is test, and is it online now?

test reports offline. The last reading came 14 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 14 October 2026.

Settings and map

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

No gather rate appears in the name: test. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.

What map is test on?

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

Connection

How do you connect to test?

Check: join. Open Rust, press F1, then enter client.connect 176.234.24.167: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,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
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 The server runs game build 167781.
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.