RUST METRICSFlight deck · live data
Data live Servers11,882 Players97,865 Populated3,914 Fresh wipes 3 h398 Scan5 min
‹ All servers106.178.130.181:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server

Offline 106.178.130.181:28015 checked 17d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 8 16 24 32 PAX 1 /32

Players now

3% 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,364top 61%
Last wipe17d agono schedule published
Next wipe–too few wipes 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
15k10k15k20k21 Sep24 Sep27 Sep13 Oct16 Oct19 Oct

Top 61% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 11:11 UTC17d ago 1 – running 1

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

Reset cycle

What happens on Test Server when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does Test Server follow?

Its rhythm cannot be told from the wipes of Test Server 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. The world it runs now was made 17 days 5 hours ago.

Tag meanings

How should you read the tags on Test Server?

Tags published by Test Server, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp32 (Max players): Slots: 32; ts32 (Group limit): Teams are capped at 32; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167584 (Build): The server runs game build 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Test Server?

Rust Metrics lists featuring Test Server: 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 Server hold among Rust servers?

Ranking for Test Server: #13,364 on seven-day player hours, top 61% of all ranked servers.

How full does Test Server get?

Reading for Test Server: offline at this moment; last seen 17 days 3 hours ago.

Operator and location

Which location does Test Server run from?

No region comes from Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 106.178.130.181:28015.

What Rust version is Test Server on?

Reading: Test Server, Rust network protocol 2634 and build 167584, Windows. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Test Server, and is it online?

Test Server reports offline. The last reading came 17 days 3 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 21 September 2026, recorded by Rust Metrics.

Map and rules

What rules does Test Server enforce, and what are its settings?

Check: gather rate. The name Test Server does not state one. The cap on groups is 32 players. survival, gather, build and raid, as the game normally runs — that is the game mode. 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.

What map is Test Server on?

Check: map. Procedural, generated by the game, on Test Server.

Join

How do you connect to Test Server?

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

PLACARDS

Server tags

what each one means

Published as mp32,ptrak,$r?,v2634,gmrust,cs167584,ts32,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp32
Max players Slots: 32.
ts32
Group limit Teams are capped at 32.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167584
Build The server runs game build 167584.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

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.