Rust Server TrendsSeismic network · station log
Recording Stations11,636 Players31,247 Active2,768 Wipes · 3 h72 48 h

Station XX-4131 · recording

Coconut Cove Pve

Online 89.34.97.220:28080 checked 13m ago

moddedcarbon
Connect
Players now
0/ 50
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
0
peak 3
Rank
#4,131
top 19%
Last wipe
4d ago
no schedule published
Next wipe
–
no rhythm it keeps
Seismic record · station XX-4131 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 50 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
−1into Wed 01:00 UTC
Peak · 48 h
2most players in any hour
Channel 1 · calibrated

Players

AveragePeak
00.511.5206:0015:0000:0009:0019:0004:00

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

05010015020006:0015:0000:0009:0019:0004: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.

Channel 3 · rank movement

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.

Expected events

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 gap
1.9 daysbetween real wipes
on rhythm
0%of its recent wipes
wipe-day peak
3players, last three wipes
crowd held
100%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

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Sat 24 Oct, 15:47 UTC4d ago M0.5rising 3 – running 0
Fri 23 Oct, 17:42 UTC5d ago M0.3rising 3 – 0.9 days 1
Thu 22 Oct, 20:24 UTC6d ago M0.3rising 2 – 0.9 days 0
Wed 14 Oct, 19:30 UTC14d ago M0.3rising 2 held half 8 days 0
Tue 13 Oct, 19:41 UTC15d ago M0.0rising 2 – 1 days 1
Sun 4 Oct, 17:08 UTC24d ago M0.0rising 2 held half 9.1 days 1
Thu 1 Oct, 21:36 UTC FW27d ago M0.3rising 2 held half 2.8 days 0

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
ShockRust | Blue | NoLimit no group limit · 152 on average
43/ 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average
135/ 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 117 on average
48/ 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average
17/ 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average
1/ 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average
4/ 1000
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on Coconut Cove Pve?

Coconut Cove Pve runs a procedural map of size 4,500 with seed 481981, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page. You will find the map named Custom Map.

Which settings and rules apply on Coconut Cove Pve?

The name of Coconut Cove Pve gives no gather rate. The group limit is 8 players, the game's default. survival is the game mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. Carbon is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on Coconut Cove Pve?

0 of the 50 slots on Coconut Cove Pve are filled right now. Averaged across the last seven days the population was 0 players, reaching a peak of 3. The last 48 hours show their highest activity at 23:00 UTC, averaging 2 players.

How does Coconut Cove Pve rank against other Rust servers?

On player hours for the past week, Coconut Cove Pve sits at #4,131, which puts it inside the top 19% of every ranked server.

Server details

How reliably does Coconut Cove Pve stay online?

Right now, you can reach Coconut Cove Pve. The uptime it reports puts its last restart about 21 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. On 26 September 2026 it was recorded for the first time by Rust Server Trends.

How well does Coconut Cove Pve perform under load?

The 48-hour average is 86 server fps; 9 is the lowest observed. The world held up to 154,894 entities at its peak, buildings and deployables included. Its highest memory use was 5,245 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does Coconut Cove Pve run from?

Nothing about a region comes from Coconut Cove Pve. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 89.34.97.220:28080 is the address it uses.

What build of Rust does Coconut Cove Pve use?

On Windows, Coconut Cove Pve runs Rust network protocol 2635 and build 168909. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on Coconut Cove Pve?

The recent wipes averaged a busiest count of 3 players. 24 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

How often does Coconut Cove Pve wipe, and on which days?

No next wipe can be predicted for Coconut Cove Pve, which wipes at irregular times. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 4 days 11 hours.

Lists and tags

What do the server tags on Coconut Cove Pve mean?

These are the tags Coconut Cove Pve publishes for the browser to read: gmrust (Game mode): Survival in standard Rust; mp50 (Max players): 50 slots are available; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does Coconut Cove Pve appear?

You will find Coconut Cove Pve on the following Rust Server Trends lists: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.

How to join

How do you connect to Coconut Cove Pve?

You can connect by pressing F1 in Rust and typing client.connect 89.34.97.220:28080 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp50
Max players 50 slots are available.
ts8
Group limit Teams max out at 8, the default set by the game.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build It runs game build 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code No region code is set for this server.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.