RUST METRICSFlight deck · live data
Data live Servers11,604 Players34,824 Populated2,902 Fresh wipes 3 h66 Scan5 min
‹ All servers9.244.16.170:28021
Offline Full Queue Fresh wipe Wipe due No query

typical tst 3

Offline 9.244.16.170:28021 checked 38d 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 wipe38d agono schedule published
Next wipe–too few wipes 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

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 19 Sep, 06:13 UTC38d ago 0 – running 0

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 should you expect from wipe day on typical tst 3?

The busiest point of its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does typical tst 3 wipe?

Its rhythm cannot be told from the wipes of typical tst 3 on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 38 days 23 hours ago.

Tag meanings

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

Tags published by typical tst 3, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): The server runs game build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does typical tst 3 appear in Rust Metrics lists and filters?

On Rust Metrics, typical tst 3 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

What position does typical tst 3 hold among Rust servers?

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

What is the population on typical tst 3?

typical tst 3 is not responding; status offline, last seen 38 days 23 hours ago.

Server

What location is typical tst 3 hosted in?

No region comes from typical tst 3. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 9.244.16.170:28021.

What Rust version is typical tst 3 on?

Rust network protocol 2633 and build 164530 on Linux is the build typical tst 3 runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the uptime on typical tst 3, and is it online?

Reading: offline. typical tst 3 last answered 38 days 23 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.

Rules and settings

What settings and rules apply on typical tst 3?

Reading the name gives no gather rate for typical tst 3. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

What map is typical tst 3 on?

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

Join

What do you do to join typical tst 3?

Press F1 in Rust and enter client.connect 9.244.16.170:28021. 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 The game mode is plain Rust survival.
mp100
Max players The server holds 100 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build The server runs game build 164530.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.