RUST METRICSFlight deck · live data
Data live Servers11,590 Players33,807 Populated2,855 Fresh wipes 3 h65 Scan5 min
‹ All servers5.164.252.134:28015
Offline Full Queue Fresh wipe Wipe due No query

test

Offline 5.164.252.134:28015 checked 29d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 4 8 11 15 PAX 0 /15

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#16,247top 68%
Last wipe29d 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
15k10k15k20k28 Sep29 Sep1 Oct2 Oct4 Oct5 Oct

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

To tell the rhythm of 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 in play was created 29 days 17 hours ago.

Tag meanings

How should you read the tags on test?

These are the tags test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp15 (Max players): Slots: 15; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166016 (Build): Game build reading: 166016; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Plugin framework in use: Carbon. 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 Carbon ^y; Group limit: 5 or more.

Population

What position does test hold among Rust servers?

Ranking for test: #16,247 on seven-day player hours, top 68% of all ranked servers.

How full does test get?

Reading for test: offline at this moment; last seen 29 days 16 hours ago.

Server details

Which location does test run from?

No region tag on test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 5.164.252.134:28015.

What Rust version is test on?

Version check: Rust network protocol 2634 and build 166016 on Windows, run by test. Matching protocol is required to join. Let Steam update your game.

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

test reports offline. The last reading came 29 days 16 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 28 September 2026.

Rules and settings

What settings and rules apply on test?

Reading the name gives no gather rate for test. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Carbon plugins are running. VAC is on. That is Valve's anti-cheat.

What map is test on?

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

How to join

What do you do to join test?

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

PLACARDS

Server tags

what each one means

Published as mp15,ptrak,$r?,v2634,gmrust,cs166016,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp15
Max players Slots: 15.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166016
Build Game build reading: 166016.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^y
Carbon Plugin framework in use: Carbon.

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.