RUST METRICSFlight deck · live data
Data live Servers11,747 Players58,097 Populated3,441 Fresh wipes 3 h133 Scan5 min
‹ All servers95.31.40.60:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 95.31.40.60:28015 checked 19d 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#15,848top 72%
Last wipe19d 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
15k10k15k20k8 Oct9 Oct11 Oct12 Oct14 Oct15 Oct

Top 72% 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
Thu 8 Oct, 11:17 UTC19d 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

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.

When does TEST wipe?

The rhythm of TEST's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 19 days 12 hours ago the current world was made.

Lists and filters

How should you read the tags on TEST?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167231 (Build): Build 167231; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from TEST. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does TEST appear in Rust Metrics lists and filters?

These Rust Metrics lists carry 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; Group limit: 5 or more.

Population

What position does TEST hold among Rust servers?

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

What player count does TEST carry?

Status for TEST: offline. Last seen 19 days 9 hours ago.

Operator and location

Which location does TEST run from?

No region comes from TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 95.31.40.60:28015.

What Rust version is TEST on?

Version check: Rust network protocol 2634 and build 167231 on Windows, run by TEST. Check: protocol. To join, your game must match; Steam handles the update.

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

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

Map and rules

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

No gather rate appears in the name: TEST. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on TEST?

Check: map. Procedural, generated by the game, on TEST.

Connection

How do you connect to TEST?

Press F1 in Rust and enter client.connect 95.31.40.60: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,cs167231,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167231
Build Build 167231.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.