RUST METRICSFlight deck · live data
Data live Servers11,658 Players44,769 Populated3,058 Fresh wipes 3 h104 Scan5 min
‹ All servers104.7.174.182:28015
Offline Full Queue Fresh wipe Wipe due No query

Rust Server [Docker] Test

Offline 104.7.174.182:28015 checked 44d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

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,172no region published
Last wipe52d 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
No rank history yet.
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 Rust Server [Docker] Test follow?

To tell the rhythm of Rust Server [Docker] Test, too few of its wipes 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 52 days 8 hours ago.

Lists and filters

Which tags does Rust Server [Docker] Test carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163493 (Build): Build 163493; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from Rust Server [Docker] Test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does Rust Server [Docker] Test appear in Rust Metrics lists and filters?

Rust Metrics lists featuring Rust Server [Docker] Test: 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.

Population

What position does Rust Server [Docker] Test hold among Rust servers?

Player hours over seven days put Rust Server [Docker] Test at #15,172, in the top – of all ranked servers.

What is the population on Rust Server [Docker] Test?

Status for Rust Server [Docker] Test: offline. Last seen 44 days 8 hours ago.

Server details

Where does Rust Server [Docker] Test sit?

No region tag on Rust Server [Docker] Test. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 104.7.174.182:28015.

What Rust version is Rust Server [Docker] Test on?

Version check: Rust network protocol 2633 and build 163493 on Linux, run by Rust Server [Docker] Test. Matching protocol is required to join. Let Steam update your game.

Is Rust Server [Docker] Test up, and how often does it stay up?

Reading: offline. Rust Server [Docker] Test last answered 44 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Rules and settings

What rules does Rust Server [Docker] Test enforce, and what are its settings?

Reading the name gives no gather rate for Rust Server [Docker] Test. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Rust Server [Docker] Test?

Check: map. Procedural, generated by the game, on Rust Server [Docker] Test.

Join

What do you do to join Rust Server [Docker] Test?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players 5 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163493
Build Build 163493.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^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.