RUST METRICSFlight deck · live data
Data live Servers11,647 Players39,332 Populated2,956 Fresh wipes 3 h70 Scan5 min
‹ All servers199.30.67.210:28021
Offline Full Queue Fresh wipe Wipe due No query

Typical 3X

Offline 199.30.67.210:28021 checked 32d ago

3x
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#16,226top 71%
Last wipe37d 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, measured since 20 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 Sep25 Sep27 Sep30 Sep2 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

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 peak1players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 20 Sep, 07:35 UTC37d ago 1 – 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 3X?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 6 hours in.

How often does Typical 3X wipe, and when?

To tell the rhythm of Typical 3X, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 37 days 19 hours ago the current world was made.

Tag meanings

How should you read the tags on Typical 3X?

These are the tags Typical 3X 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): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Typical 3X?

On Rust Metrics, Typical 3X sits in these lists: 3x Rust servers, checked live and Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Gather rate: 3x.

Population

Where does Typical 3X sit in the rankings?

Player hours over seven days put Typical 3X at #16,226, in the top 71% of all ranked servers.

What is the population on Typical 3X?

Status for Typical 3X: offline. Last seen 32 days 20 hours ago.

Server

Which location does Typical 3X run from?

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

What Rust version is Typical 3X on?

Version check: Rust network protocol 2633 and build 165217 on Linux, run by Typical 3X. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Typical 3X, and is it online?

Check: connection. Typical 3X is offline at this moment. Last contact was 32 days 20 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.

Map and rules

What settings and rules apply on Typical 3X?

Gather rate check: 3x. That comes from the name Typical 3X. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.

Which map is live on Typical 3X?

From seed 6738, the game generates the procedural map on Typical 3X. Its size is 4,500. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How can you get onto Typical 3X?

Check: join. Open Rust, press F1, then enter client.connect 199.30.67.210:28021. 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,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp100
Max players Slots: 100.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build The server runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.