RUST METRICSFlight deck · live data
Data live Servers11,709 Players55,398 Populated3,239 Fresh wipes 3 h162 Scan5 min
‹ All servers119.169.0.246:31015
Offline Full Queue Fresh wipe Wipe due No query

test

Offline 119.169.0.246:31015 checked 31d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 2 /500

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#12,824top 54%
Last wipe49d 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, measured since 28 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k27 Sep29 Sep30 Sep2 Oct3 Oct5 Oct

Top 54% 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 wipe?

The rhythm of test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 49 days 20 hours ago.

Tag meanings

How should you read the tags on test?

Tags published by test, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp500 (Max players): 500 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163493 (Build): The server runs game build 163493; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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?

Rust Metrics lists featuring test: 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

Where does test sit in the rankings?

Ranking for test: #12,824 on seven-day player hours, top 54% of all ranked servers.

How full does test get?

test is not responding; status offline, last seen 31 days 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. The endpoint you need is 119.169.0.246:31015.

What Rust version is test on?

Rust network protocol 2633 and build 163493 on Windows is the build test runs. Check: protocol. To join, your game must match; Steam handles the update.

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

test reports offline. The last reading came 31 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 27 September 2026.

Map and rules

What settings and rules apply on test?

Reading the name gives no gather rate for test. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

What map is test on?

Size 4,500 and seed 1234567: the game generates the procedural map on test from them. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

What do you do to join test?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2633,gmrust,cs163493,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp500
Max players 500 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163493
Build The server runs game build 163493.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^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.