RUST METRICSFlight deck · live data
Data live Servers11,662 Players43,563 Populated3,033 Fresh wipes 3 h101 Scan5 min
‹ All servers98.97.9.217:28015
Offline Full Queue Fresh wipe Wipe due No query

<SERVER_NAME>

Offline 98.97.9.217:28015 checked 7d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /?

Players now

no slots published 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,340top 69%
Last wipe26d agono schedule published
Next wipe–no wipe 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
15k10k15k20k19 Oct21 Oct22 Oct24 Oct25 Oct27 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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

When does <SERVER_NAME> wipe?

To tell the rhythm of <SERVER_NAME>, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 26 days 2 hours ago the current world was made.

Tags

How should you read the tags on <SERVER_NAME>?

These are the tags <SERVER_NAME> publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp0 (Max players): Slots: 0; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show <SERVER_NAME>?

On Rust Metrics, <SERVER_NAME> sits in these lists: 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.

Player count

What position does <SERVER_NAME> hold among Rust servers?

Player hours over seven days put <SERVER_NAME> at #15,340, in the top 69% of all ranked servers.

How full does <SERVER_NAME> get?

<SERVER_NAME> is not responding; status offline, last seen 7 days 22 hours ago.

Server

What location is <SERVER_NAME> hosted in?

No region comes from <SERVER_NAME>. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 98.97.9.217:28015.

What Rust version is <SERVER_NAME> on?

Reading: <SERVER_NAME>, Rust network protocol 2634 and build 167781, Linux. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on <SERVER_NAME>, and is it online?

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

Settings and map

How is <SERVER_NAME> configured, and what rules are in force?

Reading the name gives no gather rate for <SERVER_NAME>. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is <SERVER_NAME> on?

Check: map. Procedural, generated by the game, on <SERVER_NAME>.

Connection

How do you connect to <SERVER_NAME>?

Press F1 in Rust and enter client.connect 98.97.9.217: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 mp0,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp0
Max players Slots: 0.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.