Working its way up from the back of the class: #12,874 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 930 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeak
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 60% of all ranked servers, top 82% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·····W·
·W·W···
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 29 October, 14:48 UTC, in 4h.
Its biweekly schedule tag · low confidence
usual gap3.3 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak1players, last three wipes
Coming wipes
4hThu 29 Oct, 14:48 UTC
7d 8hThu 5 Nov, 19:00 UTCFW
14d 4hThu 12 Nov, 14:48 UTC
28d 4hThu 26 Nov, 14:48 UTC
35d 8hThu 3 Dec, 19:00 UTCFW
42d 4hThu 10 Dec, 14:48 UTC
The first 48 hours of its last wipes
Thu 15 OctTue 13 OctSat 10 Oct
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 UTCFW27d 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
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is CobaltCove.io Testing Branch based in?
You'll see CobaltCove.io Testing Branch listed in Europe, tagged EU. Rust Server Score takes the server's word for its location and does not trace the hardware. 138.201.33.101:38015 is the address to use.
How dependable is CobaltCove.io Testing Branch, and is it online at the moment?
You cannot join now: CobaltCove.io Testing Branch is offline, last seen 13 days 19 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 17 September 2026.
On what Rust version does CobaltCove.io Testing Branch sit?
The server CobaltCove.io Testing Branch is on Rust network protocol 2634 and build 167781 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does CobaltCove.io Testing Branch wipe its map?
Too few wipes on CobaltCove.io Testing Branch are recorded to confirm the schedule, so its tag guides the prediction. It is due to wipe next on Thursday 29 October at 14:48 UTC. It has been running its current world for 13 days 19 hours. A fortnightly wipe schedule appears in its tags.
What happens on CobaltCove.io Testing Branch when wipe day arrives?
Recent wipes have peaked at 1 players on average. 1 hours after the latest wipe began, the crowd hit its peak.
Population
Where does CobaltCove.io Testing Branch sit among Rust servers?
In Europe, CobaltCove.io Testing Branch is #2,424, and overall it is #12,874 on player hours over the last seven days, in the top 60% of all ranked servers.
What does the population on CobaltCove.io Testing Branch look like?
CobaltCove.io Testing Branch is offline at the moment; the last time it was seen was 13 days 19 hours ago.
Tags and filters
What do CobaltCove.io Testing Branch's tags stand for?
The game's browser takes its cue from the tags CobaltCove.io Testing Branch has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp0 (Max players): Its slot count is 0; ts10 (Group limit): Teams cap out at 10; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): This runs on build 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; EU (Europe): In the server browser it appears under Europe. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Who is behind CobaltCove.io Testing Branch?
2 other servers we track also use a cobaltcove.io hostname, so they and CobaltCove.io Testing Branch most likely share an operator.
Which lists and filters on Rust Server Score show CobaltCove.io Testing Branch?
These Rust Server Score lists count CobaltCove.io Testing Branch among them: European Rust servers, graded, Modded Rust servers, graded and Rust PvE servers, graded. 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.
Rules and settings
How is CobaltCove.io Testing Branch set up, and what rules does it keep?
You will find no gather rate in the name of CobaltCove.io Testing Branch. A group here can reach 10 players. pve is the mode here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
CobaltCove.io Testing Branch runs which map?
A procedural map of size 4,500 and seed 124032105, generated by the game, is what CobaltCove.io Testing Branch runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
How to join
How should you connect to CobaltCove.io Testing Branch?
To connect, start Rust, press F1, and type client.connect 138.201.33.101:38015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://cobaltcove.io.
Server tags
what each one means
Published asmp0,ptrak,$r?,v2634,^b,EU,^p,gmrust,cs167781,ts10,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp0
Max playersIts slot count is 0.
ts10
Group limitTeams cap out at 10.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
EU
EuropeIn the server browser it appears 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.
A term to build on. Even marks across the subjects, from F to D.