RUST METRICSFlight deck · live data
Data live Servers11,695 Players39,471 Populated2,990 Fresh wipes 3 h89 Scan5 min
‹ All servers92.124.206.153:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 92.124.206.153:28015 checked 6d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.5 1 1.5 2 PAX 2 /2

Players now

100% 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 2
Rank#9,047top 41%
Last wipe6d 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
12.5k5k7.5k10k22 Oct23 Oct25 Oct26 Oct28 Oct29 Oct

Top 41% 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 schedule

What wipe timing does TEST follow?

Its rhythm cannot be told from the wipes of TEST 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. 6 days 15 hours ago the current world was made.

Lists and filters

How should you read the tags on TEST?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; 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): Modded: plugins or settings depart from the stock game from TEST. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

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; Last wipe: In the last week.

Player count

Where does TEST sit in the rankings?

Ranking for TEST: #9,047 on seven-day player hours, top 41% of all ranked servers.

What player count does TEST carry?

Reading for TEST: offline at this moment; last seen 6 days 12 hours ago. Check: players over seven days. Average 1, peak 2.

Operator and location

Where does TEST sit?

No region tag on TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 92.124.206.153:28015.

What Rust version is TEST on?

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

How reliable is TEST, and is it online now?

Reading: offline. TEST last answered 6 days 12 hours ago. Reading: 0% uptime over the last 6 full days. It was up 0 of 144 hours. The first sighting on Rust Metrics was 22 October 2026.

Rules and settings

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

No gather rate appears in the name: TEST. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on TEST?

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

Join

What do you do to join TEST?

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

PLACARDS

Server tags

what each one means

Published as mp2,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp2
Max players The server holds 2 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 167781.
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 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.