RUST METRICSFlight deck · live data
Data live Servers11,668 Players33,864 Populated2,833 Fresh wipes 3 h84 Scan5 min
‹ All servers192.255.237.203:28017
Offline Full Queue Fresh wipe Wipe due No query

typical TEST

Offline 192.255.237.203:28017 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 wipe40d 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 schedule

What wipe timing does typical TEST follow?

To tell the rhythm of typical TEST, too few of its wipes are on record. 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 in play was created 40 days 22 hours ago.

Tags

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

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): The server runs game build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from typical TEST. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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

On Rust Metrics, typical TEST sits in these lists: 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,490, in the top 69% of all ranked servers.

What player count does typical TEST carry?

typical TEST is not responding; status offline, last seen 39 days 23 hours ago.

Server

What location is typical TEST hosted in?

No region comes from typical TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 192.255.237.203:28017.

What Rust version is typical TEST on?

Version check: Rust network protocol 2633 and build 164530 on Linux, run by typical TEST. To get in, your game needs the same protocol; Steam applies the update.

How reliable is typical TEST, and is it online now?

Reading: offline. typical TEST last answered 39 days 23 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 18 September 2026, recorded by Rust Metrics.

Map and rules

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

Reading the name gives no gather rate for typical TEST. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on typical TEST?

From seed 6738, the game generates the procedural map on typical TEST. Its size is 1,000. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How can you get onto typical TEST?

Press F1 in Rust and enter client.connect 192.255.237.203:28017. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp100
Max players The server holds 100 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs164530
Build The server runs game build 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.