RUST METRICSFlight deck · live data
Data live Servers11,652 Players32,618 Populated2,799 Fresh wipes 3 h77 Scan5 min
‹ All servers49.192.61.204:28015
Offline Full Queue Fresh wipe Wipe due No query

test

Offline 49.192.61.204:28015 checked 9d ago

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,039top 59%
Last wipe10d 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
15k10k15k20k18 Oct20 Oct21 Oct23 Oct24 Oct26 Oct

Top 59% 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, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 18 Oct, 16:49 UTC10d ago 1 – running 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

Reset cycle

What happens on test when wipe day comes?

The busiest point of its recent wipes drew 1 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe.

When does test wipe?

The rhythm of test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 10 days 10 hours ago.

Tags

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; mp5 (Max players): Slots: 5; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168352 (Build): Game build reading: 168352; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show test?

On Rust Metrics, test sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Occupancy

What position does test hold among Rust servers?

Player hours over seven days put test at #13,039, in the top 59% of all ranked servers.

What player count does test carry?

Status for test: offline. Last seen 9 days 20 hours ago.

Operator and location

Which location does test run from?

Reading: location. test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 49.192.61.204:28015.

What Rust version is test on?

Reading: test, Rust network protocol 2635 and build 168352, Windows. To get in, your game needs the same protocol; Steam applies the update.

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

test reports offline. The last reading came 9 days 20 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 18 October 2026, recorded by Rust Metrics.

Map and rules

What rules does test enforce, and what are its settings?

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. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.

Which map is live on test?

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

Join

What do you do to join test?

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

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2635,gmrust,cs168352,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168352
Build Game build reading: 168352.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code The region field is empty.

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.