RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h108 Scan5 min
‹ All servers62.226.97.119:28015
Offline Full Queue Fresh wipe Wipe due No query

Test

Offline 62.226.97.119:28015 checked 28d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.8 1.5 2.2 3 PAX 0 /3

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#16,862top 71%
Last wipe31d 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
15k10k15k20k26 Sep28 Sep30 Sep2 Oct4 Oct6 Oct

Top 71% 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
Sat 26 Sep, 20:20 UTC31d 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 schedule

What should you expect from wipe day on Test?

An average of 1 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does Test wipe, and when?

Its rhythm cannot be told from the wipes of Test on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 31 days 21 hours ago the current world was made.

Tag meanings

How should you read the tags on Test?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp3 (Max players): The server holds 3 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server from Test. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Test appear in Rust Metrics lists and filters?

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

Where does Test sit in the rankings?

Ranking for Test: #16,862 on seven-day player hours, top 71% of all ranked servers.

How full does Test get?

Test is not responding; status offline, last seen 28 days 20 hours ago.

Operator and location

Which location does Test run from?

No region comes from Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 62.226.97.119:28015.

What Rust version is Test on?

Version check: Rust network protocol 2633 and build 163794 on Windows, run by Test. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. Test last answered 28 days 20 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 26 September 2026.

Map and rules

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

Check: gather rate. The name Test does not state one. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

What map is Test on?

Check: map. Procedural, generated by the game, on Test.

Connection

How do you connect to Test?

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

PLACARDS

Server tags

what each one means

Published as mp3,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp3
Max players The server holds 3 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Build 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Plugins or settings make this a modded server.

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.