RUST METRICSFlight deck · live data
Data live Servers11,651 Players43,576 Populated2,910 Fresh wipes 3 h101 Scan5 min
‹ All servers104.28.217.175:28015
Offline Full Queue Fresh wipe Wipe due No query

Local_Test

Offline 104.28.217.175:28015 checked 17d 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,543top 71%
Last wipe17d 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 Oct15 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.

wipe-day peak0players, 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 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 09:19 UTC17d ago 0 – 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

Wipe timing

What happens on Local_Test when wipe day comes?

At their busiest, 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. 17 days 18 hours ago the current world was made.

Lists and filters

How should you read the tags on Local_Test?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167584 (Build): Build 167584; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from Local_Test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Local_Test?

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.

Occupancy

What position does Local_Test hold among Rust servers?

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

What is the population on Local_Test?

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

Server

Where does Local_Test sit?

Reading: location. Local_Test gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 104.28.217.175:28015.

What Rust version is Local_Test on?

Version check: Rust network protocol 2634 and build 167584 on Windows, run by Local_Test. To get in, your game needs the same protocol; Steam applies the update.

Is Local_Test up, and how often does it stay up?

Reading: offline. Local_Test last answered 17 days 17 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 16 September 2026, recorded by Rust Metrics.

Map and rules

How is Local_Test configured, and what rules are in force?

No gather rate appears in the name: Local_Test. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.

Which map is live on Local_Test?

Check: map. Procedural, generated by the game, on Local_Test.

How to join

How can you get onto Local_Test?

Press F1 in Rust and enter client.connect 104.28.217.175: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 mp10,ptrak,$r?,v2634,gmrust,cs167584,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167584
Build Build 167584.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.