Offline 200.112.18.220:28015 checked 25d ago
Cocoverse | X10
Connect
srv = rust.server("200.112.18.220:28017")
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. 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 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 200.112.18.220:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 17:23 UTC
- hostname
- –
- first seen
- 2 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Atlas - EU 10x | No BPs | Kits | Shop | EU · groups of 20+ · 10x · weekly · 349 on average | 131/150 |
| 1 | TemplarGaming 10x Swift Loot++|PvP|MyMini|SkinBox|x10 JUST WIPE | NA · groups of 8+ · 10x · weekly · 179 on average | 126/250 |
| 2 | Atlas - US 10x | No BPs | Kits | Shop | NA · groups of 30+ · 10x · weekly · 178 on average | 196/250 |
| 3 | KRAKEN | X10 | EU | KITS | RP | FPS+ | EU · groups of 14+ · 10x · weekly · 153 on average | 18/400 |
| 4 | HollowServers.co EU 10x No BPs [Loot++|Events|MyMini|Shop] | EU · groups of 8+ · 10x · biweekly · 77 on average | 25/150 |
| 5 | HollowServers.co AU 10x No BPs [Loot++|Events|MyMini|Shop] | OC · groups of 8+ · 10x · biweekly · 67 on average | 48/150 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does Cocoverse | X10 rank?
Over the last seven days Cocoverse | X10 sits at #15,971 on player hours, in the top 70% of ranked servers.
How full does Cocoverse | X10 run?
Cocoverse | X10 returns no live count at this refresh, having last been seen 25 days 22 hours ago.
Server facts
What Rust version does Cocoverse | X10 run?
Version Rust network protocol 2634 and build 166652 on Linux is reported by Cocoverse | X10. Steam updates your game for you, but the protocol must match to join.
How reliable is Cocoverse | X10, and is it up?
The latest sample has Cocoverse | X10 offline, with a last sighting 25 days 22 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 2 October 2026.
Where does Cocoverse | X10 sit?
For Cocoverse | X10, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 200.112.18.220:28015.
Rules, settings, map
Which rules apply on Cocoverse | X10, and what settings?
Gather sits at 10x, read from the server's own name: Cocoverse | X10. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Oxide plugins run on it. VAC, Valve's anti-cheat, is enabled.
Which map has Cocoverse | X10 selected?
A procedural map runs on Cocoverse | X10, generated by the game.
Wipe data
When does Cocoverse | X10 wipe, and on what schedule?
The record for Cocoverse | X10 holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 26 days 12 hours ago, and that is the one in play.
Tags, lists
Where does Cocoverse | X10 appear among Rust Data lists and filters?
These Rust Data lists include Cocoverse | X10: Modded Rust servers and 10x Rust servers: the live sample. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 10x.
How should you read the server tags on Cocoverse | X10?
The game's server browser reads these tags from Cocoverse | X10: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166652 (Build): The server runs build 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to Cocoverse | X10?
The manual route: launch Rust, F1, then client.connect 200.112.18.220:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.