RUST METRICSFlight deck · live data
Data live Servers11,832 Players65,657 Populated3,608 Fresh wipes 3 h129 Scan5 min
‹ All servers15.204.83.240:20003
Offline Full Queue Fresh wipe Wipe due No query

typical TEST

Offline 15.204.83.240:20003 checked 16d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 25 50 75 100 PAX 0 /100

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,702top 71%
Last wipe24d 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, measured since 4 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
15k10k15k20k4 Oct7 Oct10 Oct12 Oct15 Oct18 Oct

Top 71% 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

Wipe timing

What wipe timing does typical TEST follow?

To tell the rhythm of typical TEST, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 24 days 23 hours ago.

Tag meanings

How should you read the tags on typical TEST?

These are the tags typical TEST publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): 100 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167398 (Build): Game build reading: 167398; ptrak (Networking): Network layer: RakNet, the standard for the game; $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 typical TEST?

These Rust Metrics lists carry typical TEST: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

What position does typical TEST hold among Rust servers?

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

How full does typical TEST get?

typical TEST is not responding; status offline, last seen 16 days 2 hours ago.

Server

Where does typical TEST sit?

Reading: location. typical TEST gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 15.204.83.240:20003.

What Rust version is typical TEST on?

Version check: Rust network protocol 2634 and build 167398 on Linux, run by typical TEST. Check: protocol. To join, your game must match; Steam handles the update.

Is typical TEST up, and how often does it stay up?

Reading: offline. typical TEST last answered 16 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 4 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on typical TEST?

Reading the name gives no gather rate for typical TEST. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. VAC is on. That is Valve's anti-cheat.

What map is typical TEST on?

Size 1,000 and seed 6738: the game generates the procedural map on typical TEST from them. View it on RustMaps from this page: matching size and seed give an identical map.

Connection

What do you do to join typical TEST?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players 100 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167398
Build Game build reading: 167398.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.