Offline 77.191.248.95:28015 checked 27d ago
combatland staging
Connect
srv = rust.server("77.191.248.95: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 59% 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 | Thu 1 Oct, 13:07 UTC27d 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
- 77.191.248.95:28015
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 15:37 UTC
- hostname
- –
- first seen
- 1 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 · 553 on average | 361/500 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 217/300 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 294 on average | 36/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 293 on average | 28/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 273 on average | 61/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 252 on average | 82/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does combatland staging rank?
Player hours over seven days put combatland staging at #13,967, in the top 59% of the ranked set.
What population does combatland staging carry?
Offline now for combatland staging, with the last sample 27 days 5 hours ago.
Server data
What is the Rust version on combatland staging?
Version Rust network protocol 2634 and build 166493 on Windows is reported by combatland staging. Joining needs the same protocol on your game; Steam handles the update.
How reliable is combatland staging, and is it up?
Offline now for combatland staging, last seen 27 days 5 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 1 October 2026.
Where does combatland staging sit?
There is no region published for combatland staging. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 77.191.248.95:28015.
Rules, settings, map
Which settings and rules does combatland staging run?
No gather rate appears in the name: combatland staging. Eight players per group: that is the game's default, and it applies here. Recorded as survival, the base game, where you gather, build and raid. Raids and player combat are enabled. The server browser lists 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 schedule
When does combatland staging wipe, and on what schedule?
The record for combatland staging holds too few wipes to show a rhythm. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 27 days 7 hours ago.
On combatland staging, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags, lists
Which Rust Data filters and lists contain combatland staging?
These Rust Data lists include combatland staging: Rust community servers, unfiltered. 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.
Which meanings do the tags on combatland staging hold?
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): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166493 (Build): Recorded game build: 166493; ptrak (Networking): Standard network layer for Rust: RakNet; $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.
How to join
How can I connect to combatland staging?
In Rust, F1 opens the console: type client.connect 77.191.248.95:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.