On the class lists: C+ (67), with population over 48 hours and no performance mark.
Players now1/ 1100% full
7-day average1peak 1
Rank#9,451top 42%
Last wipe2d agono schedule published
Next wipe–no rhythm it keeps
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
70/ 100
B−
Draws a healthy crowd: 1 of 1 on average.
Standingrank on player hours
58/ 100
C−
Working its way up from the back of the class: #9,451 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
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
44/ 100
F
Slipped a little: down 1,176 places this week. Nothing a good wipe can't fix.
A steady term.
Strongest in wipe hold (A+); 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.
AveragePeakWipe
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 42% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
9 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
···WW··
·W·W···
·······
···W·W·
·W·····
W···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap2.1 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd
The first 48 hours of its last wipes
Mon 26 OctTue 20 OctSat 17 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 02:52 UTC2d ago
1
–
running
1
Tue 20 Oct, 02:54 UTC8d ago
1
✓ held half
6 days
1
Sat 17 Oct, 02:31 UTC11d ago
1
✓ held half
3 days
1
Thu 15 Oct, 22:27 UTC13d ago
1
–
1.2 days
1
Thu 1 Oct, 00:34 UTC28d ago
1
–
16.1 days
1
Tue 29 Sep, 22:54 UTC29d ago
1
–
1.1 days
1
Tue 29 Sep, 06:47 UTC29d ago
1
–
0.7 days
1
Fri 25 Sep, 05:48 UTC33d ago
–
–
4 days
1
Thu 24 Sep, 01:03 UTC35d ago
–
–
1.2 days
0
Sat 12 Sep, 02:23 UTC46d ago
–
–
11.9 days
0
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
Hunter's Cove leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 79.127.254.131:28015.
Is Hunter's Cove up, and how steady is its uptime?
At this moment, Hunter's Cove is offline; the last time it was seen was 2 days 21 hours ago. For the last 7 full days, it was up 7 of 168 hours, or 4% of the time. On 17 September 2026, Rust Server Score saw it for the first time.
What Rust version is Hunter's Cove on?
You will find Hunter's Cove on Rust network protocol 2635 and build 168909, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does Hunter's Cove wipe its map?
No next wipe can be predicted for Hunter's Cove, which wipes at irregular times. 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 2 days 23 hours.
What should you expect from wipe day on Hunter's Cove?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 1 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 100% of its recent wipes.
Population
Where does Hunter's Cove sit among Rust servers?
In the top 42% of all ranked servers, Hunter's Cove sits at #9,451 for player hours over the last seven days.
Is Hunter's Cove a busy server?
Hunter's Cove is offline at the moment; the last time it was seen was 2 days 21 hours ago. It peaked at 1 and averaged 1 players over the last seven days.
Lists and filters
How should you read the tags on Hunter's Cove?
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; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags Hunter's Cove publishes, and the game's server browser reads them. 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 Hunter's Cove?
These Rust Server Score lists count Hunter's Cove among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 3 days.
Rules and settings
How is Hunter's Cove set up, and what rules does it keep?
Nothing in the name of Hunter's Cove states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Connecting
How do you get onto Hunter's Cove?
Enter client.connect 79.127.254.131: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?,v2635,gmrust,cs168909,ts8,^o^z
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.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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 steady term. Strongest in wipe hold (A+); momentum is the one to work on (F).