RUST METRICSFlight deck · live data
Data live Servers11,898 Players102,471 Populated3,963 Fresh wipes 3 h334 Scan5 min
‹ All servers189.163.125.215:29115
Offline Full Queue Fresh wipe Wipe due No query

C03 beta marker

Offline 189.163.125.215:29115 checked 26d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /?

Players now

no slots published 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,929top 70%
Last wipe26d 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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

Top 70% 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.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 19:43 UTC26d ago 0 – running 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 C03 beta marker?

At their busiest, its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does C03 beta marker wipe?

Its rhythm cannot be told from the wipes of C03 beta marker on record: there are too few. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. 26 days 22 hours ago the current world was made.

Lists and filters

How should you read the tags on C03 beta marker?

These are the tags C03 beta marker publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp0 (Max players): Slots: 0; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs166586 (Build): Build 166586; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show C03 beta marker?

On Rust Metrics, C03 beta marker sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Occupancy

Where does C03 beta marker sit in the rankings?

Ranking for C03 beta marker: #15,929 on seven-day player hours, top 70% of all ranked servers.

What is the population on C03 beta marker?

C03 beta marker is not responding; status offline, last seen 26 days 22 hours ago.

Server details

What location is C03 beta marker hosted in?

Reading: location. C03 beta marker gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 189.163.125.215:29115.

What Rust version is C03 beta marker on?

Reading: C03 beta marker, Rust network protocol 2634 and build 166586, Windows. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on C03 beta marker, and is it online?

C03 beta marker reports offline. The last reading came 26 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 2 October 2026.

Map and rules

How is C03 beta marker configured, and what rules are in force?

Reading the name gives no gather rate for C03 beta marker. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is C03 beta marker on?

The game generates a procedural map for C03 beta marker.

Join

How do you connect to C03 beta marker?

Press F1 in Rust and enter client.connect 189.163.125.215:29115. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2634,gmrust,cs166586,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp0
Max players Slots: 0.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs166586
Build Build 166586.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.