Offline 89.12.141.47:28015 checked 16d ago
combatland staging
Connect
srv = rust.server("89.12.141.47:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 11 Oct, 11:33 UTC16d ago | 1 | NaN | 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 89.12.141.47:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 11 Oct 2026, 11:45 UTC
- hostname
- –
- first seen
- 11 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 527 on average | 259/350 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 331 on average | 22/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 329 on average | 35/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 128/200 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 279 on average | 46/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 264 on average | 48/100 |
Quick answers
From the figures on this page.
Population data
What position does combatland staging take in the server rankings?
Player hours over seven days put combatland staging at #13,570, in the top 61% of the ranked set.
How full does combatland staging run?
Offline now for combatland staging, with the last sample 16 days 9 hours ago.
Server facts
What Rust version does combatland staging run?
Rust network protocol 2634 and build 166493 on Windows is what combatland staging runs. The protocol has to match before you can join, and Steam does the updating.
Is combatland staging up, and what does its uptime show?
combatland staging is offline at this refresh; the last response came 16 days 9 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 11 October 2026.
In which location is combatland staging hosted?
There is no region published for combatland staging. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 89.12.141.47:28015.
Map and rules
What rules and settings are recorded for combatland staging?
No gather rate appears in the name: combatland staging. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. Anti-cheat status: VAC on.
What is the map on combatland staging?
combatland staging runs a procedural map, which the game generates.
Wipe data
When does combatland staging wipe, and on what schedule?
A rhythm cannot be read from the wipes of combatland staging on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. This world was created 16 days 14 hours ago.
What is wipe day on combatland staging like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Where does combatland staging appear among Rust Data lists and filters?
The Rust Data lists that combatland staging fits are: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the server tags on combatland staging?
Read by the game's server browser, the tags combatland staging publishes are: gmrust (Game mode): Rust survival in its standard form; mp1 (Max players): Slot count: 1; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166493 (Build): The server runs build 166493; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into combatland staging?
Enter client.connect 89.12.141.47:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.