RUST METRICSFlight deck · live data
Data live Servers11,773 Players67,310 Populated3,523 Fresh wipes 3 h192 Scan5 min
‹ All servers49.109.126.47:28015
Offline Full Queue Fresh wipe Wipe due No query

HH_TGMR_SKserver_20260721

Offline 49.109.126.47:28015 checked 39d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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#13,265no region published
Last wipe51d 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 schedule

What wipe timing does HH_TGMR_SKserver_20260721 follow?

To tell the rhythm of HH_TGMR_SKserver_20260721, 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 51 days 10 hours ago.

Lists and filters

How should you read the tags on HH_TGMR_SKserver_20260721?

These are the tags HH_TGMR_SKserver_20260721 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs164530 (Build): The server runs game build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does HH_TGMR_SKserver_20260721 appear in Rust Metrics lists and filters?

These Rust Metrics lists carry HH_TGMR_SKserver_20260721: 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.

Population

What position does HH_TGMR_SKserver_20260721 hold among Rust servers?

Player hours over seven days put HH_TGMR_SKserver_20260721 at #13,265, in the top – of all ranked servers.

What is the population on HH_TGMR_SKserver_20260721?

HH_TGMR_SKserver_20260721 is not responding; status offline, last seen 39 days 19 hours ago.

Server details

Where does HH_TGMR_SKserver_20260721 sit?

No region tag on HH_TGMR_SKserver_20260721. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 49.109.126.47:28015.

What Rust version is HH_TGMR_SKserver_20260721 on?

Reading: HH_TGMR_SKserver_20260721, Rust network protocol 2633 and build 164530, Windows. To get in, your game needs the same protocol; Steam applies the update.

How reliable is HH_TGMR_SKserver_20260721, and is it online now?

HH_TGMR_SKserver_20260721 reports offline. The last reading came 39 days 19 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 19 September 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on HH_TGMR_SKserver_20260721?

Reading the name gives no gather rate for HH_TGMR_SKserver_20260721. 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. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

What map is HH_TGMR_SKserver_20260721 on?

Check: map. Procedural, generated by the game, on HH_TGMR_SKserver_20260721.

Connection

How do you connect to HH_TGMR_SKserver_20260721?

Press F1 in Rust and enter client.connect 49.109.126.47:28015. 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 mp1,ptrak,$r?,v2633,gmrust,cs164530,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs164530
Build The server runs game build 164530.
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.