Coconut Cove Pve
Online 89.34.97.220:28080 checked 12m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server performance
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, measured since 26 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Li4Rank
daily · 1 is bestTop 18% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 24 hours in.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 24 Oct, 15:47 UTC3d ago | 3° | – | running | 0 |
| Fri 23 Oct, 17:42 UTC4d ago | 3° | – | 0.9 days | 1 |
| Thu 22 Oct, 20:24 UTC5d ago | 2° | – | 0.9 days | 0 |
| Wed 14 Oct, 19:30 UTC13d ago | 2° | held half | 8 days | 0 |
| Tue 13 Oct, 19:41 UTC14d ago | 2° | – | 1 days | 1 |
| Sun 4 Oct, 17:08 UTC23d ago | 2° | held half | 9.1 days | 1 |
| Thu 1 Oct, 21:36 UTC FW26d ago | 2° | held half | 2.8 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What does wipe day look like on Coconut Cove Pve?
Its recent wipes drew an average peak of 3 players. 24 hours into the latest wipe, player numbers topped out. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.
What is the wipe schedule on Coconut Cove Pve?
No next wipe can be predicted: Coconut Cove Pve wipes when it chooses, at irregular times. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world it runs now dates from 3 days 10 hours ago.
Population
How busy is Coconut Cove Pve?
Coconut Cove Pve currently has 0 of its 50 slots filled. A seven-day average of 1 players, with a peak of 3. Look at 20:00 UTC for the last 48 hours: that hour averaged 2 players.
How does Coconut Cove Pve rank against other Rust servers?
Ranked #3,915 on seven-day player hours, Coconut Cove Pve is in the top 18% of all ranked servers.
Settings and rules
Which map does Coconut Cove Pve run?
The map on Coconut Cove Pve is procedural, size 4,500 with seed 481981, generated by the game. You can look at the map on RustMaps from this page: the same size and seed give the same map. You play on a map named Custom Map.
What are the rules and settings on Coconut Cove Pve?
The name Coconut Cove Pve does not specify a gather rate. Groups can contain up to 8 players, the default in the game. The server runs survival, gather, build and raid in the standard game. Combat between players and raiding are both possible. In the server browser it is Modded, meaning plugins or settings modify the game. Carbon plugins run on this server. The server has VAC, Valve's anti-cheat, turned on.
Location and uptime
Which version of Rust does Coconut Cove Pve run?
Rust network protocol 2635 and build 168909 on Windows is what Coconut Cove Pve runs. Steam updates your game for you, and the protocol has to match for you to join.
Is Coconut Cove Pve online, and how reliable is it?
Online now: Coconut Cove Pve. About 2 days 6 hours ago is when it last restarted, by its own uptime figure. It was up 168 of 168 hours across the last 7 full days, or 100% of the time. Rust Heatmap has had it on record since 26 September 2026.
Where is Coconut Cove Pve located?
A region is not published for Coconut Cove Pve. A server says where it is, and Rust Heatmap shows that. The machine's actual location is not looked up. 89.34.97.220:28080 is its address.
Does Coconut Cove Pve run smoothly?
It averaged 97 server fps over the last 48 hours, with a low of 70. Buildings, deployables and the rest of the world came to as much as 88,364 entities. At its peak it held 5,245 MB of memory. Lag, as players experience it, comes from low fps and a rising entity count.
Tags
Which Rust Heatmap lists and filters include Coconut Cove Pve?
Modded Rust servers, by live population are the Rust Heatmap lists that Coconut Cove Pve fits. These are the filters that return it on the list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
What do the server tags on Coconut Cove Pve mean?
These are the tags Coconut Cove Pve publishes for the game's server browser to read: gmrust (Game mode): Survival in the standard Rust form; mp50 (Max players): The slot count is 50; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): The game build here is 168909; ptrak (Networking): Standard game networking here, which is RakNet; $r? (Region code): No region code is set; ^z (Modded): Settings or plugins alter the game, which puts it under Modded; ^y (Carbon): The plugin framework in use is Carbon. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
How to join
How do I join Coconut Cove Pve?
Press F1 in Rust to open the console, then enter client.connect 89.34.97.220:28080. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.