RUST METRICSFlight deck · live data
Data live Servers11,752 Players56,681 Populated3,410 Fresh wipes 3 h130 Scan5 min
‹ All servers104.28.197.15:28015
Offline Full Queue Fresh wipe Wipe due No query

Parallax Local Test

Offline 104.28.197.15:28015 checked 25d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1 2 3 4 PAX 1 /4

Players now

25% 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#13,901top 61%
Last wipe25d 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
15k10k15k20k26 Sep29 Sep2 Oct4 Oct7 Oct10 Oct

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

00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 3 Oct, 12:18 UTC25d ago 1 – running 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 should you expect from wipe day on Parallax Local Test?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does Parallax Local Test follow?

The rhythm of Parallax Local Test's wipes cannot be told yet: too few 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 it runs now was made 25 days 10 hours ago.

Lists and filters

How should you read the tags on Parallax Local Test?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp4 (Max players): Slots: 4; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): The server runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from Parallax 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 Parallax Local Test?

On Rust Metrics, Parallax 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.

Player count

Where does Parallax Local Test sit in the rankings?

Ranking for Parallax Local Test: #13,901 on seven-day player hours, top 61% of all ranked servers.

What player count does Parallax Local Test carry?

Reading for Parallax Local Test: offline at this moment; last seen 25 days ago.

Server details

Which location does Parallax Local Test run from?

Reading: location. Parallax Local Test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 104.28.197.15:28015.

What Rust version is Parallax Local Test on?

Reading: Parallax Local Test, Rust network protocol 2634 and build 166652, Windows. To get in, your game needs the same protocol; Steam applies the update.

Is Parallax Local Test up, and how often does it stay up?

Reading: offline. Parallax Local Test last answered 25 days ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 26 September 2026.

Rules and settings

What settings and rules apply on Parallax Local Test?

No gather rate appears in the name: Parallax Local Test. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.

Which map is live on Parallax Local Test?

Procedural map on Parallax Local Test, made by the game's generator.

Connection

How do you connect to Parallax Local Test?

Check: join. Open Rust, press F1, then enter client.connect 104.28.197.15:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp4,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp4
Max players Slots: 4.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build The server runs game build 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.