RUST METRICSFlight deck · live data
Data live Servers11,686 Players34,939 Populated2,865 Fresh wipes 3 h97 Scan5 min
‹ All servers103.236.54.209:28015
Online Full Queue Fresh wipe Wipe due No query

TestServer

Online 103.236.54.209:28015 checked 9m ago

COM 1 · connect

Server instruments

last reading Thu 01:00 UTC
0 250 500 750 1000 PAX 0 /1,000

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS 248 SERVER FPS

Server fps

48 h low 224 · below 20 is lag, below 10 is bad
0 10 20 30 40 ENT 19,904 ×1000

Entities

48 h range 19,823–22,207 · memory 2,736 MB
1239 ET SINCE RESTART 14D 05H

Uptime

14 days 5 hours since its last restart, at the last reading
7-day average0peak –
Rank#15,358top 69%
Last wipe14d agono schedule published
Next wipe–no rhythm it keeps
Memory2,736MBat the last reading
REC 1

Players

AveragePeak
0123404:0013:0022:0006:0015:0001:00

Hourly average and peak, UTC.

REC 2

Server performance

010020030040004:0013:0022:0006:0015:0001:00

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, measured since 14 Oct. 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 Sep11 Oct15 Oct20 Oct24 Oct29 Oct

Top 69% 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 gap3.5 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Fri 16 OctWed 14 OctSun 11 Oct
01234+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
Fri 16 Oct, 08:36 UTC12d ago 0 – running 0
Wed 14 Oct, 19:15 UTC14d ago 0 – 1.6 days 0
Sun 11 Oct, 08:18 UTC17d ago 0 – 3.5 days 0
Wed 16 Sep, 19:41 UTC42d ago 0 – 24.5 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 timing

What happens on TestServer when wipe day comes?

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

When does TestServer wipe?

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

Lists and filters

How should you read the tags on TestServer?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1000 (Max players): 1,000 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set from TestServer. 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 TestServer?

Rust Metrics lists featuring TestServer: 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.

Player count

What position does TestServer hold among Rust servers?

Player hours over seven days put TestServer at #15,358, in the top 69% of all ranked servers.

What is the population on TestServer?

0 of 1,000 slots are filled on TestServer right now. A seven-day average of 0 players is the reading.

Operator and location

What location is TestServer hosted in?

No region comes from TestServer. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 103.236.54.209:28015.

What Rust version is TestServer on?

Rust network protocol 2633 and build 163794 on Linux is the build TestServer runs. Check: protocol. To join, your game must match; Steam handles the update.

How does TestServer perform?

Check: fps. Average 242 server fps over the last 48 hours, low of 224. Within range. Reading: 22,207 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 2,912 MB. What players call lag comes from low fps and an entity count on the rise.

How reliable is TestServer, and is it online now?

Check: connection. TestServer is online at this moment. Reading: uptime. About 14 days 5 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Check: first contact. Rust Metrics logged it on 14 September 2026.

Rules and settings

How is TestServer configured, and what rules are in force?

No gather rate appears in the name: TestServer. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

What map is TestServer on?

From seed 12345, the game generates the procedural map on TestServer. Its size is 2,300. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How do you connect to TestServer?

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

PLACARDS

Server tags

what each one means

Published as mp1000,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1000
Max players 1,000 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build Game build reading: 163794.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.