RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h0 Scan5 min
‹ All servers92.208.255.97:28015
Offline Full Queue Fresh wipe Wipe due No query

my_server

Offline 92.208.255.97:28015 checked 23d 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#15,963top 71%
Last wipe23d 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
15k10k15k20k5 Oct6 Oct8 Oct9 Oct11 Oct12 Oct

Top 71% 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 peak0players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 14:27 UTC23d ago 0 – 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

Wipe schedule

What happens on my_server when wipe day comes?

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

How often does my_server wipe, and when?

Its rhythm cannot be told from the wipes of my_server 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. 23 days 1 hours ago the current world was made.

Lists and filters

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

These are the tags my_server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166757 (Build): Build 166757; ptrak (Networking): This is RakNet, Rust's usual network layer; $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.

Where does my_server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry my_server: 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.

Population

Where does my_server sit in the rankings?

Player hours over seven days put my_server at #15,963, in the top 71% of all ranked servers.

What is the population on my_server?

Reading for my_server: offline at this moment; last seen 23 days ago.

Server

Where does my_server sit?

No region comes from my_server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 92.208.255.97:28015.

What Rust version is my_server on?

Version check: Rust network protocol 2634 and build 166757 on Windows, run by my_server. Matching protocol is required to join. Let Steam update your game.

Is my_server up, and how often does it stay up?

my_server reports offline. The last reading came 23 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 5 October 2026, recorded by Rust Metrics.

Rules and settings

What rules does my_server enforce, and what are its settings?

Check: gather rate. The name my_server does not state one. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on my_server?

Procedural map on my_server, made by the game's generator.

How to join

What do you do to join my_server?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players The server holds 500 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166757
Build Build 166757.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.