Online 89.34.97.220:28080 checked 8m ago
Coconut Cove Pve
Connect
srv = rust.server("89.34.97.220:28015")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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
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.
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.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_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())
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 164 on average | 143/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 112 on average | 139/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 28/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 86 on average | 124/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 43/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.