Working its way up from the back of the class: #14,514 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
29/ 100
F
Lost ground: down 6,083 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); momentum is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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.
Rank
daily · 1 is best
RankRank in region
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is HH_TGMR_SKserver_20260721 based in?
You'll find no region listed by HH_TGMR_SKserver_20260721. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 49.109.124.14:28015.
Is HH_TGMR_SKserver_20260721 up, and how steady is its uptime?
You cannot join now: HH_TGMR_SKserver_20260721 is offline, last seen 29 days 16 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 29 September 2026.
What Rust version is HH_TGMR_SKserver_20260721 on?
Rust network protocol 2633 and build 165217 on Windows is what HH_TGMR_SKserver_20260721 runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does HH_TGMR_SKserver_20260721 reset?
HH_TGMR_SKserver_20260721 has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 51 days 5 hours.
Population
Where does HH_TGMR_SKserver_20260721 sit among Rust servers?
Over the last seven days, HH_TGMR_SKserver_20260721 has #14,514 for player hours, in the top 61% of all ranked servers.
Is HH_TGMR_SKserver_20260721 a busy server?
HH_TGMR_SKserver_20260721 is offline at the moment; the last time it was seen was 29 days 16 hours ago.
Tags and filters
How should you read the tags on HH_TGMR_SKserver_20260721?
You'll see HH_TGMR_SKserver_20260721 tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): 1 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature HH_TGMR_SKserver_20260721?
These Rust Server Score lists count HH_TGMR_SKserver_20260721 among them: Best community servers, graded. You can find it under these server-list filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does HH_TGMR_SKserver_20260721 enforce, and what are its settings?
You will find no gather rate in the name of HH_TGMR_SKserver_20260721. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it under Community, as a community server. You are covered by VAC, Valve's anti-cheat.
HH_TGMR_SKserver_20260721 runs which map?
A procedural map, generated by the game, is what HH_TGMR_SKserver_20260721 runs.
Connecting
How do you get onto HH_TGMR_SKserver_20260721?
Enter client.connect 49.109.124.14:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max players1 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been 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.
A term to build on. Strongest in standing (F); momentum is the one to work on (F).