Offline 104.28.218.151:28015 checked 15d ago
MixMods Test (carbon)
Connect
srv = rust.server("104.28.218.151:28016")
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 12 Oct, 09:08 UTC15d ago | 0 | NaN | running | 0 |
| 1 | Fri 9 Oct, 02:02 UTC18d ago | 3 | halved by day 1 | 3.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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 104.28.218.151:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 12 Oct 2026, 09:08 UTC
- hostname
- –
- first seen
- 7 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 | 119/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 112 on average | 119/225 |
| 3 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 27/200 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 86 on average | 114/700 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 34/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does MixMods Test (carbon) rank?
Rank #15,544 on seven-day player hours for MixMods Test (carbon), within the top 71% of all ranked servers.
How many players does MixMods Test (carbon) hold at once?
MixMods Test (carbon) returns no live count at this refresh, having last been seen 15 days 12 hours ago.
About the server
What is the Rust version on MixMods Test (carbon)?
The build is Rust network protocol 2634 and build 166652 on Linux, run by MixMods Test (carbon). Joining needs the same protocol on your game; Steam handles the update.
Is MixMods Test (carbon) up, and what does its uptime show?
The latest sample has MixMods Test (carbon) offline, with a last sighting 15 days 12 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 7 October 2026.
Where does MixMods Test (carbon) sit?
There is no region published for MixMods Test (carbon). The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 104.28.218.151:28015.
Settings and map
Which settings and rules does MixMods Test (carbon) run?
The name MixMods Test (carbon) carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Carbon plugins run on it. Anti-cheat status: VAC on.
Which map has MixMods Test (carbon) loaded?
MixMods Test (carbon) runs a procedural map, which the game generates.
Wipe schedule
On what schedule does MixMods Test (carbon) wipe?
The record for MixMods Test (carbon) holds too few wipes to show a rhythm. 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 15 days 12 hours ago.
On MixMods Test (carbon), what happens on wipe day?
Across recent wipes the busiest point averaged 2 players. The crowd on the latest wipe topped out 0 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. The drop under half arrived by day 1 in the other cases.
Tags and filters
Which lists on Rust Data hold MixMods Test (carbon), and which filters?
These Rust Data lists include MixMods Test (carbon): 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 MixMods Test (carbon)?
These tags are published by MixMods Test (carbon) and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): Slot count: 4; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): The server runs build 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $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. 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 to join MixMods Test (carbon)?
Enter client.connect 104.28.218.151:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.