Rust Server TrendsSeismic network · station log
Recording Stations11,866 Players94,541 Active3,878 Wipes · 3 h396 48 h

Station EU-12874 · no signal

CobaltCove.io Testing Branch

Offline EU 138.201.33.101:38015 checked 14d ago

biweekly wipes moddedoxidepve
Connect
Players now
1/ ?
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#12,874
top 60% · #2424 in EU
Last wipe
14d ago
biweekly schedule
Next wipe
7d 3h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station EU-12874 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of ? slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep24 Sep11 Oct15 Oct18 Oct22 Oct

Top 60% of all ranked servers, top 82% in EU. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 3h. The force wipe · high confidence

usual gap
3.3 daysbetween real wipes
on rhythm
33%of its recent wipes
wipe-day peak
1players, last three wipes

Coming wipes

  1. 7d 3hThu 5 Nov, 19:00 UTCFW
  2. 13d 22hThu 12 Nov, 14:48 UTC
  3. 27d 22hThu 26 Nov, 14:48 UTC
  4. 35d 3hThu 3 Dec, 19:00 UTCFW
  5. 41d 22hThu 10 Dec, 14:48 UTC

The first 48 hours of its last wipes

Thu 15 OctTue 13 OctSat 10 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Thu 15 Oct, 14:48 UTC14d ago M0.0rising 1 – running 0
Tue 13 Oct, 15:07 UTC16d ago M0.0rising 1 – 2 days 0
Sat 10 Oct, 07:36 UTC19d ago M0.0steady 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. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo EU · no group limit · biweekly · 243 on average
279/ 2000
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 EU · groups of 30+ · biweekly · 49 on average
68/ 100
RustAria#4 [Мирный / PVE / SKINDROPS] EU · groups of 100+ · biweekly · 28 on average
21/ 200
[EU/US] RustyWasteland PVE | Halloween Contest | Zombies | Raid EU · groups of 10+ · biweekly · 26 on average
20/ 100
[ESP] TIESOLAND PVE | SKILLS | EVENTOS | HOME EU · groups of 8+ · biweekly · 26 on average
18/ 50
PvE Rust-Z {х1-х5} Quest/Eco/Zombie/Events EU · groups of 8+ · biweekly · 23 on average
56/ 100
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on CobaltCove.io Testing Branch?

CobaltCove.io Testing Branch runs a procedural map of size 4,500 with seed 124032105, produced by the game. Size and seed produce the same map, so RustMaps can show it from this page.

Which settings and rules apply on CobaltCove.io Testing Branch?

You will find no gather rate in the name of CobaltCove.io Testing Branch. 10 players is the most a group can hold. pve is the game mode, no player-versus-player fighting. The server browser lists it under Modded, where plugins or settings change the game. Its plugins are run through Oxide. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on CobaltCove.io Testing Branch?

A reading taken now finds CobaltCove.io Testing Branch offline; the most recent activity was 14 days ago.

How does CobaltCove.io Testing Branch rank against other Rust servers?

The last seven days of player hours place CobaltCove.io Testing Branch at #12,874, in the top 60% of all ranked servers and #2,424 in Europe.

Server facts

How reliably does CobaltCove.io Testing Branch stay online?

No contact with CobaltCove.io Testing Branch right now, and the last recorded contact was 14 days ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. Its earliest appearance in the records of Rust Server Trends dates to 17 September 2026.

Which region does CobaltCove.io Testing Branch run from?

The EU tag is how CobaltCove.io Testing Branch lists itself in Europe. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 138.201.33.101:38015 is the address it uses.

What build of Rust does CobaltCove.io Testing Branch use?

CobaltCove.io Testing Branch is running Rust network protocol 2634 and build 167781 on a machine with Windows. The protocol must match for you to join, and Steam takes care of updating it.

Wipe schedule

What does wipe day look like on CobaltCove.io Testing Branch?

On average, the busiest point of its recent wipes drew 1 players. 1 hours after the latest wipe, the crowd peaked.

How often does CobaltCove.io Testing Branch wipe, and on which days?

Its schedule cannot be confirmed, as too few of CobaltCove.io Testing Branch's wipes are on record; the prediction follows its tag instead. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. It has run its current world for 14 days 1 hours. Its tags state that it wipes every two weeks.

Tags

What do the server tags on CobaltCove.io Testing Branch mean?

The game's server browser reads the tags CobaltCove.io Testing Branch publishes: gmrust (Game mode): Survival in standard Rust; mp0 (Max players): Slots: 0; ts10 (Group limit): Each team can hold up to 10; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs167781 (Build): It runs game build 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^b (Biweekly): The wipe cycle is two weeks; ^p (PvE): There's no player combat; the world provides the threat; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EU (Europe): The server browser files it under Europe. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does CobaltCove.io Testing Branch appear?

You will find CobaltCove.io Testing Branch on the following Rust Server Trends lists: EU Rust servers, Modded Rust servers, tracked 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.

Which person or group runs CobaltCove.io Testing Branch?

Both CobaltCove.io Testing Branch and 2 other servers we track publish a cobaltcove.io hostname, so the same operator most likely runs them.

How to join

What steps get you onto CobaltCove.io Testing Branch?

To join, enter client.connect 138.201.33.101:38015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you. You can find its website at https://cobaltcove.io.

Instrument codes

Server tags

what each one means

Published as mp0,ptrak,$r?,v2634,^b,EU,^p,gmrust,cs167781,ts10,^o^z

Game

gmrust
Game mode Survival in standard Rust.
mp0
Max players Slots: 0.
ts10
Group limit Each team can hold up to 10.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs167781
Build It runs game build 167781.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code The server has no region code.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Gameplay

^p
PvE There's no player combat; the world provides the threat.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), runs here.
^z
Modded The game is changed by plugins or settings, placing it under Modded.

Region

EU
Europe The server browser files it under Europe.

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.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.