Rust Server TrendsSeismic network · station log
Recording Stations11,688 Players63,966 Active3,456 Wipes · 3 h119 48 h

Station XX-14560 · no signal

combatland staging

Offline 93.128.149.92:28015 checked 29d ago

Connect
Players now
1/ 1
100% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,560
top 61%
Last wipe
29d ago
no schedule published
Next wipe
–
too few wipes seen yet
Seismic record · station XX-14560 · 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
15k10k15k20k28 Sep29 Sep1 Oct2 Oct4 Oct5 Oct

Top 61% 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
Mon 28 Sep, 11:38 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 · 540 on average
637/ 675
Rustoria.co - EU East Long EU · groups of 12+ · monthly · 318 on average
386/ 425
Rustoria.co - EU Main EU · groups of 16+ · weekly · 312 on average
42/ 250
Rusty Moose |EU Main| EU · groups of 12+ · weekly · 311 on average
47/ 250
Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 272 on average
161/ 200
Rustafied.com - EU Friday EU · groups of 16+ · weekly · 265 on average
97/ 125
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on combatland staging?

A procedural map runs on combatland staging, generated by the game.

Which settings and rules apply on combatland staging?

The name of combatland staging gives no gather rate. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. Under Community in the server browser, it runs as a community server. VAC, Valve's anti-cheat, is switched on.

Live population

What is the current population on combatland staging?

No players are recorded on combatland staging at this moment; it is offline, and the last sighting was 29 days 11 hours ago.

How does combatland staging rank against other Rust servers?

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

Server details

How reliably does combatland staging stay online?

combatland staging is down at the moment; the last recorded contact was 29 days 11 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. On 28 September 2026 it was recorded for the first time by Rust Server Trends.

Which region does combatland staging run from?

No region is published by combatland staging. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 93.128.149.92:28015.

What build of Rust does combatland staging use?

On Windows, combatland staging runs Rust network protocol 2634 and build 166012. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

What does wipe day look like on combatland staging?

1 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 0 hours after the wipe.

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

On record so far are too few of combatland staging's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 29 days 23 hours.

Server tags

What do the server tags on combatland staging mean?

The game's server browser reads the tags combatland staging publishes: gmrust (Game mode): Survival in standard Rust; mp1 (Max players): Slots: 1; ts8 (Group limit): Teams max out at 8, the default set by the game; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166012 (Build): It runs game build 166012; 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 combatland staging appear?

The Rust Server Trends lists that take in combatland staging are: 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 combatland staging?

You can connect by pressing F1 in Rust and typing client.connect 93.128.149.92:28015 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 mp1,ptrak,$r?,v2634,gmrust,cs166012,ts8

Game

gmrust
Game mode Survival in standard Rust.
mp1
Max players Slots: 1.
ts8
Group limit Teams max out at 8, the default set by the game.
v2634
Protocol Your game needs to be on protocol 2634 to join.
cs166012
Build It runs game build 166012.
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.