RUST METRICSFlight deck · live data
Data live Servers11,709 Players55,398 Populated3,239 Fresh wipes 3 h162 Scan5 min
‹ All servers193.32.126.153:28015
Offline Full Queue Fresh wipe Wipe due No query

Test

Offline 193.32.126.153:28015 checked 26d ago

moddedoxide
COM 1 · connect

Server instruments

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

Players now

10% 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,842top 61%
Last wipe26d 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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 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
Fri 2 Oct, 21:52 UTC26d ago 1 – 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 Test 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 Test follow?

The rhythm of Test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 26 days 12 hours ago.

Lists and filters

How should you read the tags on Test?

These are the tags Test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166494 (Build): The server runs game build 166494; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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 Test?

On Rust Metrics, Test sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does Test hold among Rust servers?

Player hours over seven days put Test at #13,842, in the top 61% of all ranked servers.

What is the population on Test?

Status for Test: offline. Last seen 26 days 12 hours ago.

Operator and location

Where does Test sit?

No region comes from Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 193.32.126.153:28015.

What Rust version is Test on?

Reading: Test, Rust network protocol 2634 and build 166494, Windows. Matching protocol is required to join. Let Steam update your game.

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

Test reports offline. The last reading came 26 days 12 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.

Rules and settings

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

No gather rate appears in the name: Test. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Test?

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

Connection

How can you get onto Test?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166494
Build The server runs game build 166494.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter the game.

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.