Working its way up from the back of the class: #15,932 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
46/ 100
D
Slipped a little: down 1,129 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (D); standing 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 67% 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
HH_TGMR_SKserver_20260721 leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 49.109.124.132:28015.
How dependable is HH_TGMR_SKserver_20260721, and is it online at the moment?
The server is down: HH_TGMR_SKserver_20260721 is offline now, with the last sighting 31 days 21 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 27 September 2026.
On what Rust version does HH_TGMR_SKserver_20260721 sit?
The server HH_TGMR_SKserver_20260721 is on Rust network protocol 2633 and build 165217 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does HH_TGMR_SKserver_20260721 reset?
There are too few wipes on record for HH_TGMR_SKserver_20260721 to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 51 days 8 hours.
Population
Where does HH_TGMR_SKserver_20260721 place in the wider field of Rust servers?
In the top 67% of all ranked servers, HH_TGMR_SKserver_20260721 sits at #15,932 for player hours over the last seven days.
Is HH_TGMR_SKserver_20260721 a busy server?
HH_TGMR_SKserver_20260721 is offline at the moment; the last time it was seen was 31 days 21 hours ago.
Lists and filters
How should you read the tags on HH_TGMR_SKserver_20260721?
The game's browser takes its cue from the tags HH_TGMR_SKserver_20260721 has set: gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): Its slot count is 1; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): Join only if your game runs protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show HH_TGMR_SKserver_20260721?
Rust Server Score lists that include HH_TGMR_SKserver_20260721: Best community servers, graded. 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.
Map and rules
How is HH_TGMR_SKserver_20260721 set up, and what rules does it keep?
Nothing in the name of HH_TGMR_SKserver_20260721 states a gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
Which map is in play on HH_TGMR_SKserver_20260721?
The game generates a procedural map for HH_TGMR_SKserver_20260721.
How to join
How do you get onto HH_TGMR_SKserver_20260721?
To connect, start Rust, press F1, and type client.connect 49.109.124.132:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
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 playersIts slot count is 1.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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 momentum (D); standing is the one to work on (F).