RUST METRICSFlight deck · live data
Data live Servers11,661 Players51,383 Populated3,245 Fresh wipes 3 h92 Scan5 min
‹ All servers89.12.141.47:28015
Offline Full Queue Fresh wipe Wipe due No query

combatland staging

Offline 89.12.141.47:28015 checked 16d ago

COM 1 · connect

Server instruments

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

Players now

100% 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#13,570top 61%
Last wipe16d 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
15k10k15k20k11 Oct12 Oct14 Oct15 Oct17 Oct18 Oct

Top 61% 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 peak1players, 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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 11 Oct, 11:33 UTC16d ago 1 – running 1

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 combatland staging?

An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in.

How often does combatland staging wipe, and when?

To tell the rhythm of combatland staging, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 16 days 21 hours ago.

Tags

How should you read the tags on combatland staging?

These are the tags combatland staging publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166493 (Build): Build 166493; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does combatland staging appear in Rust Metrics lists and filters?

On Rust Metrics, combatland staging sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

Where does combatland staging sit in the rankings?

Player hours over seven days put combatland staging at #13,570, in the top 61% of all ranked servers.

How full does combatland staging get?

Status for combatland staging: offline. Last seen 16 days 16 hours ago.

Server

Which location does combatland staging run from?

No region tag on combatland staging. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 89.12.141.47:28015.

What Rust version is combatland staging on?

Reading: combatland staging, Rust network protocol 2634 and build 166493, Windows. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on combatland staging, and is it online?

Reading: offline. combatland staging last answered 16 days 16 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 11 October 2026, recorded by Rust Metrics.

Map and rules

What rules does combatland staging enforce, and what are its settings?

Reading the name gives no gather rate for combatland staging. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.

What map is combatland staging on?

Procedural map on combatland staging, made by the game's generator.

How to join

How do you connect to combatland staging?

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

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs166493
Build Build 166493.
ptrak
Networking This is RakNet, Rust's usual network layer.
$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.