CobaltCove.io Testing Branch
Offline EU 138.201.33.101:38015 checked 13d ago
Server instruments
no direct query in 48 hoursPlayers now
no slots published 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 60% of all ranked servers, top 82% in EU. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 29 October, 14:48 UTC, in 57m. Its biweekly schedule tag · low confidence
Coming wipes
- WPT 1Thu 29 Oct, 14:48 UTC57m
- WPT 2Thu 5 Nov, 19:00 UTC7d 5hFW
- WPT 3Thu 12 Nov, 14:48 UTC14d 0h
- WPT 4Thu 26 Nov, 14:48 UTC28d 0h
- WPT 5Thu 3 Dec, 19:00 UTC35d 5hFW
- WPT 6Thu 10 Dec, 14:48 UTC42d 0h
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 15 Oct, 14:48 UTC13d ago | 1 | – | running | 0 |
| Tue 13 Oct, 15:07 UTC15d ago | 1 | – | 2 days | 0 |
| Sat 10 Oct, 07:36 UTC19d ago | 1 | – | 3.3 days | 1 |
| Thu 1 Oct, 18:51 UTC FW27d ago | – | – | 8.5 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 227/2000
- 54/100
- 21/200
- 25/100
- 6/50
- 1/?
Quick answers
from the figures on this pageWipe schedule
What should you expect from wipe day on CobaltCove.io Testing Branch?
At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 1 hours.
When does CobaltCove.io Testing Branch wipe?
Its tag guides the prediction: too few of CobaltCove.io Testing Branch's wipes are on record to confirm its schedule. Thursday 29 October at 14:48 UTC is when its next wipe is due. The world it runs now was made 13 days 23 hours ago. A wipe schedule of every two weeks is published in its tags.
Tags
Which tags does CobaltCove.io Testing Branch carry, and what do they mean?
Tags published by CobaltCove.io Testing Branch, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp0 (Max players): 0 slots in total; ts10 (Group limit): You may team up with at most 10; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^b (Biweekly): Two-week wipe schedule; ^p (PvE): There is no player-on-player combat here; the danger comes from the world; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server; EU (Europe): Europe is the browser category it sits in. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Who operates CobaltCove.io Testing Branch?
Check: operator. CobaltCove.io Testing Branch publishes a cobaltcove.io hostname, and 2 other servers we track do too. Same operator, most likely.
Which lists and filters on Rust Metrics show CobaltCove.io Testing Branch?
Rust Metrics lists featuring CobaltCove.io Testing Branch: EU Rust servers, checked, Modded Rust servers, checked live and Rust PvE servers. These filters bring it up on the server list: Region: Europe; Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
Population
What position does CobaltCove.io Testing Branch hold among Rust servers?
Player hours over the last seven days put CobaltCove.io Testing Branch at #12,874, #2,424 in Europe, in the top 60% of all ranked servers.
What player count does CobaltCove.io Testing Branch carry?
Status for CobaltCove.io Testing Branch: offline. Last seen 13 days 22 hours ago.
Server details
What location is CobaltCove.io Testing Branch hosted in?
Reading: location. The EU tag puts CobaltCove.io Testing Branch in Europe. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 138.201.33.101:38015.
What Rust version is CobaltCove.io Testing Branch on?
Reading: CobaltCove.io Testing Branch, Rust network protocol 2634 and build 167781, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is CobaltCove.io Testing Branch up, and how often does it stay up?
Reading: offline. CobaltCove.io Testing Branch last answered 13 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 17 September 2026, recorded by Rust Metrics.
Settings and map
What rules does CobaltCove.io Testing Branch enforce, and what are its settings?
Reading the name gives no gather rate for CobaltCove.io Testing Branch. Check: group limit. Up to 10 players. The mode is pve. Note the following: no combat against other players. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.
Which map is live on CobaltCove.io Testing Branch?
Size 4,500 and seed 124032105: the game generates the procedural map on CobaltCove.io Testing Branch from them. The map repeats when size and seed match. Open it on RustMaps from this page.
Connection
What do you do to join CobaltCove.io Testing Branch?
Check: join. Open Rust, press F1, then enter client.connect 138.201.33.101:38015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. You can find its website at https://cobaltcove.io.