Offline 136.148.219.110:28015 checked 13d ago
BizRust Carbon Dev
Connect
srv = rust.server("136.148.219.110: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 bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 15 Oct, 09:50 UTC13d ago | 1 | NaN | running | 1 |
| 1 | Wed 14 Oct, 12:00 UTC14d ago | 1 | NaN | 0.9 days | 0 |
| 2 | Mon 12 Oct, 20:30 UTC16d ago | 1 | NaN | 1.6 days | 1 |
| 3 | Mon 5 Oct, 14:06 UTC23d ago | 0 | NaN | 7.3 days | 0 |
# 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
- 136.148.219.110:28015
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Oct 2026, 09:50 UTC
- hostname
- –
- first seen
- 5 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 · 154 on average | 26/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 38/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 12/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 1/1000 |
Quick answers
From the figures on this page.
Population
What position does BizRust Carbon Dev take in the server rankings?
Player hours over seven days put BizRust Carbon Dev at #15,097, in the top 70% of the ranked set.
What population does BizRust Carbon Dev carry?
BizRust Carbon Dev returns no live count at this refresh, having last been seen 13 days 11 hours ago.
Server facts
What Rust version does BizRust Carbon Dev run?
The build is Rust network protocol 2634 and build 167781 on Windows, run by BizRust Carbon Dev. Joining needs the same protocol on your game; Steam handles the update.
How reliable is BizRust Carbon Dev, and is it online now?
Offline now for BizRust Carbon Dev, last seen 13 days 11 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 5 October 2026.
Which location does BizRust Carbon Dev run from?
No region is published by BizRust Carbon Dev. 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 136.148.219.110:28015.
Rules, settings, map
What rules and settings are recorded for BizRust Carbon Dev?
No gather rate appears in the name: BizRust Carbon Dev. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
Wipe data
When does BizRust Carbon Dev wipe, and how often?
Irregular wipe times on BizRust Carbon Dev leave no next wipe to forecast. 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 13 days 17 hours ago.
On BizRust Carbon Dev, what happens on wipe day?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 1 hours after it began.
Tags, lists
Which lists on Rust Data hold BizRust Carbon Dev, and which filters?
These Rust Data lists include BizRust Carbon Dev: 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 2 weeks.
Which meanings do the tags on BizRust Carbon Dev hold?
Read by the game's server browser, the tags BizRust Carbon Dev publishes are: gmrust (Game mode): Rust survival in its standard form; mp500 (Max players): The server lists 500 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon. 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 BizRust Carbon Dev?
In Rust, F1 opens the console: type client.connect 136.148.219.110:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.