RUST METRICSFlight deck · live data
Data live Servers11,632 Players38,377 Populated2,983 Fresh wipes 3 h101 Scan5 min
‹ All servers95.25.134.167:28015
Offline Full Queue Fresh wipe Wipe due No query

my test server

Offline 95.25.134.167:28015 checked 3d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 1 /15

Players now

7% full 7-day avg7-day peak
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 average1peak 1
Rank#10,844top 49%
Last wipe3d 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
15k10k15k20k23 Oct24 Oct25 Oct26 Oct27 Oct28 Oct

Top 49% 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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 24 Oct, 18:07 UTC3d ago 1 – running 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 my test server when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours.

What wipe timing does my test server follow?

To tell the rhythm of my test server, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 3 days 11 hours ago.

Tag meanings

How should you read the tags on my test server?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp15 (Max players): 15 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from my test server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show my test server?

On Rust Metrics, my test server sits in these lists: 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; Last wipe: In the last week.

Player count

Where does my test server sit in the rankings?

Player hours over seven days put my test server at #10,844, in the top 49% of all ranked servers.

What is the population on my test server?

Reading for my test server: offline at this moment; last seen 3 days 10 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server details

Where does my test server sit?

No region tag on my test server. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 95.25.134.167:28015.

What Rust version is my test server on?

Rust network protocol 2635 and build 168909 on Windows is the build my test server runs. Matching protocol is required to join. Let Steam update your game.

Is my test server up, and how often does it stay up?

Check: connection. my test server is offline at this moment. Last contact was 3 days 10 hours ago. Uptime for the last 4 full days: 3 of 96 hours, or 3%. Reading: first seen 23 October 2026, recorded by Rust Metrics.

Map and rules

How is my test server configured, and what rules are in force?

Reading the name gives no gather rate for my test server. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on my test server?

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

Connection

What do you do to join my test server?

Press F1 in Rust and enter client.connect 95.25.134.167: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 mp15,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp15
Max players 15 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.