RUST METRICSFlight deck · live data
Data live Servers11,702 Players66,491 Populated3,572 Fresh wipes 3 h116 Scan5 min
‹ All servers94.41.131.169:28015
Offline Full Queue Fresh wipe Wipe due No query

your_server_name

Offline 94.41.131.169:28015 checked 20d 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,903top 72%
Last wipe20d 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
15k10k15k20k7 Oct8 Oct10 Oct11 Oct13 Oct14 Oct

Top 72% 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

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 7 Oct, 19:28 UTC20d 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 should you expect from wipe day on your_server_name?

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 your_server_name wipe?

To tell the rhythm of your_server_name, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 20 days 16 hours ago the current world was made.

Lists and filters

How should you read the tags on your_server_name?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167058 (Build): Build 167058; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from your_server_name. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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. 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

What position does your_server_name hold among Rust servers?

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

What player count does your_server_name carry?

Reading for your_server_name: offline at this moment; last seen 20 days 16 hours ago.

Server

Where does your_server_name sit?

Reading: location. your_server_name gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 94.41.131.169:28015.

What Rust version is your_server_name on?

Reading: your_server_name, Rust network protocol 2634 and build 167058, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on your_server_name, and is it online?

Check: connection. your_server_name is offline at this moment. Last contact was 20 days 16 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 7 October 2026.

Map and rules

What settings and rules apply on your_server_name?

Reading the name gives no gather rate for your_server_name. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.

What map is your_server_name on?

The game generates a procedural map for your_server_name.

How to join

How can you get onto your_server_name?

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167058
Build Build 167058.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.