Offline 169.0.232.208:28025 checked 22d ago
Carbon Test
Connect
srv = rust.server("169.0.232.208:28027")
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 71% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 5 Oct, 14:09 UTC22d ago | 0 | NaN | running | 0 |
| 1 | Mon 5 Oct, 07:45 UTC22d ago | 0 | NaN | 0.3 days | 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
- 169.0.232.208:28025
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 18:46 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 · 164 on average | 160/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 129/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 112 on average | 136/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 28/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 86 on average | 148/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 46/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Carbon Test rank?
Rank #15,966 on seven-day player hours for Carbon Test, within the top 71% of all ranked servers.
What population does Carbon Test carry?
Carbon Test returns no live count at this refresh, having last been seen 22 days 3 hours ago.
About the server
Which Rust version is Carbon Test on?
The build is Rust network protocol 2634 and build 166652 on Windows, run by Carbon Test. Steam updates your game for you, but the protocol must match to join.
How reliable is Carbon Test, and is it up?
The latest sample has Carbon Test offline, with a last sighting 22 days 3 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 4 October 2026.
In which location is Carbon Test hosted?
No region is published by Carbon Test. 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 169.0.232.208:28025.
Map and rules
What rules and settings are recorded for Carbon Test?
No gather rate appears in the name: Carbon Test. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: 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. Anti-cheat status: VAC on.
Which map has Carbon Test loaded?
Carbon Test runs a procedural map, which the game generates.
Wipe data
When does Carbon Test wipe, and on what schedule?
A rhythm cannot be read from the wipes of Carbon Test on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 23 days 2 hours ago.
What is wipe day on Carbon Test like?
Recent wipes averaged 0 players at their peak. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does Carbon Test appear among Rust Data lists and filters?
On Rust Data, Carbon Test 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 Carbon Test?
Read by the game's server browser, the tags Carbon Test publishes are: gmrust (Game mode): Rust survival in its standard form; mp5 (Max players): Slot count: 5; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^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.
Connecting
What is the way to join Carbon Test?
In Rust, F1 opens the console: type client.connect 169.0.232.208:28025. Launch Rust on this page does the same by opening the game through Steam and connecting.