RUST METRICSFlight deck · live data
Data live Servers11,877 Players95,616 Populated4,087 Fresh wipes 3 h156 Scan5 min
‹ All servers147.189.171.132:28015
Offline Full Queue Fresh wipe Wipe due No query

ZapX Rust Test

Offline 147.189.171.132:28015 checked 25d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 0 /50

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,917top 69%
Last wipe25d agono schedule published
Next wipe–no wipe 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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 schedule

How often does ZapX Rust Test wipe, and when?

Its rhythm cannot be told from the wipes of ZapX Rust 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. 25 days 12 hours ago the current world was made.

Tag meanings

How should you read the tags on ZapX Rust Test?

These are the tags ZapX Rust Test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166586 (Build): Game build reading: 166586; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. 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 ZapX Rust Test?

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

What position does ZapX Rust Test hold among Rust servers?

Player hours over seven days put ZapX Rust Test at #15,917, in the top 69% of all ranked servers.

What is the population on ZapX Rust Test?

ZapX Rust Test is not responding; status offline, last seen 25 days 10 hours ago.

Server details

Where does ZapX Rust Test sit?

Reading: location. ZapX Rust Test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 147.189.171.132:28015.

What Rust version is ZapX Rust Test on?

Rust network protocol 2634 and build 166586 on Linux is the build ZapX Rust Test runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on ZapX Rust Test, and is it online?

Reading: offline. ZapX Rust Test last answered 25 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 2 October 2026, recorded by Rust Metrics.

Map and rules

What rules does ZapX Rust Test enforce, and what are its settings?

No gather rate appears in the name: ZapX Rust Test. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on ZapX Rust Test?

The game generates a procedural map for ZapX Rust Test.

How to join

What do you do to join ZapX Rust Test?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players Slots: 50.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166586
Build Game build reading: 166586.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.