RUST METRICSFlight deck · live data
Data live Servers11,619 Players41,711 Populated3,041 Fresh wipes 3 h92 Scan5 min
‹ All servers192.255.237.203:28015
Offline Full Queue Fresh wipe Wipe due No query

typical TEST

Offline 192.255.237.203:28015 checked 39d 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,490top 69%
Last wipe41d 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 18 Sep. 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 Sep22 Sep24 Sep26 Sep28 Sep30 Sep

Top 69% 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?

The rhythm of typical TEST's wipes cannot be told yet: too few 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 41 days ago.

Lists and filters

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

These are the tags typical TEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): Slots: 100; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Game build reading: 164530; 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.

Where does typical TEST appear in Rust Metrics lists and filters?

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

Occupancy

What position does typical TEST hold among Rust servers?

Ranking for typical TEST: #15,490 on seven-day player hours, top 69% of all ranked servers.

What is the population on typical TEST?

Status for typical TEST: offline. Last seen 39 days 3 hours ago.

Server

What location is typical TEST hosted in?

No region comes from typical TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 192.255.237.203:28015.

What Rust version is typical TEST on?

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

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

typical TEST reports offline. The last reading came 39 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 18 September 2026.

Map and rules

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

Reading the name gives no gather rate for typical TEST. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on typical TEST?

From seed 6738, the game generates the procedural map on typical TEST. Its size is 1,000. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto typical TEST?

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

PLACARDS

Server tags

what each one means

Published as mp100,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players Slots: 100.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs164530
Build Game build reading: 164530.
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.