RUST METRICSFlight deck · live data
Data live Servers11,755 Players63,128 Populated3,519 Fresh wipes 3 h136 Scan5 min
‹ All servers199.30.67.210:28015
Offline Full Queue Fresh wipe Wipe due No query

Typical 2X

Offline 199.30.67.210:28015 checked 32d ago

2x
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 19 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.

usual gap0.3 daysbetween real wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Sun 20 SepSat 19 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 20 Sep, 05:09 UTC37d ago 1 – running 0
Sat 19 Sep, 21:09 UTC38d ago 1 – 0.3 days 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 timing

What happens on Typical 2X when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours.

How often does Typical 2X wipe, and when?

To tell the rhythm of Typical 2X, 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 it runs now was made 37 days 17 hours ago.

Tag meanings

Which tags does Typical 2X carry, and what do they mean?

Tags published by Typical 2X, read by the game's server browser: 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): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Typical 2X appear in Rust Metrics lists and filters?

On Rust Metrics, Typical 2X sits in these lists: 2x Rust servers, checked live and 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; Gather rate: 2x.

Population

What position does Typical 2X hold among Rust servers?

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

How full does Typical 2X get?

Status for Typical 2X: offline. Last seen 32 days 16 hours ago.

Server

What location is Typical 2X hosted in?

No region comes from Typical 2X. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 199.30.67.210:28015.

What Rust version is Typical 2X on?

Reading: Typical 2X, Rust network protocol 2633 and build 165217, Linux. To get in, your game needs the same protocol; Steam applies the update.

Is Typical 2X up, and how often does it stay up?

Typical 2X reports offline. The last reading came 32 days 16 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 19 September 2026.

Map and rules

What settings and rules apply on Typical 2X?

The name carries the rate: 2x gather on Typical 2X. The group cap is 8 players, which is the default in the game. Mode check gives survival; gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

What map is Typical 2X on?

Size 3,500 and seed 1561417458: the game generates the procedural map on Typical 2X from them. The map repeats when size and seed match. Open it on RustMaps from this page.

How to join

What do you do to join Typical 2X?

Check: join. Open Rust, press F1, then enter client.connect 199.30.67.210:28015. 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 Your game must run protocol 2633 to get in.
cs165217
Build Game build reading: 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.