RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h4 Scan5 min
‹ All servers9.244.18.186:30000
Offline Full Queue Fresh wipe Wipe due No query

typical TEST

Offline 9.244.18.186:30000 checked 32d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 10 20 30 40 PAX 0 /40

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#16,490top 71%
Last wipe33d 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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k25 Sep26 Sep28 Sep29 Sep1 Oct2 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 schedule

When does typical TEST wipe?

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 33 days 11 hours ago.

Lists and filters

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; mp40 (Max players): The server holds 40 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none 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. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does typical TEST sit in the rankings?

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

What player count does typical TEST carry?

Reading for typical TEST: offline at this moment; last seen 32 days 23 hours ago.

Operator and location

Which location does typical TEST run from?

Reading: location. typical TEST 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 9.244.18.186:30000.

What Rust version is typical TEST on?

Reading: typical TEST, Rust network protocol 2633 and build 165217, Linux. Matching protocol is required to join. Let Steam update your game.

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

Check: connection. typical TEST is offline at this moment. Last contact was 32 days 23 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 25 September 2026.

Settings and map

What rules does typical TEST enforce, and what are its settings?

No gather rate appears in the name: typical TEST. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

Which map is live on typical TEST?

Check: map. Procedural, generated by the game, on typical TEST.

How to join

How can you get onto typical TEST?

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

PLACARDS

Server tags

what each one means

Published as mp40,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp40
Max players The server holds 40 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build The server runs game build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none 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.