RUST METRICSFlight deck · live data
Data live Servers11,737 Players52,840 Populated3,354 Fresh wipes 3 h124 Scan5 min
‹ All servers95.25.121.195:28015
Offline Full Queue Fresh wipe Wipe due No query

test

Offline 95.25.121.195:28015 checked 21d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 0 /500

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,366top 65%
Last wipe21d agono schedule published
Next wipe–no rhythm it keeps
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
15k10k15k20k24 Sep28 Sep2 Oct6 Oct10 Oct14 Oct

Top 65% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.1 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Wed 7 OctTue 6 OctMon 5 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 7 Oct, 18:47 UTC21d ago 1 – running 1
Tue 6 Oct, 20:25 UTC22d ago 1 – 0.9 days 1
Mon 5 Oct, 18:32 UTC23d ago 1 – 1.1 days 0
Fri 2 Oct, 16:16 UTC26d ago 1 – 3.1 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?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

How often does test wipe, and when?

There is no next wipe to predict: test wipes at irregular times. 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 it runs now was made 21 days 4 hours ago.

Tags

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

Tags published by test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166586 (Build): Build 166586; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. 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 test?

Rust Metrics lists featuring 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.

Occupancy

What position does test hold among Rust servers?

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

What player count does test carry?

test is not responding; status offline, last seen 21 days 4 hours ago.

Operator and location

Which location does test run from?

No region comes from test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 95.25.121.195:28015.

What Rust version is test on?

Reading: test, Rust network protocol 2634 and build 166586, Windows. Matching protocol is required to join. Let Steam update your game.

How reliable is test, and is it online now?

test reports offline. The last reading came 21 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 24 September 2026.

Settings and map

What settings and rules apply on test?

Reading the name gives no gather rate for test. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Join

How do you connect to test?

To join: start Rust, press F1 and type client.connect 95.25.121.195:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players The server holds 500 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166586
Build Build 166586.
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.