Offline 125.236.230.198:29025 checked 4d ago
gitsync-carbon
Connect
srv = rust.server("125.236.230.198:29125")
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
- 125.236.230.198:29025
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 22:40 UTC
- hostname
- –
- first seen
- 4 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 · 151 on average | 19/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 122 on average | 51/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 9/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 94 on average | 29/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 49/200 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does gitsync-carbon rank?
Rank #15,270 on seven-day player hours for gitsync-carbon, within the top 69% of all ranked servers.
How many players does gitsync-carbon hold at once?
Offline now for gitsync-carbon, with the last sample 4 days 23 hours ago. Over the last seven days it averaged 0 players.
About the server
What Rust version does gitsync-carbon run?
The build is Rust network protocol 2634 and build 166652 on Linux, run by gitsync-carbon. The protocol has to match before you can join, and Steam does the updating.
Is gitsync-carbon up, and what does its uptime show?
gitsync-carbon is offline at this refresh; the last response came 4 days 23 hours ago. Uptime of 1% across the last 7 full days: 1 hours of 168. Its earliest recorded date in Rust Data is 4 October 2026.
Where does gitsync-carbon sit?
For gitsync-carbon, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 125.236.230.198:29025 is its address.
Map and rules
Which rules apply on gitsync-carbon, and what settings?
You will not find a gather rate in the string gitsync-carbon. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has gitsync-carbon selected?
gitsync-carbon runs a procedural map, which the game generates.
Wipes and dates
On what schedule does gitsync-carbon wipe?
A rhythm cannot be read from the wipes of gitsync-carbon 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. The world it runs now was generated 26 days 5 hours ago.
Lists and tags
Which lists on Rust Data hold gitsync-carbon, and which filters?
On Rust Data, gitsync-carbon appears in these lists: 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.
How should you read the server tags on gitsync-carbon?
Read by the game's server browser, the tags gitsync-carbon publishes are: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): 2 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
How can I connect to gitsync-carbon?
The manual route: launch Rust, F1, then client.connect 125.236.230.198:29025. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.