RUST METRICSFlight deck · live data
Data live Servers11,806 Players72,381 Populated3,700 Fresh wipes 3 h114 Scan5 min
‹ All servers84.32.176.94:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST Server

Offline 84.32.176.94:28015 checked 20d ago

moddedoxide
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 38 75 112 150 PAX 1 /150

Players now

1% 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,632top 62%
Last wipe21d 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
15k10k15k20k22 Sep25 Sep28 Sep9 Oct12 Oct15 Oct

Top 62% 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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 7 Oct, 12:37 UTC21d 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 happens on TEST Server when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe.

How often does TEST Server wipe, and when?

Its rhythm cannot be told from the wipes of TEST Server 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. The world it runs now was made 21 days 8 hours ago.

Tags

How should you read the tags on TEST Server?

These are the tags TEST Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp150 (Max players): The server holds 150 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): Build 166586; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does TEST Server appear in Rust Metrics lists and filters?

These Rust Metrics lists carry TEST Server: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does TEST Server hold among Rust servers?

Player hours over seven days put TEST Server at #13,632, in the top 62% of all ranked servers.

How full does TEST Server get?

TEST Server is not responding; status offline, last seen 20 days 4 hours ago.

Server details

Which location does TEST Server run from?

No region tag on TEST Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 84.32.176.94:28015.

What Rust version is TEST Server on?

Reading: TEST Server, Rust network protocol 2634 and build 166586, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is TEST Server up, and how often does it stay up?

Check: connection. TEST Server is offline at this moment. Last contact was 20 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 22 September 2026.

Settings and map

How is TEST Server configured, and what rules are in force?

No gather rate appears in the name: TEST Server. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

Join

What do you do to join TEST Server?

To join: start Rust, press F1 and type client.connect 84.32.176.94:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp150,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp150
Max players The server holds 150 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166586
Build Build 166586.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide It runs Oxide, also known as 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.