RUST METRICSFlight deck · live data
Data live Servers11,814 Players74,934 Populated3,774 Fresh wipes 3 h145 Scan5 min
‹ All servers5.3.229.55:28015
Offline Full Queue Fresh wipe Wipe due No query

Test Server

Offline 5.3.229.55:28015 checked 35d ago

moddedcarbon
COM 1 · connect
Launch Rust and join

Server instruments

no direct query in 48 hours
0 12 25 38 50 PAX 1 /50

Players now

2% 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#14,455top 63%
Last wipe35d 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
15k10k15k20k21 Sep22 Sep24 Sep25 Sep27 Sep28 Sep

Top 63% 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.7 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Mon 21 SepMon 21 Sep
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
Mon 21 Sep, 20:58 UTC36d ago 1 – running 0
Mon 21 Sep, 05:19 UTC36d ago 1 – 0.7 days 1

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 should you expect from wipe day on Test Server?

The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 1 hours in.

When does Test Server wipe?

Its rhythm cannot be told from the wipes of Test Server 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 35 days 23 hours ago.

Tags

How should you read the tags on Test Server?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon from Test Server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Test Server?

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

Occupancy

Where does Test Server sit in the rankings?

Player hours over seven days put Test Server at #14,455, in the top 63% of all ranked servers.

How full does Test Server get?

Reading for Test Server: offline at this moment; last seen 35 days 23 hours ago.

Server

What location is Test Server hosted in?

Reading: location. Test Server gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 5.3.229.55:28015.

What Rust version is Test Server on?

Rust network protocol 2633 and build 164530 on Windows is the build Test Server runs. Matching protocol is required to join. Let Steam update your game.

How reliable is Test Server, and is it online now?

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

Map and rules

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

Reading the name gives no gather rate for Test Server. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Carbon. VAC is on. That is Valve's anti-cheat.

How to join

How can you get onto Test Server?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2633,gmrust,cs164530,ts8,^z,^y

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Protocol 2633: join only on the same game version.
cs164530
Build Build 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

Mods and access

^z
Modded Modded: plugins or settings depart from the stock game.
^y
Carbon Check: framework. 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.