RUST METRICSFlight deck · live data
Data live Servers11,680 Players52,558 Populated3,201 Fresh wipes 3 h137 Scan5 min
‹ All servers138.36.32.33:28016
Offline Full Queue Fresh wipe Wipe due No query

test 2

Offline 138.36.32.33:28016 checked 3d ago

moddedoxide
COM 1 · connect

Server instruments

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

Players now

2% full 7-day avg7-day peak
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 average1peak 1
Rank#6,577top 30%
Last wipe21d 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
15k10k15k20k22 Oct23 Oct25 Oct26 Oct28 Oct29 Oct

Top 30% 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 timing

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 in play was created 21 days 20 hours ago.

Tags

How should you read the tags on test 2?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock 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?

On Rust Metrics, test 2 sits in these lists: 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.

Player count

What position does test 2 hold among Rust servers?

Ranking for test 2: #6,577 on seven-day player hours, top 30% of all ranked servers.

What is the population on test 2?

test 2 is not responding; status offline, last seen 3 days 8 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Server

What location is test 2 hosted in?

No region comes from test 2. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 138.36.32.33:28016.

What Rust version is test 2 on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by test 2. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on test 2, and is it online?

test 2 reports offline. The last reading came 3 days 8 hours ago. Uptime for the last 6 full days: 17 of 144 hours, or 12%. Reading: first seen 22 October 2026, recorded by Rust Metrics.

Settings and map

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

No gather rate appears in the name: test 2. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

How to join

How do you connect to test 2?

Press F1 in Rust and enter client.connect 138.36.32.33:28016. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players The server holds 50 slots.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Modded: plugins or settings depart from the stock 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.