RUST METRICSFlight deck · live data
Data live Servers11,720 Players60,549 Populated3,378 Fresh wipes 3 h181 Scan5 min
‹ All servers31.59.125.121:28015
Offline Full Queue Fresh wipe Wipe due No query

Cobalt Test

Offline 31.59.125.121:28015 checked 28d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,514top 65%
Last wipe28d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

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. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k23 Sep26 Sep29 Sep1 Oct4 Oct7 Oct

Top 65% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap4 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Sun 27 SepWed 23 Sep
01234+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 27 Sep, 21:41 UTC31d ago 0 – running 0
Wed 23 Sep, 22:22 UTC35d ago 0 – 4 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What should you expect from wipe day on Cobalt Test?

The busiest point of its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

What wipe timing does Cobalt Test follow?

Its rhythm cannot be told from the wipes of Cobalt Test on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 28 days 15 hours ago the current world was made.

Tags

Which tags does Cobalt Test carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from Cobalt Test. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show Cobalt Test?

Rust Metrics lists featuring Cobalt Test: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player count

Where does Cobalt Test sit in the rankings?

Player hours over seven days put Cobalt Test at #15,514, in the top 65% of all ranked servers.

How full does Cobalt Test get?

Cobalt Test is not responding; status offline, last seen 28 days 13 hours ago.

Server

Where does Cobalt Test sit?

Reading: location. Cobalt Test gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 31.59.125.121:28015.

What Rust version is Cobalt Test on?

Rust network protocol 2633 and build 165217 on Windows is the build Cobalt Test runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Cobalt Test, and is it online now?

Check: connection. Cobalt Test is offline at this moment. Last contact was 28 days 13 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 23 September 2026, recorded by Rust Metrics.

Rules and settings

What rules does Cobalt Test enforce, and what are its settings?

Check: gather rate. The name Cobalt Test does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.

Which map is live on Cobalt Test?

The game generates a procedural map for Cobalt Test.

Join

What do you do to join Cobalt Test?

To join: start Rust, press F1 and type client.connect 31.59.125.121:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp10
Max players The server holds 10 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build Build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none set.

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.