Working its way up from the back of the class: #11,541 on player hours.
Uptimehours on the list, last 48
6/ 100
F
Attendance needs work: on the list only 3 of the last 48 hours.
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
37/ 100
F
Slipped a little: down 3,048 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in population (C+); uptime 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.
AveragePeak
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 52% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
13 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W··W
·W·WWW·
····WW·
·······
WW·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 gap1.1 daysbetween real wipes
on rhythm38%of its recent wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Mon 26 OctSat 17 OctThu 15 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 45 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Mon 26 Oct, 02:52 UTC2d ago
1
–
running
0
Sat 17 Oct, 02:31 UTC11d ago
1
–
9 days
0
Thu 15 Oct, 22:27 UTC13d ago
1
–
1.2 days
1
Thu 15 Oct, 01:40 UTC14d ago
1
–
0.9 days
1
Tue 13 Oct, 23:20 UTC15d ago
1
–
1.1 days
1
Mon 12 Oct, 23:03 UTC16d ago
1
–
1 days
1
Sat 3 Oct, 06:32 UTC25d ago
1
✓ held half
9.7 days
1
Fri 2 Oct, 21:15 UTC26d ago
1
–
0.4 days
1
Fri 2 Oct, 03:16 UTC26d ago
1
–
0.7 days
1
Sat 26 Sep, 04:55 UTC32d ago
1
–
5.9 days
1
Fri 25 Sep, 22:38 UTC33d ago
1
–
0.3 days
1
Fri 25 Sep, 05:48 UTC33d ago
1
–
0.7 days
0
Thu 24 Sep, 01:03 UTC35d ago
1
–
1.2 days
1
Tue 22 Sep, 18:51 UTC36d ago
1
–
1.3 days
1
Sun 20 Sep, 20:48 UTC38d ago
1
–
1.9 days
1
Thu 17 Sep, 01:51 UTC42d ago
1
✓ held half
3.8 days
1
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.134: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 25 hours ago. It was up 2% of the time over the last 7 full days, 3 of 168 hours. On 16 September 2026, Rust Server Score saw it for the first time.
What Rust version is Hunter's Cove on?
Rust network protocol 2635 and build 168909 on Windows is what Hunter's Cove runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does Hunter's Cove wipe its map?
Hunter's Cove wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 2 days 23 hours have passed since this world was made.
What should you expect from wipe day on Hunter's Cove?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 45 hours after it began.
Player numbers
Where does Hunter's Cove sit among Rust servers?
Over the last seven days, Hunter's Cove has #11,541 for player hours, in the top 52% of all ranked servers.
Is Hunter's Cove a busy server?
The last sighting of Hunter's Cove was 25 hours ago, and it is offline right now. It peaked at 1 and averaged 1 players over the last seven days. The busiest time in the last 48 hours was 23:00 UTC, with an average of 1 players.
Tags and filters
What is meant by the tags on Hunter's Cove?
You'll see Hunter's Cove tagged with 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; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded 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.
Where does Hunter's Cove appear in the Rust Server Score lists and filters?
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.
Server rules
What settings and rules apply on Hunter's Cove?
The name of Hunter's Cove gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
How to join
What is the way to join Hunter's Cove?
To connect, start Rust, press F1, and type client.connect 79.127.254.134:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
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.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 term to build on. Strongest in population (C+); uptime is the one to work on (F).