RUST METRICSFlight deck · live data
Data live Servers11,696 Players36,352 Populated2,907 Fresh wipes 3 h94 Scan5 min
‹ All servers1.170.164.40:28015
Offline Full Queue Fresh wipe Wipe due No query

Test

Offline 1.170.164.40:28015 checked 25d ago

moddedoxide
COM 1 · connect

Server instruments

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

Players now

20% 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,911top 61%
Last wipe26d 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
15k10k15k20k20 Sep24 Sep28 Sep2 Oct6 Oct10 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.

usual gap0.3 daysbetween real wipes
wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

Fri 2 OctFri 2 Oct
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 10 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 16:35 UTC26d ago 2 – running 0
Fri 2 Oct, 08:22 UTC26d ago 2 – 0.3 days 0

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 happens on Test when wipe day comes?

An average of 2 players came at the busiest on its recent wipes. 10 hours after the wipe, the crowd peaked on the latest wipe.

How often does Test wipe, and when?

To tell the rhythm of Test, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 26 days 18 hours ago the current world was made.

Lists and filters

How should you read the tags on Test?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166586 (Build): The server runs game build 166586; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server 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. Check: filters. On the server list it appears under these: 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: #13,911 on seven-day player hours, top 61% of all ranked servers.

How full does Test get?

Reading for Test: offline at this moment; last seen 25 days 5 hours ago.

Server details

Which location does Test run from?

Reading: location. Test gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 1.170.164.40:28015.

What Rust version is Test on?

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

How reliable is Test, and is it online now?

Reading: offline. Test last answered 25 days 5 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 20 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on Test?

Check: gather rate. The name Test does not state one. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Test?

Procedural map on Test, made by the game's generator.

Connection

How can you get onto Test?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs166586,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166586
Build The server runs game build 166586.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^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.