RUST METRICSFlight deck · live data
Data live Servers11,686 Players34,939 Populated2,865 Fresh wipes 3 h97 Scan5 min
‹ All servers194.50.170.71:28015
Offline Full Queue Fresh wipe Wipe due No query

My test SERVER

Offline 194.50.170.71:28015 checked 15d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 1 /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#13,224top 61%
Last wipe15d 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
15k10k15k20k13 Oct14 Oct16 Oct17 Oct19 Oct20 Oct

Top 61% 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 peak1players, last three wipes

The first 48 hours of its last wipes

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 13 Oct, 07:42 UTC15d ago 1 – 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 timing

What happens on My test SERVER when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 1 hours in.

How often does My test SERVER wipe, and when?

To tell the rhythm of My test SERVER, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 15 days 19 hours ago.

Tag meanings

Which tags does My test SERVER carry, and what do they mean?

Tags published by My test SERVER, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): The server holds 500 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167584 (Build): Build 167584; 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 My test SERVER appear in Rust Metrics lists and filters?

These Rust Metrics lists carry My test SERVER: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does My test SERVER hold among Rust servers?

Ranking for My test SERVER: #13,224 on seven-day player hours, top 61% of all ranked servers.

What is the population on My test SERVER?

My test SERVER is not responding; status offline, last seen 15 days 18 hours ago.

Operator and location

Which location does My test SERVER run from?

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

What Rust version is My test SERVER on?

Rust network protocol 2634 and build 167584 on Windows is the build My test SERVER runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on My test SERVER, and is it online?

Reading: offline. My test SERVER last answered 15 days 18 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on My test SERVER?

No gather rate appears in the name: My test SERVER. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is My test SERVER on?

The game generates a procedural map for My test SERVER.

How to join

What do you do to join My test SERVER?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players The server holds 500 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167584
Build Build 167584.
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.