RUST METRICSFlight deck · live data
Data live Servers11,619 Players41,711 Populated3,041 Fresh wipes 3 h92 Scan5 min
‹ All servers24.171.68.3:28015
Offline Full Queue Fresh wipe Wipe due No query

<SERVER_NAME>

Offline 24.171.68.3:28015 checked 10d 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,330top 70%
Last wipe26d agono schedule published
Next wipe8d 11hThu 5 Nov, 19:00 UTC FW
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
15k10k15k20k20 Sep26 Sep7 Oct12 Oct18 Oct24 Oct

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

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 8d 11h. The force wipe · high confidence

wipe-day peak0players, last three wipes

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC8d 11hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC36d 11hFW

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
Thu 1 Oct, 23:20 UTC FW26d 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

Reset cycle

What happens on <SERVER_NAME> when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does <SERVER_NAME> wipe?

Once a month <SERVER_NAME> wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 26 days 8 hours ago the current world was made.

Tag meanings

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): The server holds 0 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $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.

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.

Player count

What position does <SERVER_NAME> hold among Rust servers?

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

What is the population on <SERVER_NAME>?

Status for <SERVER_NAME>: offline. Last seen 10 days 7 hours ago.

Server

What location is <SERVER_NAME> hosted in?

Reading: location. <SERVER_NAME> gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 24.171.68.3:28015.

What Rust version is <SERVER_NAME> on?

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

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

Check: connection. <SERVER_NAME> is offline at this moment. Last contact was 10 days 7 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

What settings and rules apply on <SERVER_NAME>?

Reading the name gives no gather rate for <SERVER_NAME>. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

Which map is live on <SERVER_NAME>?

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

Connection

How can you get onto <SERVER_NAME>?

Press F1 in Rust and enter client.connect 24.171.68.3: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 The server holds 0 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.