RUST METRICSFlight deck · live data
Data live Servers11,733 Players61,573 Populated3,391 Fresh wipes 3 h185 Scan5 min
‹ All servers138.204.27.157:28016
Offline Full Queue Fresh wipe Wipe due No query

test 2

Offline 138.204.27.157:28016 checked 20d ago

moddedoxide
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,874top 72%
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
15k10k15k20k7 Oct9 Oct10 Oct12 Oct13 Oct15 Oct

Top 72% 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
Wed 7 Oct, 12:59 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

Wipe timing

What should you expect from wipe day on test 2?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

When does test 2 wipe?

To tell the rhythm of test 2, too few of its wipes are on record. 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 22 hours ago.

Lists and filters

How should you read the tags on test 2?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp50 (Max players): 50 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167058 (Build): Build 167058; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game from test 2. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does test 2 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry test 2: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does test 2 hold among Rust servers?

Player hours over seven days put test 2 at #15,874, in the top 72% of all ranked servers.

What player count does test 2 carry?

Status for test 2: offline. Last seen 20 days 14 hours ago.

Operator and location

What location is test 2 hosted in?

No region tag on test 2. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 138.204.27.157:28016.

What Rust version is test 2 on?

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

Is test 2 up, and how often does it stay up?

test 2 reports offline. The last reading came 20 days 14 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 7 October 2026, recorded by Rust Metrics.

Rules and settings

How is test 2 configured, and what rules are in force?

Reading the name gives no gather rate for test 2. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

How to join

How do you connect to test 2?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,gmrust,cs167058,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp50
Max players 50 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167058
Build Build 167058.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is 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.