RUST METRICSFlight deck · live data
Data live Servers11,722 Players55,260 Populated3,387 Fresh wipes 3 h136 Scan5 min
‹ All servers98.97.13.208:28015
Offline Full Queue Fresh wipe Wipe due No query

<SERVER_NAME>

Offline 98.97.13.208:28015 checked 5d 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,409top 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
15k10k15k20k21 Oct22 Oct23 Oct25 Oct26 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 schedule

What wipe timing does <SERVER_NAME> follow?

Its rhythm cannot be told from the wipes of <SERVER_NAME> on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 26 days ago the current world was made.

Lists and filters

How should you read the tags on <SERVER_NAME>?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp0 (Max players): 0 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167781 (Build): The server runs game build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from <SERVER_NAME>. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

These Rust Metrics lists carry <SERVER_NAME>: 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 <SERVER_NAME> hold among Rust servers?

Ranking for <SERVER_NAME>: #15,409 on seven-day player hours, top 69% of all ranked servers.

What is the population on <SERVER_NAME>?

Reading for <SERVER_NAME>: offline at this moment; last seen 5 days 15 hours ago. Seven-day reading: 0 players on average.

Server

Which location does <SERVER_NAME> run from?

No region tag on <SERVER_NAME>. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 98.97.13.208:28015.

What Rust version is <SERVER_NAME> on?

Rust network protocol 2634 and build 167781 on Linux is the build <SERVER_NAME> runs. Matching protocol is required to join. Let Steam update your game.

Is <SERVER_NAME> up, and how often does it stay up?

Reading: offline. <SERVER_NAME> last answered 5 days 15 hours ago. Uptime for the last 5 full days: 9 of 120 hours, or 8%. The first sighting on Rust Metrics was 21 October 2026.

Rules and settings

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

No gather rate appears in the name: <SERVER_NAME>. 8 players per group, the default value. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is <SERVER_NAME> on?

The game generates a procedural map for <SERVER_NAME>.

How to join

What do you do to join <SERVER_NAME>?

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

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp0
Max players 0 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167781
Build The server runs game build 167781.
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.