Cocoverse | X10
Key statistics
the figures behind the quote- Players now
- 0/ 50 0% full
- Change · 24h
- ▪n/a no reading a day ago
- 7-day average
- 0 peak –
- Rank
- #15,997 top 71%
- Rank · 7d ago
- #14,416 ▼1581 places down
- Last wipe
- 11d ago no schedule published
- Next wipe
- – no wipe seen yet
- Group limit
- 8 8, the default
- Gather rate
- 10x read from the name
- Score
- 0 player hours, last seven days
- Map
- – Procedural Map
- First seen
- 3 Oct 2026 no hostname published
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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.
Similar servers
the same kind of game, then region, group limit, rate and wipes| # | Server | Last | Chg 24h | Players over the last 24 hours24h |
|---|---|---|---|---|
| 1 | Atlas - EU 10x | No BPs | Kits | ShopEU · groups of 20+ · 10x · weekly · 288 on average | 398/450 | ▼−71−15.1% | |
| 2 | TemplarGaming 10x Swift Loot++|PvP|MyMini|SkinBox|x10 JUST WIPENA · groups of 8+ · 10x · weekly · 189 on average | 74/200 | ▼−51−40.9% | |
| 3 | Atlas - US 10x | No BPs | Kits | ShopNA · groups of 30+ · 10x · weekly · 162 on average | 105/150 | ▲+22+25.7% | |
| 4 | KRAKEN | X10 | EU | KITS | RP | FPS+EU · groups of 14+ · 10x · weekly · 120 on average | 120/350 | ▼−32−21.3% | |
| 5 | [EU] HollowServers.co 10x No BPs [Loot++|Events|MyMini|Shop]EU · groups of 8+ · 10x · biweekly · 75 on average | 68/150 | ▼−8−9.9% | |
| 6 | Vitality - US 10x | No BPs | Kits | ShopNA · groups of 32+ · 10x · weekly · 71 on average | 10/50 | ▼−3−23.6% |
Quick answers
from the figures on this pageServer Rules
How is Cocoverse | X10 configured in terms of rules and settings?
A gather rate of 10x appears in the name of Cocoverse | X10. The default group size of 8 players applies here. survival is the mode, gather, build and raid in the standard game. Combat and raiding between players are allowed. In the server browser it appears under Modded, with plugins or settings that change the game. Plugin count: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is played on Cocoverse | X10?
Cocoverse | X10 uses a procedural map, which the game generates.
Population
Where does Cocoverse | X10 sit in the rankings?
For the last seven days, Cocoverse | X10 holds rank #15,997 on player hours, in the top 71% of all ranked servers.
What is the population on Cocoverse | X10?
Right now, Cocoverse | X10 is offline; the last sighting was 10 days 14 hours ago.
Wipe Schedule
How often does Cocoverse | X10 wipe?
The record holds too few of Cocoverse | X10's wipes to establish its rhythm. The monthly force wipe takes every Rust server. Next: Thursday 5 November at 19:00 UTC. 11 days 20 hours ago the current world was created.
Server Overview
What is the location of Cocoverse | X10?
No region is published by Cocoverse | X10. The location shown by Rust Analytics is the one a server states; it does not verify the machine's position. You can reach it at 200.112.27.210:28015.
What Rust version is Cocoverse | X10 running?
The version in use at Cocoverse | X10: Rust network protocol 2634 and build 166652, on Linux. Joining requires the same protocol on your game, which Steam updates.
How reliable is Cocoverse | X10 and is it currently online?
No response from Cocoverse | X10. It was last seen 10 days 14 hours ago. 0% is its uptime for the last 7 full days, 0 of 168 hours. First sighting by Rust Analytics: 3 October 2026.
Server Tags
How should you interpret the tags on Cocoverse | X10?
The game's server browser reads gmrust (Game mode): Survival in the standard Rust format; mp50 (Max players): Capacity: 50 slots; ts8 (Group limit): At the game default, teams hold up to 8; v2634 (Protocol): Protocol 2634: matching game versions are required to join; cs166652 (Build): It runs build 166652; ptrak (Networking): RakNet, the network layer the game ships with; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Categorised as Modded: plugins or settings alter gameplay, which Cocoverse | X10 publishes. Also in the tags and at the top of this page: current players, queue and world creation time.
Where does Cocoverse | X10 show up in Rust Analytics lists and filters?
These Rust Analytics lists include Cocoverse | X10: 10x Rust servers and Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks; Gather rate: 10x.
Connection
What steps do I take to join Cocoverse | X10?
The console route: start Rust, press F1, enter client.connect 200.112.27.210:28015. The page's Launch Rust button opens Rust through Steam and connects you instead.
Server tags
what each one meansPublished as mp50,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
mp50
ts8
v2634
cs166652
ptrak
$r?
Mods and access
^o
^z
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.