RUST METRICSFlight deck · live data
Data live Servers11,681 Players55,814 Populated3,378 Fresh wipes 3 h102 Scan5 min
‹ All servers176.124.164.7:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 176.124.164.7:28015 checked 17d ago

moddedoxide
COM 1 · connect

Server instruments

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

Players now

10% 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#13,613top 62%
Last wipe17d 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
15k10k15k20k10 Oct11 Oct13 Oct14 Oct16 Oct17 Oct

Top 62% 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?

Its rhythm cannot be told from the wipes of TEST on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 17 days 23 hours ago the current world was made.

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): Protocol 2634: join only on the same game version; cs166652 (Build): Build 166652; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the 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?

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

Where does TEST sit in the rankings?

Player hours over seven days put TEST at #13,613, in the top 62% of all ranked servers.

How full does TEST get?

Reading for TEST: offline at this moment; last seen 17 days 23 hours ago.

Server details

Which location does TEST run from?

Reading: location. TEST gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 176.124.164.7:28015.

What Rust version is TEST on?

Rust network protocol 2634 and build 166652 on Windows is the build TEST runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. TEST last answered 17 days 23 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 10 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. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. 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?

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 176.124.164.7: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 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 Protocol 2634: join only on the same game version.
cs166652
Build Build 166652.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none 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.