RUST METRICSFlight deck · live data
Data live Servers11,706 Players60,014 Populated3,275 Fresh wipes 3 h169 Scan5 min
‹ All servers142.189.204.220:28015
Offline Full Queue Fresh wipe Wipe due No query

localtest

Offline 142.189.204.220:28015 checked 6h ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,003top 63%
Last wipe19h agono schedule published
Next wipe–too few wipes seen yet
Memory–48 h peak 1 players
REC 1

Players

AveragePeakWipe
00.250.50.75104:0007:0010:0012:0015:0018:00Wiped Thu 29 Oct, 05:06 UTCWIPE

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
15k10k15k20k12 Oct14 Oct15 Oct17 Oct18 Oct20 Oct

Top 63% 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 gap15.6 daysbetween real wipes
wipe-day peak1players, 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 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 29 Oct, 04:53 UTC19h ago – – running 1
Tue 13 Oct, 15:03 UTC16d ago 1 – – 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 localtest when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 0 hours in.

What wipe timing does localtest follow?

Its rhythm cannot be told from the wipes of localtest on record: there are too few. 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 19 hours ago.

Tag meanings

How should you read the tags on localtest?

These are the tags localtest publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; 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): Game build reading: 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 localtest appear in Rust Metrics lists and filters?

On Rust Metrics, localtest sits in these lists: 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 24 hours.

Occupancy

Where does localtest sit in the rankings?

Ranking for localtest: #14,003 on seven-day player hours, top 63% of all ranked servers.

How full does localtest get?

Reading for localtest: offline at this moment; last seen 6 hours ago. Check: players over seven days. Average 0, peak 1. The last 48 hours peaked at 05:00 UTC, averaging 1 players at that hour.

Operator and location

Where does localtest sit?

No region tag on localtest. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 142.189.204.220:28015.

What Rust version is localtest on?

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

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

Check: connection. localtest is offline at this moment. Last contact was 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 12 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on localtest?

Reading the name gives no gather rate for localtest. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is localtest on?

Procedural map on localtest, made by the game's generator.

Connection

How can you get onto localtest?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
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 Game build reading: 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.