RUST METRICSFlight deck · live data
Data live Servers11,829 Players89,289 Populated4,008 Fresh wipes 3 h82 Scan5 min
‹ All servers49.109.127.175:28015
Offline Full Queue Fresh wipe Wipe due No query

HH_TGMR_SKserver_20260721

Offline 49.109.127.175:28015 checked 42d ago

COM 1 · connect

Server instruments

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

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#14,109no region published
Last wipe50d 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 Sep23 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?

The rhythm of HH_TGMR_SKserver_20260721's wipes cannot be told yet: too few 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 50 days 17 hours ago.

Tags

How should you read the tags on HH_TGMR_SKserver_20260721?

Tags published by HH_TGMR_SKserver_20260721, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does HH_TGMR_SKserver_20260721 appear in Rust Metrics lists and filters?

On Rust Metrics, HH_TGMR_SKserver_20260721 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.

Population

What position does HH_TGMR_SKserver_20260721 hold among Rust servers?

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

What is the population on HH_TGMR_SKserver_20260721?

Status for HH_TGMR_SKserver_20260721: offline. Last seen 42 days 3 hours ago.

Server

Where does HH_TGMR_SKserver_20260721 sit?

No region tag on HH_TGMR_SKserver_20260721. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 49.109.127.175:28015.

What Rust version is HH_TGMR_SKserver_20260721 on?

Version check: Rust network protocol 2633 and build 163794 on Windows, run by HH_TGMR_SKserver_20260721. To get in, your game needs the same protocol; Steam applies the update.

Is HH_TGMR_SKserver_20260721 up, and how often does it stay up?

Reading: offline. HH_TGMR_SKserver_20260721 last answered 42 days 3 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 16 September 2026.

Rules and settings

How is HH_TGMR_SKserver_20260721 configured, and what rules are in force?

Check: gather rate. The name HH_TGMR_SKserver_20260721 does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Community server. 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?

To join: start Rust, press F1 and type client.connect 49.109.127.175:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2633,gmrust,cs163794,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Build 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.