RUST METRICSFlight deck · live data
Data live Servers11,722 Players55,260 Populated3,387 Fresh wipes 3 h137 Scan5 min
‹ All servers106.153.36.63:28015
Offline Full Queue Fresh wipe Wipe due No query

TEST Server

Offline 106.153.36.63:28015 checked 14d ago

COM 1 · connect

Server instruments

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

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#15,346top 71%
Last wipe14d agono schedule published
Next wipe–no rhythm it keeps
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 Sep7 Oct11 Oct16 Oct20 Oct

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

PLAN

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Tue 13 OctWed 7 OctWed 7 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 13 Oct, 15:09 UTC14d ago 0 – running 0
Wed 7 Oct, 10:46 UTC20d ago 1 – 6.2 days 0
Wed 7 Oct, 02:16 UTC20d ago 1 – 0.4 days 0
Mon 5 Oct, 04:47 UTC22d ago 1 – 1.9 days 1
Sun 13 Sep, 11:11 UTC44d ago 1 held half 21.7 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 schedule

What should you expect from wipe day on TEST Server?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

What wipe timing does TEST Server follow?

No next wipe can be predicted for TEST Server, which wipes at irregular times. 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 14 days 8 hours ago.

Tag meanings

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

Tags published by TEST Server, read by the game's server browser: 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): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set. 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 Server?

These Rust Metrics lists carry TEST Server: 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.

Occupancy

Where does TEST Server sit in the rankings?

Player hours over seven days put TEST Server at #15,346, in the top 71% of all ranked servers.

How full does TEST Server get?

Reading for TEST Server: offline at this moment; last seen 14 days 8 hours ago.

Operator and location

Where does TEST Server sit?

No region tag on TEST Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 106.153.36.63:28015.

What Rust version is TEST Server on?

Reading: TEST Server, Rust network protocol 2634 and build 167781, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

Check: connection. TEST Server is offline at this moment. Last contact was 14 days 8 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 13 September 2026.

Settings and map

How is TEST Server configured, and what rules are in force?

Check: gather rate. The name TEST Server does not state one. 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. Under Community in the server browser you will find it. VAC is off. That is Valve's anti-cheat.

Connection

How do you connect to TEST Server?

Check: join. Open Rust, press F1, then enter client.connect 106.153.36.63: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,cs167781,ts8

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 Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

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.