RUST METRICSFlight deck · live data
Data live Servers11,696 Players45,884 Populated3,156 Fresh wipes 3 h101 Scan5 min
‹ All servers9.244.16.170:28019
Offline Full Queue Fresh wipe Wipe due No query

typical test2

Offline 9.244.16.170:28019 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,398no region published
Last wipe39d 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
15k10k15k20k20 Sep21 Sep22 Sep24 Sep25 Sep26 Sep
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

How often does typical test2 wipe, and when?

Its rhythm cannot be told from the wipes of typical test2 on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 39 days 18 hours ago.

Tags

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

Check: tags. The game's server browser reads 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): Match the game version: protocol 2633 is required; cs164530 (Build): Build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty from typical test2. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

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

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

Occupancy

Where does typical test2 sit in the rankings?

Ranking for typical test2: #15,398 on seven-day player hours, top – of all ranked servers.

What player count does typical test2 carry?

typical test2 is not responding; status offline, last seen 39 days 18 hours ago.

Operator and location

Which location does typical test2 run from?

No region comes from typical test2. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 9.244.16.170:28019.

What Rust version is typical test2 on?

Rust network protocol 2633 and build 164530 on Linux is the build typical test2 runs. To get in, your game needs the same protocol; Steam applies the update.

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

Check: connection. typical test2 is offline at this moment. Last contact was 39 days 18 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 19 September 2026.

Settings and map

What settings and rules apply on typical test2?

Reading the name gives no gather rate for typical test2. No limit is set beyond the default. Groups take up to 8 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is typical test2 on?

Procedural map on typical test2, made by the game's generator.

Connection

How do you connect to typical test2?

Check: join. Open Rust, press F1, then enter client.connect 9.244.16.170:28019. 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 Match the game version: protocol 2633 is required.
cs164530
Build Build 164530.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.