Offline 151.243.93.160:28115 checked 25d ago
MixMods clean test (private)
Connect
srv = rust.server("151.243.93.160:28117")
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 59% 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 30, 12 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 10:45 UTC26d ago | 30 | NaN | running | 19 |
# 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
- 151.243.93.160:28115
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 10:45 UTC
- hostname
- –
- first seen
- 28 Sep 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 · 151 on average | 52/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 70/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 20/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 6/1000 |
Quick answers
From the figures on this page.
Player counts
How does MixMods clean test (private) compare in the rankings?
Rank #13,274 on seven-day player hours for MixMods clean test (private), within the top 59% of all ranked servers.
What population does MixMods clean test (private) carry?
MixMods clean test (private) returns no live count at this refresh, having last been seen 25 days 7 hours ago.
Server facts
Which Rust version is MixMods clean test (private) on?
Version Rust network protocol 2634 and build 166586 on Linux is reported by MixMods clean test (private). Steam updates your game for you, but the protocol must match to join.
Is MixMods clean test (private) up, and what does its uptime show?
MixMods clean test (private) is offline at this refresh; the last response came 25 days 7 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 28 September 2026.
In which location is MixMods clean test (private) hosted?
For MixMods clean test (private), no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 151.243.93.160:28115 is its address.
Map and rules
What rules and settings are recorded for MixMods clean test (private)?
The name MixMods clean test (private) carries no gather rate. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. VAC is running: Valve's anti-cheat is on.
Which map has MixMods clean test (private) selected?
A procedural map runs on MixMods clean test (private), generated by the game.
Wipe data
When does MixMods clean test (private) wipe, and on what schedule?
Too few wipes are on record for MixMods clean test (private) to reveal its rhythm. 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 26 days 19 hours ago, and that is the one in play.
What is wipe day on MixMods clean test (private) like?
Across recent wipes the busiest point averaged 30 players. 12 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Which Rust Data filters and lists contain MixMods clean test (private)?
These Rust Data lists include MixMods clean test (private): 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 clean test (private)?
Read by the game's server browser, the tags MixMods clean test (private) publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166586 (Build): Recorded game build: 166586; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not 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.
Join steps
How can I connect to MixMods clean test (private)?
In Rust, F1 opens the console: type client.connect 151.243.93.160:28115. Launch Rust on this page does the same by opening the game through Steam and connecting.