RUST METRICSFlight deck · live data
Data live Servers11,623 Players37,934 Populated2,921 Fresh wipes 3 h81 Scan5 min
‹ All servers124.189.20.69:28015
Offline Full Queue Fresh wipe Wipe due No query

local test

Offline 124.189.20.69:28015 checked 5d 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 avg7-day peak
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 1
Rank#14,673top 66%
Last wipe5d 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
15k10k15k20k23 Oct24 Oct25 Oct27 Oct28 Oct29 Oct

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

01234+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
Fri 23 Oct, 12:54 UTC5d 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

Reset cycle

What happens on local test when wipe day comes?

The busiest point of its recent wipes drew 1 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. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 5 days 18 hours ago.

Tags

How should you read the tags on local test?

Tags published by local test, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $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. 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; Last wipe: In the last week.

Occupancy

What position does local test hold among Rust servers?

Player hours over seven days put local test at #14,673, in the top 66% of all ranked servers.

What is the population on local test?

local test is not responding; status offline, last seen 5 days 18 hours ago. Seven-day check: 0 players on average. Peak reading: 1.

Operator and location

Where does local test sit?

No region comes from local test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 124.189.20.69:28015.

What Rust version is local test on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by local test. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on local test, and is it online?

local test reports offline. The last reading came 5 days 18 hours ago. Uptime for the last 5 full days: 0 of 120 hours, or 0%. Check: first contact. Rust Metrics logged it on 23 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, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is off. That is Valve's anti-cheat.

What map is local test on?

The game generates a procedural map for local test.

Connection

How can you get onto local test?

Press F1 in Rust and enter client.connect 124.189.20.69: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?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players 5 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.