Station XX-15549 · no signal
MixMods Test (carbon)
Offline 104.28.218.152:28015 checked 16d ago
- Players now
- 0/ 4
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,549
- top 71%
- Last wipe
- 16d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 4 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- usual gap
- 3.9 daysbetween real wipes
- wipe-day peak
- 1players, last three wipes
- crowd held
- 0%else halves by day 1
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Mon 12 Oct, 10:44 UTC16d ago | M0.0▼falling | 0 | – | running | 1 | |
| Thu 8 Oct, 12:54 UTC20d ago | M0.0■steady | 2 | halved by day 1 | 3.9 days | 2 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on MixMods Test (carbon)?
The map on MixMods Test (carbon) is procedural, produced by the game.
Which settings and rules apply on MixMods Test (carbon)?
No gather rate appears in the name of MixMods Test (carbon). Groups hold up to 8 players, which is the default for the game. survival is the game mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. The server browser lists it under Modded, where plugins or settings change the game. Carbon is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Live population
What is the current population on MixMods Test (carbon)?
MixMods Test (carbon) is not responding at this moment and is offline, last seen 16 days 8 hours ago.
How does MixMods Test (carbon) rank against other Rust servers?
Over the last seven days, MixMods Test (carbon) recorded enough player hours to reach #15,549 worldwide, placing it in the top 71% of all ranked servers.
Server facts
How reliably does MixMods Test (carbon) stay online?
No contact with MixMods Test (carbon) right now, and the last recorded contact was 16 days 8 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 7 October 2026 is when Rust Server Trends first recorded it.
Which region does MixMods Test (carbon) run from?
Nothing about a region comes from MixMods Test (carbon). Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 104.28.218.152:28015.
Which Rust version is MixMods Test (carbon) running?
Rust network protocol 2634 and build 166652 on Linux is what MixMods Test (carbon) runs. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on MixMods Test (carbon)?
On average, the busiest point of its recent wipes drew 1 players. 0 hours into the latest wipe, the crowd reached its peak. Half that peak was held until the next wipe in 0% of its recent wipes. By day 1 it fell below half in the wipes where it didn't hold.
On what timetable does MixMods Test (carbon) run its wipes?
On record so far are too few of MixMods Test (carbon)'s wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 16 days 8 hours is how long the current world has been running.
Lists and tags
What do the server tags on MixMods Test (carbon) mean?
The game's server browser reads the tags MixMods Test (carbon) publishes: gmrust (Game mode): The game mode is standard Rust survival; mp4 (Max players): The server has 4 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2634 (Protocol): Your game needs to be on protocol 2634 to join; cs166652 (Build): It runs game build 166652; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does MixMods Test (carbon) appear?
These Rust Server Trends lists include MixMods Test (carbon): Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Connecting
What steps get you onto MixMods Test (carbon)?
Enter client.connect 104.28.218.152:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.