RUST METRICSFlight deck · live data
Data live Servers11,747 Players58,097 Populated3,441 Fresh wipes 3 h135 Scan5 min
‹ All servers104.28.161.35:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 104.28.161.35:28015 checked 21d ago

moddedoxide
COM 1 · connect

Server instruments

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

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#15,990top 71%
Last wipe22d 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
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 Oct

Top 71% 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. The world it runs now was made 22 days 15 hours ago.

Lists and filters

How should you read the tags on TEST?

These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): The server runs game build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. 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.

Player count

Where does TEST sit in the rankings?

Player hours over seven days put TEST at #15,990, in the top 71% of all ranked servers.

How full does TEST get?

Reading for TEST: offline at this moment; last seen 21 days 6 hours ago.

Server details

What location is TEST hosted in?

Reading: location. TEST gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 104.28.161.35:28015.

What Rust version is TEST on?

Rust network protocol 2634 and build 166652 on Windows is the build TEST runs. To get in, your game needs the same protocol; Steam applies the update.

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

Check: connection. TEST is offline at this moment. Last contact was 21 days 6 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 6 October 2026, recorded by Rust Metrics.

Settings and map

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

Reading the name gives no gather rate for TEST. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

What map is TEST on?

The game generates a procedural map for TEST.

Connection

What do you do to join TEST?

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

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build The server runs game build 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

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