StatusLive Servers online11,711 Players58,911 Populated3,347 Wiped · 3 h176 Interval5 min Date29 OCT 2026

DWG RG-S4118Server sheetchecked 12m ago

Coconut Cove Pve

Online 89.34.97.220:28080 checked 12m ago

moddedcarbon
Connect
Players now 0/ 50 0% full
7-day average0peak 3
Rank#4,118top 19%
Last wipe4d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
00.511.5211:0020:0005:0014:0000:0009:00

Hourly average and peak, UTC.

Fig. 1Players on Coconut Cove Pve
Fig. 2

Server performance

05010015020011:0020:0005:0014:0000:0009:00

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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k26 Sep3 Oct9 Oct16 Oct22 Oct29 Oct

Top 19% of all ranked servers. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

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.9 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak3players, last three wipes
crowd held100%of its cycles kept half the crowd

The first 48 hours of its last wipes

Sat 24 OctFri 23 OctThu 22 Oct
01234+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 3, 24 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers 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 UTC6d 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 FW27d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 149 on average
146 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average
123 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 118 on average
188 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average
78 / 700
05
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average
10 / 200
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
20 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

Is Coconut Cove Pve online, and what uptime has been recorded?

Coconut Cove Pve is up at this moment. About 26 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. First seen by Rust Graphs on 26 September 2026.

How does Coconut Cove Pve perform, as measured?

The last 48 hours give an average of 79 server fps and a floor of 9. Counted at its highest: 154,894 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 5,245 MB. A climbing entity count and low fps are the source of what players feel as lag.

What location is recorded for Coconut Cove Pve?

A region is not published by Coconut Cove Pve. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. It is reached at 89.34.97.220:28080.

What Rust version is recorded for Coconut Cove Pve?

On Windows, Coconut Cove Pve runs Rust network protocol 2635 and build 168909. Steam updates your game, which must be on the same protocol for you to join.

Counts

What does the population history show for Coconut Cove Pve?

Current player count on Coconut Cove Pve: 0, of 50 slots. The seven-day mean is 0 players; the peak over the same period is 3. Averaged over the last 48 hours, the player count is highest at 23:00 UTC: 2 players.

Against other Rust servers, where is Coconut Cove Pve placed?

Player hours over seven days place Coconut Cove Pve at #4,118, within the top 19% of ranked servers.

Wipe data

What happens on Coconut Cove Pve on the day of a wipe?

At their busiest, its recent wipes drew 3 players on average. At 24 hours after the latest wipe the crowd was at its peak. The crowd stayed above half the peak until the next wipe in 100% of its recent wipes.

On Coconut Cove Pve, when do wipes occur?

Coconut Cove Pve wipes at times that follow no pattern, so no next wipe can be predicted. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The world it runs now was made 4 days 16 hours ago.

Settings

What settings and rules apply on Coconut Cove Pve?

The name of Coconut Cove Pve records no gather rate. Eight players per group: the default for the game. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. Plugins or settings change the game, and the browser lists it as Modded. The plugin count is Carbon. VAC is on: that is Valve's anti-cheat.

What is the map for Coconut Cove Pve?

Size 4,500 with seed 481981: that is the procedural map Coconut Cove Pve runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. The name of the map reads: Custom Map.

Tags

On Rust Graphs, which lists and filters contain Coconut Cove Pve?

These Rust Graphs lists include Coconut Cove Pve: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.

Which meaning is attached to each tag on Coconut Cove Pve?

gmrust (Game mode): Standard survival, as Rust plays; mp50 (Max players): The slot count is 50; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): The plugin framework is Carbon are the tags Coconut Cove Pve publishes; the game's server browser reads them. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.

Joining the server

How is Coconut Cove Pve joined?

In Rust, press F1 and type client.connect 89.34.97.220:28080 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Standard survival, as Rust plays.
mp50
Max players The slot count is 50.
ts8
Group limit The team limit is 8, which is the game default.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build Build: 168909.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code No region code is recorded.

Mods and access

^z
Modded The game is changed by plugins or settings; the listing is Modded.
^y
Carbon The plugin framework is Carbon.

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.

KeyTag string decoded