Offline 104.28.250.152:28015 checked 15d ago
MixMods Test (carbon)
Connect
srv = rust.server("104.28.250.152: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 bestTop 71% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 13 Oct, 14:08 UTC15d ago | 0 | NaN | running | 0 |
| 1 | Mon 12 Oct, 09:29 UTC16d ago | 0 | NaN | 1.2 days | 0 |
| 2 | Sun 11 Oct, 07:04 UTC17d ago | 0 | NaN | 1.1 days | 2 |
| 3 | Fri 9 Oct, 00:51 UTC19d ago | 3 | NaN | 2.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
- 104.28.250.152:28015
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 13 Oct 2026, 14: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 · 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 · 115 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 · 88 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.
Population
What position does MixMods Test (carbon) take in the server rankings?
Rank #15,352 on seven-day player hours for MixMods Test (carbon), within the top 71% of all ranked servers.
What population does MixMods Test (carbon) carry?
The current row shows MixMods Test (carbon) offline; the last response was 15 days 6 hours ago.
Server data
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.
How reliable is MixMods Test (carbon), and is it online now?
Offline now for MixMods Test (carbon), last seen 15 days 6 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 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. 104.28.250.152:28015 is its address.
Settings and map
What rules and settings are recorded for MixMods Test (carbon)?
The name MixMods Test (carbon) carries no gather rate. Eight players per group: that is the game's default, and it applies here. survival is the game mode here, and gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has MixMods Test (carbon) selected?
A procedural map runs on MixMods Test (carbon), generated by the game.
Wipe data
When does MixMods Test (carbon) wipe, and on what schedule?
Irregular wipe times on MixMods Test (carbon) leave no next wipe to forecast. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. The world it runs now was generated 15 days 6 hours ago.
What is wipe day on MixMods Test (carbon) like?
The average peak over recent wipes is 0 players. Peak population on the latest wipe came 0 hours in.
Tags and filters
Where does MixMods Test (carbon) appear among Rust Data lists and filters?
On Rust Data, MixMods Test (carbon) appears in these lists: Modded Rust servers. These filters bring it up on the server list: 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): The server speaks protocol 2634, so match your game version; cs166652 (Build): Build number: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: 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
How can I connect to MixMods Test (carbon)?
In Rust, F1 opens the console: type client.connect 104.28.250.152:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.