Rust Server TrendsSeismic network · station log
Recording Stations11,809 Players80,805 Active3,802 Wipes · 3 h104 48 h

Station XX-14450 · no signal

combatland staging

Offline 77.11.239.193:28015 checked 28d ago

Connect
Players now
1/ 1
100% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,450
top 60%
Last wipe
28d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-14450 · 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 1 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
15k10k15k20k29 Sep30 Sep2 Oct3 Oct5 Oct6 Oct

Top 60% 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
1players, last three wipes

The first 48 hours of its last wipes

00.250.50.751+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Tue 29 Sep, 17:08 UTC29d ago M0.0rising 1 – 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 · 552 on average
605/ 675
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
377/ 525
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 299 on average
47/ 250
Rustoria.co - EU Main EU · groups of 16+ · weekly · 298 on average
35/ 250
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 271 on average
137/ 200
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 254 on average
160/ 300
Readings, in words

Quick answers

from the figures on this page

Map and rules

Which map is running on combatland staging?

The map on combatland staging is procedural, produced by the game.

Which settings and rules apply on combatland staging?

No gather rate appears in the name of combatland staging. The group limit is 8 players, the game's default. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. It is a community server, and the browser lists it under Community. Anti-cheat is on: VAC, from Valve.

Player counts

How many players are recorded on combatland staging right now?

A reading taken now finds combatland staging offline; the most recent activity was 28 days 22 hours ago.

How does combatland staging rank against other Rust servers?

The last seven days of player hours place combatland staging at #14,450, in the top 60% of all ranked servers.

Server details

How reliably does combatland staging stay online?

As recorded now, combatland staging is not reachable, the last contact having been 28 days 22 hours 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 29 September 2026.

Which region does combatland staging run from?

A region is not published by combatland staging. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 77.11.239.193:28015.

Which Rust version is combatland staging running?

Rust network protocol 2634 and build 166257 on Windows is what combatland staging runs. The protocol must match for you to join, and Steam takes care of updating it.

Wipe pattern

What does wipe day look like on combatland staging?

On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 0 hours after the wipe.

How often does combatland staging wipe, and on which days?

The rhythm of combatland staging cannot yet be told: too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 28 days 22 hours is how long the current world has been running.

Tags

What do the server tags on combatland staging mean?

The game's server browser reads the tags combatland staging publishes: gmrust (Game mode): You'll find standard Rust survival here; mp1 (Max players): Slots: 1; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): To connect, your game must be on the same protocol, 2634; cs166257 (Build): The game build is 166257; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.

On which Rust Server Trends lists does combatland staging appear?

You will find combatland staging on the following Rust Server Trends lists: Rust community servers without the side modes. You will find it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

How to join

What steps get you onto combatland staging?

To join, enter client.connect 77.11.239.193:28015 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.

Instrument codes

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs166257,ts8

Game

gmrust
Game mode You'll find standard Rust survival here.
mp1
Max players Slots: 1.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol To connect, your game must be on the same protocol, 2634.
cs166257
Build The game build is 166257.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$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.