Working its way up from the back of the class: #15,775 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
42/ 100
F
Slipped a little: down 2,576 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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 66% 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 reports the location a server gives; it does not check where the machine actually is. You can connect at 49.109.125.116:28015.
How reliable is HH_TGMR_SKserver_20260721, and is it up?
At this moment, HH_TGMR_SKserver_20260721 is offline; the last time it was seen was 29 days 18 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 30 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 cycle
How frequently does HH_TGMR_SKserver_20260721 wipe its map?
There are too few wipes on record for HH_TGMR_SKserver_20260721 to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 51 days 20 hours.
Player numbers
Where does HH_TGMR_SKserver_20260721 sit among Rust servers?
Over the last seven days, HH_TGMR_SKserver_20260721 has #15,775 for player hours, in the top 66% of all ranked servers.
How many players does HH_TGMR_SKserver_20260721 usually have?
It has been 29 days 18 hours since HH_TGMR_SKserver_20260721 was last seen, and it is offline right now.
Lists and filters
What is meant by 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): This one runs plain Rust survival, with nothing altered; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here. 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 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. 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.
Server rules
What settings and rules apply on HH_TGMR_SKserver_20260721?
You will find no gather rate in the name of HH_TGMR_SKserver_20260721. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
Which map is in play on HH_TGMR_SKserver_20260721?
HH_TGMR_SKserver_20260721 runs a procedural map, which the game generates.
Connecting
What is the way to join HH_TGMR_SKserver_20260721?
To connect, start Rust, press F1, and type client.connect 49.109.125.116: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 modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$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. Even marks across the subjects, from F to F.