Rust Data

rustdata.spaceservers89.34.97.220:28015.ipynb

Run all rust-data · live

‹ All servers

Online 89.34.97.220:28080 checked 8m ago

Coconut Cove Pve

moddedcarbon

Connect

srv = rust.server("89.34.97.220:28015")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 1 # peak 3
rank #3,814 # top 17%
last wipe 3d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
00.511.5222:0007:0016:0001:0010:0019:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020022:0007:0016:0001:0010:0019: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.

Rank · daily · 1 is best

srv.rank.plot(invert=True)  # 1 is best
RankRank in region
15k10k15k20k26 Sep2 Oct8 Oct15 Oct21 Oct27 Oct

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

Wipe schedule · no rhythm it keeps

srv.wipe_schedule()

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

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Sat 24 Oct, 15:47 UTC3d ago 3 NaN running 0
1 Fri 23 Oct, 17:42 UTC4d ago 3 NaN 0.9 days 1
2 Thu 22 Oct, 20:24 UTC5d ago 2 NaN 0.9 days 0
3 Wed 14 Oct, 19:30 UTC13d ago 2 held half 8 days 0
4 Tue 13 Oct, 19:41 UTC14d ago 2 NaN 1 days 1
5 Sun 4 Oct, 17:08 UTC23d ago 2 held half 9.1 days 1
6 Thu 1 Oct, 21:36 UTC FW25d 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.

display(srv.map, srv.info())

Map

4500 · seed 481981
Map of Coconut Cove Pve
map
Custom Map
size
4500
seed
481981

Server

srv.info()
address
89.34.97.220:28080
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
24 Oct 2026, 18:25 UTC
hostname
–
first seen
26 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 164 on average143/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average128/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 112 on average139/225
3RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average28/200
4404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 86 on average124/700
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average43/1000

Quick answers

From the figures on this page.

Population

What position does Coconut Cove Pve take in the server rankings?

Over the last seven days Coconut Cove Pve sits at #3,814 on player hours, in the top 17% of ranked servers.

What population does Coconut Cove Pve carry?

Coconut Cove Pve reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 1 players and peaked at 3. The 48-hour sample puts the busiest hour at 20:00 UTC, averaging 2 players.

Server data

How smoothly does Coconut Cove Pve run?

The 48-hour average is 98 server fps, with a low of 61. Entity numbers reached 88,364, and that includes buildings, deployables and the rest. The memory field tops out at 4,996 MB. What players call lag is these two fields together: low fps and a rising entity count.

Which Rust version is Coconut Cove Pve on?

Rust network protocol 2635 and build 168909 on Windows is what Coconut Cove Pve runs. Joining needs the same protocol on your game; Steam handles the update.

Is Coconut Cove Pve up, and what does its uptime show?

Coconut Cove Pve reports itself online at the current refresh. Count back 46 hours from its reported uptime to get the last restart. Uptime of 100% across the last 7 full days: 168 hours of 168. Its earliest recorded date in Rust Data is 26 September 2026.

Where does Coconut Cove Pve sit?

No region is published by Coconut Cove Pve. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 89.34.97.220:28080.

Settings and map

Which settings and rules does Coconut Cove Pve run?

No gather rate appears in the name: Coconut Cove Pve. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.

Which map has Coconut Cove Pve selected?

Coconut Cove Pve runs a procedural map of size 4,500 with seed 481981, generated by the game. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: Custom Map.

Wipes and dates

When does Coconut Cove Pve wipe, and how often?

No next wipe can be predicted for Coconut Cove Pve, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 3 days 2 hours ago.

On Coconut Cove Pve, what happens on wipe day?

Across recent wipes the busiest point averaged 3 players. The crowd on the latest wipe topped out 24 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.

Tags and filters

Which Rust Data filters and lists contain Coconut Cove Pve?

The Rust Data lists that Coconut Cove Pve fits are: Modded Rust servers. 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.

Which meanings do the tags on Coconut Cove Pve hold?

The game's server browser reads these tags from Coconut Cove Pve: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): Runs on Carbon for plugins. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.

Connecting

How can I connect to Coconut Cove Pve?

The manual route: launch Rust, F1, then client.connect 89.34.97.220:28080. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.

Server tags · what each one means

srv.tags.decode()

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

Game

gmrust
Game mode Survival play, standard Rust.
mp50
Max players 50 slots in total.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Build number: 168909.
ptrak
Networking Network traffic runs over RakNet, the game standard.
$r?
Region code No region code is set.

Mods and access

^z
Modded The Modded section lists it, because plugins or settings change the game.
^y
Carbon Runs on Carbon for plugins.

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.

Rust Data 77,057 players 11,838 servers online