RUST METRICSFlight deck · live data
Data live Servers11,707 Players67,519 Populated3,582 Fresh wipes 3 h108 Scan5 min
‹ All servers104.28.249.175:28015
Offline Full Queue Fresh wipe Wipe due No query

Local_Test

Offline 104.28.249.175:28015 checked 16d 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 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,544top 71%
Last wipe16d 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
15k10k15k20k20 Sep22 Sep12 Oct14 Oct17 Oct19 Oct

Top 71% 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 gap25 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Mon 12 OctThu 17 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 09:19 UTC16d ago 0 – running 1
Thu 17 Sep, 10:04 UTC41d ago 1 – 25 days 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

Reset cycle

What happens on Local_Test when wipe day comes?

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

What wipe timing does Local_Test follow?

To tell the rhythm of Local_Test, 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 in play was created 16 days 2 hours ago.

Tag meanings

Which tags does Local_Test carry, and what do they mean?

Tags published by Local_Test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): Build 167584; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Local_Test?

Rust Metrics lists featuring Local_Test: 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.

Occupancy

Where does Local_Test sit in the rankings?

Player hours over seven days put Local_Test at #15,544, in the top 71% of all ranked servers.

How full does Local_Test get?

Local_Test is not responding; status offline, last seen 16 days 2 hours ago.

Operator and location

Which location does Local_Test run from?

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

What Rust version is Local_Test on?

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

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

Check: connection. Local_Test is offline at this moment. Last contact was 16 days 2 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 16 September 2026.

Rules and settings

What rules does Local_Test enforce, and what are its settings?

Check: gather rate. The name Local_Test does not state one. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. 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.

How to join

How can you get onto Local_Test?

To join: start Rust, press F1 and type client.connect 104.28.249.175: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?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167584
Build Build 167584.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.