Offline 82.4.76.169:28115 checked 2d ago
carbon-compile-check
Connect
srv = rust.server("82.4.76.169:28116")
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
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 | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 82.4.76.169:28115
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 26 Oct 2026, 01:56 UTC
- hostname
- –
- first seen
- 26 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 · 157 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 127 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 183/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
Quick answers
From the figures on this page.
Player counts
What position does carbon-compile-check take in the server rankings?
Over the last seven days carbon-compile-check sits at #15,373 on player hours, in the top 69% of ranked servers.
How many players does carbon-compile-check hold at once?
carbon-compile-check returns no live count at this refresh, having last been seen 2 days 17 hours ago. Over the last seven days it averaged 0 players.
About the server
Which Rust version is carbon-compile-check on?
Rust network protocol 2635 and build 168909 on Linux is what carbon-compile-check runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is carbon-compile-check, and is it up?
The latest sample has carbon-compile-check offline, with a last sighting 2 days 17 hours ago. Over the last 1 full day the hours up number 0 of 24, 0%. Its earliest recorded date in Rust Data is 26 October 2026.
Where does carbon-compile-check sit?
No region is published by carbon-compile-check. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 82.4.76.169:28115 is its address.
Map and rules
Which settings and rules does carbon-compile-check run?
You will not find a gather rate in the string carbon-compile-check. 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. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. Anti-cheat status: VAC on.
Which map has carbon-compile-check loaded?
A procedural map runs on carbon-compile-check, generated by the game.
Wipes and dates
On what schedule does carbon-compile-check wipe?
A rhythm cannot be read from the wipes of carbon-compile-check 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. A new world was started 2 days 17 hours ago, and that is the one in play.
Lists and tags
Which lists on Rust Data hold carbon-compile-check, and which filters?
The Rust Data lists that carbon-compile-check fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the server tags on carbon-compile-check?
The game's server browser reads these tags from carbon-compile-check: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way to join carbon-compile-check?
The manual route: launch Rust, F1, then client.connect 82.4.76.169:28115. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.