RUST METRICSFlight deck · live data
Data live Servers11,815 Players73,779 Populated3,763 Fresh wipes 3 h143 Scan5 min
‹ All servers209.97.185.252:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST SERVER

Offline 209.97.185.252:28015 checked 19d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 2 /4

Players now

50% 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#12,118top 55%
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 55% 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 peak2players, last three wipes

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 20:40 UTC19d ago 2 – 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 SERVER?

An average of 2 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does TEST SERVER follow?

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

Tags

How should you read the tags on TEST SERVER?

Tags published by TEST SERVER, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): Slots: 4; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167231 (Build): Build 167231; 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 SERVER appear in Rust Metrics lists and filters?

These Rust Metrics lists carry TEST SERVER: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

What position does TEST SERVER hold among Rust servers?

Ranking for TEST SERVER: #12,118 on seven-day player hours, top 55% of all ranked servers.

How full does TEST SERVER get?

Reading for TEST SERVER: offline at this moment; last seen 19 days ago.

Server

Where does TEST SERVER sit?

No region comes from TEST SERVER. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 209.97.185.252:28015.

What Rust version is TEST SERVER on?

Version check: Rust network protocol 2634 and build 167231 on Linux, run by TEST SERVER. Matching protocol is required to join. Let Steam update your game.

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

TEST SERVER reports offline. The last reading came 19 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 8 October 2026.

Settings and map

What settings and rules apply on TEST SERVER?

Reading the name gives no gather rate for TEST SERVER. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.

Which map is live on TEST SERVER?

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

Join

How do you connect to TEST SERVER?

Check: join. Open Rust, press F1, then enter client.connect 209.97.185.252:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp4,ptrak,$r?,v2634,gmrust,cs167231,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp4
Max players Slots: 4.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167231
Build Build 167231.
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.