Server profile
Coconut Cove Pve
Online, with 0 of 50 players on; ranked #4,080 of every public Rust server, the top 18%. It last wiped 4d ago.
Online 89.34.97.220:28080 checked 3h ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 18% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
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.
The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 3, 24 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 24 Oct, 15:47 UTC4d ago | 3 | – | running | 0 |
| Fri 23 Oct, 17:42 UTC5d ago | 3 | – | 0.9 days | 1 |
| Thu 22 Oct, 20:24 UTC5d ago | 2 | – | 0.9 days | 0 |
| Wed 14 Oct, 19:30 UTC14d ago | 2 | held half | 8 days | 0 |
| Tue 13 Oct, 19:41 UTC15d ago | 2 | – | 1 days | 1 |
| Sun 4 Oct, 17:08 UTC24d ago | 2 | held half | 9.1 days | 1 |
| Thu 1 Oct, 21:36 UTC FW26d ago | 2 | held half | 2.8 days | 0 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe days
What does Coconut Cove Pve look like once wipe day arrives?
Recent wipes peaked at 3 players on average. 24 hours after the latest wipe, the crowd peaked. In 100% of recent wipes, more than half the peak was still playing at the next wipe.
When does Coconut Cove Pve wipe, and how often?
There is no next wipe to predict: Coconut Cove Pve wipes at irregular times. A force wipe falls on every Rust server once a month, and the next one is Thursday 5 November at 19:00 UTC. The world you are playing on now was made 4 days 1 hours ago.
About the server
Does Coconut Cove Pve hold a steady frame rate?
The 48-hour average for server fps is 96, and 44 was the lowest seen. At its highest the entity count reached 89,432: buildings, deployables and everything else. The highest memory figure was 5,245 MB. Lag, for players, is low fps and an entity count that keeps climbing.
Which Rust version is Coconut Cove Pve on?
The Rust build is network protocol 2635 and build 168909, running on Windows, for Coconut Cove Pve. The same protocol is required to join, and Steam takes care of updating it.
What does uptime look like for Coconut Cove Pve, and is it online?
At the time of this check Coconut Cove Pve is online. Going by the uptime figure it gives, its last restart was around 9 hours ago. The last 7 full days gave 168 of 168 hours up, or 100% of the time. The first record Rust Insights has of it is 26 September 2026.
Where does Coconut Cove Pve run from?
There is no region published for Coconut Cove Pve. Rust Insights reports the location a server declares, not the physical place of the machine. Connect through 89.34.97.220:28080.
Lists and tags
How should you read the tags listed for Coconut Cove Pve?
When the game's server browser reads Coconut Cove Pve, it finds these tags: gmrust (Game mode): Survival as standard Rust plays; mp50 (Max players): It holds 50 slots; ts8 (Group limit): This is the game default: 8 per team at most; v2635 (Protocol): Matching versions are required, and the protocol is 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it is filed under Modded; ^y (Carbon): The plugin framework here is Carbon. Current players, queue length and the age of the world sit in the tags as well, shown at the top of this page.
Which Rust Insights filters and lists feature Coconut Cove Pve?
These Rust Insights lists include Coconut Cove Pve: Modded Rust servers, explained. You will find it on the server list by applying these filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
Player counts
How many players are on Coconut Cove Pve right now, and how does that number move?
Coconut Cove Pve shows 0 players at the moment, against 50 slots. The seven-day average is 0 players, and the highest point in that week was 3. Its strongest hour in the past 48 was 21:00 UTC, with an average of 2 players.
Where does Coconut Cove Pve sit in the rankings?
Player hours over seven days put Coconut Cove Pve at #4,080, within the top 18% of the ranked field.
Settings and rules
What settings and rules apply on Coconut Cove Pve?
Nothing about gather rate is given in the name of Coconut Cove Pve. The default of 8 players per group is what applies here. You get survival as the game mode, the standard game: gather, build, raid. PvP and raiding are both enabled. Plugins or settings change the game, so it sits under Modded in the browser. It runs plugins, Carbon of them. VAC is on: Valve's anti-cheat is active.
What is the map on Coconut Cove Pve?
Size 4,500 and seed 481981 define the procedural map on Coconut Cove Pve, generated by the game. Size and seed give the same map each time, so this page lets you look at it on RustMaps. The name of its map reads: Custom Map.
How to join
How do you connect to Coconut Cove Pve?
Type client.connect 89.34.97.220:28080 into the console, which you open with F1 in Rust. The Launch Rust button on this page does the same job by opening Rust through Steam.