Offline 176.115.149.159:28015 checked 4h ago
Combat Local - Carbon Dev
Connect
srv = rust.server("176.115.149.159: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 25% 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.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 21:20 UTC19h ago | NaN | NaN | running | 0 |
| 1 | Tue 27 Oct, 15:13 UTC1d ago | NaN | NaN | NaN | 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 176.115.149.159:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Oct 2026, 21:20 UTC
- hostname
- –
- first seen
- 24 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 | ShockRust | Blue | NoLimit | no group limit · 156 on average | 203/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 128/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 178/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 89 on average | 129/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 20/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 45/1000 |
Quick answers
From the figures on this page.
Population
What position does Combat Local - Carbon Dev take in the server rankings?
Player hours over seven days put Combat Local - Carbon Dev at #5,496, in the top 25% of the ranked set.
What population does Combat Local - Carbon Dev carry?
Combat Local - Carbon Dev returns no live count at this refresh, having last been seen 4 hours ago. Over the last seven days it averaged 1 players and peaked at 2. Peak hour in the last 48 hours: 15:00 UTC, mean 1 players.
Server facts
Which Rust version is Combat Local - Carbon Dev on?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Combat Local - Carbon Dev. The protocol has to match before you can join, and Steam does the updating.
Is Combat Local - Carbon Dev up, and what does its uptime show?
The latest sample has Combat Local - Carbon Dev offline, with a last sighting 4 hours ago. Uptime of 43% across the last 3 full days: 31 hours of 72. The first row Rust Data holds for it is dated 24 October 2026.
Where does Combat Local - Carbon Dev sit?
There is no region published for Combat Local - Carbon Dev. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 176.115.149.159:28015.
Settings and map
Which settings and rules does Combat Local - Carbon Dev run?
No gather rate appears in the name: Combat Local - Carbon Dev. 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. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Wipes and dates
When does Combat Local - Carbon Dev wipe, and on what schedule?
The record for Combat Local - Carbon Dev holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 19 hours ago.
Tags and filters
Where does Combat Local - Carbon Dev appear among Rust Data lists and filters?
On Rust Data, Combat Local - Carbon Dev appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.
Which meanings do the tags on Combat Local - Carbon Dev hold?
These tags are published by Combat Local - Carbon Dev and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
How can I connect to Combat Local - Carbon Dev?
The manual route: launch Rust, F1, then client.connect 176.115.149.159:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.