RUST METRICSFlight deck · live data
Data live Servers11,880 Players96,217 Populated4,117 Fresh wipes 3 h159 Scan5 min
‹ All servers46.98.98.17:28015
Offline Full Queue Fresh wipe Wipe due No query

your_server_name

Offline 46.98.98.17:28015 checked 10d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

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,159top 70%
Last wipe13d 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
15k10k15k20k11 Oct14 Oct16 Oct19 Oct21 Oct24 Oct

Top 70% 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.

usual gap2.4 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Tue 13 OctSun 11 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
Tue 13 Oct, 19:23 UTC13d ago 1 – running 1
Sun 11 Oct, 09:26 UTC16d ago 1 – 2.4 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

Reset cycle

What happens on your_server_name when wipe day comes?

An average of 1 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 your_server_name follow?

The rhythm of your_server_name'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. The world it runs now was made 13 days 22 hours ago.

Lists and filters

How should you read the tags on your_server_name?

These are the tags your_server_name publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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 your_server_name appear in Rust Metrics lists and filters?

These Rust Metrics lists carry your_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; Last wipe: In the last 2 weeks.

Population

What position does your_server_name hold among Rust servers?

Player hours over seven days put your_server_name at #15,159, in the top 70% of all ranked servers.

What player count does your_server_name carry?

Reading for your_server_name: offline at this moment; last seen 10 days ago.

Operator and location

What location is your_server_name hosted in?

No region comes from your_server_name. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 46.98.98.17:28015.

What Rust version is your_server_name on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by your_server_name. To get in, your game needs the same protocol; Steam applies the update.

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

your_server_name reports offline. The last reading came 10 days ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 11 October 2026, recorded by Rust Metrics.

Settings and map

How is your_server_name configured, and what rules are in force?

Reading the name gives no gather rate for your_server_name. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on your_server_name?

The game generates a procedural map for your_server_name.

How to join

How do you connect to your_server_name?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build 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.