Offline 5.178.138.150:28015 checked 7d ago
Carbon Test (CarbonServer1)
Connect
srv = rust.server("5.178.138.150: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 69% 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 20 Oct, 17:06 UTC8d ago | 1 | NaN | running | 0 |
| 1 | Thu 15 Oct, 09:04 UTC13d ago | 1 | held half | 5.3 days | 0 |
| 2 | Mon 5 Oct, 23:36 UTC23d ago | 1 | held half | 9.4 days | 0 |
| 3 | Sat 3 Oct, 07:37 UTC25d ago | 1 | held half | 2.7 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
- Launch island
- size
- –
- seed
- –
Server
srv.info()- address
- 5.178.138.150:28015
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 20 Oct 2026, 17:06 UTC
- hostname
- –
- first seen
- 2 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 · 150 on average | 72/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 100/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 35/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 5/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 7/1000 |
Quick answers
From the figures on this page.
Population
How does Carbon Test (CarbonServer1) compare in the rankings?
Player hours over seven days put Carbon Test (CarbonServer1) at #15,339, in the top 69% of the ranked set.
How many players does Carbon Test (CarbonServer1) hold at once?
Carbon Test (CarbonServer1) returns no live count at this refresh, having last been seen 7 days ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is Carbon Test (CarbonServer1) on?
Version Rust network protocol 2634 and build 167781 on Windows is reported by Carbon Test (CarbonServer1). Joining needs the same protocol on your game; Steam handles the update.
How reliable is Carbon Test (CarbonServer1), and is it up?
Carbon Test (CarbonServer1) is offline at this refresh; the last response came 7 days ago. 1 of 168 hours up over the last 7 full days, or 1%. The first row Rust Data holds for it is dated 2 October 2026.
In which location is Carbon Test (CarbonServer1) hosted?
For Carbon Test (CarbonServer1), no region is published. 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 5.178.138.150:28015.
Rules, settings, map
Which settings and rules does Carbon Test (CarbonServer1) run?
You will not find a gather rate in the string Carbon Test (CarbonServer1). The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Combat and raiding between players: both allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
Wipe data
When does Carbon Test (CarbonServer1) wipe, and on what schedule?
Irregular wipe times on Carbon Test (CarbonServer1) 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. A new world was started 8 days 14 hours ago, and that is the one in play.
What is wipe day on Carbon Test (CarbonServer1) like?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Tags and filters
Which Rust Data filters and lists contain Carbon Test (CarbonServer1)?
On Rust Data, Carbon Test (CarbonServer1) 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; Last wipe: In the last 2 weeks.
How should you read the server tags on Carbon Test (CarbonServer1)?
Read by the game's server browser, the tags Carbon Test (CarbonServer1) publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): 10 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): Modded listing: the game is changed by plugins or settings; ^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.
How to join
How can I connect to Carbon Test (CarbonServer1)?
The manual route: launch Rust, F1, then client.connect 5.178.138.150:28015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.