RUST METRICSFlight deck · live data
Data live Servers11,610 Players35,756 Populated2,903 Fresh wipes 3 h66 Scan5 min
‹ All servers178.155.60.99:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST

Offline 178.155.60.99:28015 checked 12d ago

moddedoxide
COM 1 · connect
Launch Rust and join

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#12,834top 59%
Last wipe12d 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
15k10k15k20k15 Oct16 Oct18 Oct19 Oct21 Oct22 Oct

Top 59% 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

Reset cycle

What wipe timing does TEST follow?

Its rhythm cannot be told from the wipes of TEST on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 12 days 12 hours ago.

Lists and filters

Which tags does TEST carry, and what do they mean?

These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): 10 slots in total; 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): Game build reading: 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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; Last wipe: In the last 2 weeks.

Population

Where does TEST sit in the rankings?

Ranking for TEST: #12,834 on seven-day player hours, top 59% of all ranked servers.

How full does TEST get?

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

Server

Where does TEST sit?

Reading: location. TEST gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 178.155.60.99:28015.

What Rust version is TEST on?

Version check: Rust network protocol 2634 and build 166652 on Windows, run by TEST. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on TEST, and is it online?

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

Rules and settings

What settings and rules apply on TEST?

No gather rate appears in the name: TEST. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

What map is TEST on?

Check: map. Procedural, generated by the game, on TEST.

How to join

How can you get onto TEST?

To join: start Rust, press F1 and type client.connect 178.155.60.99:28015. Or press Launch Rust here and Steam opens the game 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 10 slots in total.
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 Game build reading: 166652.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is 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.