RUST METRICSFlight deck · live data
Data live Servers11,696 Players36,352 Populated2,907 Fresh wipes 3 h94 Scan5 min
‹ All servers81.92.203.67:28015
Offline Full Queue Fresh wipe Wipe due No query

local test

Offline 81.92.203.67:28015 checked 7d ago

COM 1 · connect

Server instruments

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

Players now

20% 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#12,376top 56%
Last wipe7d 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
15k10k15k20k21 Oct22 Oct24 Oct25 Oct27 Oct28 Oct

Top 56% 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, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 21 Oct, 14:46 UTC7d ago 1 – running 1

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 local test?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

How often does local test wipe, and when?

The rhythm of local test's wipes cannot be told yet: too few 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. 7 days 12 hours ago the current world was made.

Tag meanings

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from local test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does local test appear in Rust Metrics lists and filters?

Rust Metrics lists featuring local test: 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; Last wipe: In the last 2 weeks.

Player count

Where does local test sit in the rankings?

Ranking for local test: #12,376 on seven-day player hours, top 56% of all ranked servers.

How full does local test get?

Reading for local test: offline at this moment; last seen 7 days 9 hours ago.

Server

What location is local test hosted in?

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

What Rust version is local test on?

Rust network protocol 2634 and build 167781 on Windows is the build local test runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is local test, and is it online now?

Check: connection. local test is offline at this moment. Last contact was 7 days 9 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 21 October 2026.

Settings and map

What settings and rules apply on local test?

Reading the name gives no gather rate for local test. 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. Combat and raiding against other players are on. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is off.

What map is local test on?

Check: map. Procedural, generated by the game, on local test.

Join

What do you do to join local test?

Check: join. Open Rust, press F1, then enter client.connect 81.92.203.67: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 The game mode is plain Rust survival.
mp5
Max players Slots: 5.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 167781.
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.