RUST METRICSFlight deck · live data
Data live Servers11,617 Players35,735 Populated2,880 Fresh wipes 3 h74 Scan5 min
‹ All servers124.189.16.82:28015
Offline Full Queue Fresh wipe Wipe due No query

local test

Offline 124.189.16.82:28015 checked 9d 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,340top 69%
Last wipe9d 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
15k10k15k20k19 Oct21 Oct22 Oct24 Oct25 Oct27 Oct

Top 69% 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 gap0.8 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Tue 20 OctMon 19 Oct
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 20 Oct, 02:59 UTC9d ago 0 – running 1
Mon 19 Oct, 08:24 UTC9d ago 1 – 0.8 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 local test when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 1 hours.

How often does local test wipe, and when?

Its rhythm cannot be told from the wipes of local test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 9 days 3 hours ago the current world was made.

Lists and filters

How should you read the tags on local test?

These are the tags local test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): The server holds 5 slots; 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): Game build reading: 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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

On Rust Metrics, local test sits in these lists: 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; Last wipe: In the last 2 weeks.

Player count

Where does local test sit in the rankings?

Ranking for local test: #15,340 on seven-day player hours, top 69% of all ranked servers.

What is the population on local test?

local test is not responding; status offline, last seen 9 days 3 hours ago.

Operator and location

Where does local test sit?

No region comes from local test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 124.189.16.82:28015.

What Rust version is local test on?

Rust network protocol 2634 and build 167781 on Windows is the build local test runs. Matching protocol is required to join. Let Steam update your game.

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

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

Settings and map

What settings and rules apply on local test?

No gather rate appears in the name: local test. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on local test?

The game generates a procedural map for local test.

Connection

What do you do to join local test?

To join: start Rust, press F1 and type client.connect 124.189.16.82:28015. Or press Launch Rust here and Steam opens the game 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 The server holds 5 slots.
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 Game build reading: 167781.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.