Rust Server TrendsSeismic network · station log
Recording Stations11,627 Players40,719 Active2,850 Wipes · 3 h124 48 h

Station XX-15929 · no signal

C03 beta marker

Offline 189.163.125.215:29115 checked 27d ago

Connect
Players now
0/ ?
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#15,929
top 70%
Last wipe
27d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-15929 · 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
0of ? 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. 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
15k10k15k20k2 Oct3 Oct5 Oct6 Oct8 Oct9 Oct

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

Expected events

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 peak
0players, 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.

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Fri 2 Oct, 19:43 UTC27d ago M0.0steady 0 – – running 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
Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 477 on average
47/ 250
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 321 on average
87/ 200
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 284 on average
184/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 279 on average
5/ 100
Rustoria.co - EU Main EU · groups of 16+ · weekly · 266 on average
253/ 300
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 258 on average
311/ 300
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on C03 beta marker?

A procedural map runs on C03 beta marker, generated by the game.

Which settings and rules apply on C03 beta marker?

You will find no gather rate in the name of C03 beta marker. The group limit is 8 players, the game's default. In survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. It is a community server, and the browser lists it under Community. VAC, Valve's anti-cheat, is switched on.

Player counts

What is the current population on C03 beta marker?

C03 beta marker is not responding at this moment and is offline, last seen 27 days 8 hours ago.

How does C03 beta marker rank against other Rust servers?

The last seven days of player hours place C03 beta marker at #15,929, in the top 70% of all ranked servers.

Server facts

How reliably does C03 beta marker stay online?

As recorded now, C03 beta marker is not reachable, the last contact having been 27 days 8 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 2 October 2026.

Which region does C03 beta marker run from?

No region is published by C03 beta marker. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 189.163.125.215:29115 is the address it uses.

Which Rust version is C03 beta marker running?

C03 beta marker is running Rust network protocol 2634 and build 166586 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.

Wipe pattern

What does wipe day look like on C03 beta marker?

The recent wipes averaged a busiest count of 0 players. 0 hours into the latest wipe, the crowd reached its peak.

On what timetable does C03 beta marker run its wipes?

Too few wipes of C03 beta marker are on record yet to show its rhythm. All Rust servers wipe at the force wipe each month, the next of which is Thursday 5 November at 19:00 UTC. It has run its current world for 27 days 8 hours.

Tags

What do the server tags on C03 beta marker mean?

The game's server browser reads the tags C03 beta marker publishes: gmrust (Game mode): Survival in standard Rust; mp0 (Max players): The server has 0 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166586 (Build): It runs game build 166586; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): A region code has not been set. 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 C03 beta marker appear?

These Rust Server Trends lists include C03 beta marker: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Join the server

What steps get you onto C03 beta marker?

You can connect by pressing F1 in Rust and typing client.connect 189.163.125.215:29115 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.

Instrument codes

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust.
mp0
Max players The server has 0 slots.
ts8
Group limit 8 per team is the default, and that's the limit here.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166586
Build It runs game build 166586.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code A region code has not been 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.

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.