RUST METRICSFlight deck · live data
Data live Servers11,834 Players79,225 Populated3,875 Fresh wipes 3 h158 Scan5 min
‹ All servers46.53.210.208:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 46.53.210.208:28015 checked 7d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 2 /10

Players now

20% 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#12,662top 57%
Last wipe14d 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
15k10k15k20k20 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

Top 57% 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

What wipe timing does TEST follow?

The rhythm of TEST's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 14 days 7 hours ago.

Tags

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; mp10 (Max players): Slots: 10; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server from TEST. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does TEST appear in Rust Metrics lists and filters?

These Rust Metrics lists carry TEST: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

What position does TEST hold among Rust servers?

Ranking for TEST: #12,662 on seven-day player hours, top 57% of all ranked servers.

What player count does TEST carry?

Status for TEST: offline. Last seen 7 days 2 hours ago. Seven-day check: 1 players on average. Peak reading: 2.

Server

Where does TEST sit?

Reading: location. TEST gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 46.53.210.208:28015.

What Rust version is TEST on?

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

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

TEST reports offline. The last reading came 7 days 2 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 20 October 2026.

Map and rules

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

Reading the name gives no gather rate for TEST. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on TEST?

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

Connection

How can you get onto TEST?

Press F1 in Rust and enter client.connect 46.53.210.208:28015. 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 mp10,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players Slots: 10.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166652
Build Game build reading: 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

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