Offline 104.28.250.150:28025 checked 18d ago
MixMods Test (oxide)
Connect
srv = rust.server("104.28.250.150:28026")
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 62% 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 3, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 9 Oct, 02:16 UTC20d ago | 3 | NaN | running | 2 |
# 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.150:28025
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 7 Oct 2026, 09:41 UTC
- hostname
- –
- first seen
- 8 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 · 152 on average | 41/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 · 117 on average | 0/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 16/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 2/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 3/1000 |
Quick answers
From the figures on this page.
Population data
What position does MixMods Test (oxide) take in the server rankings?
Over the last seven days MixMods Test (oxide) sits at #13,618 on player hours, in the top 62% of ranked servers.
How full does MixMods Test (oxide) run?
The current row shows MixMods Test (oxide) offline; the last response was 18 days 16 hours ago.
About the server
Which Rust version is MixMods Test (oxide) on?
Version Rust network protocol 2634 and build 166652 on Linux is reported by MixMods Test (oxide). Steam updates your game for you, but the protocol must match to join.
How reliable is MixMods Test (oxide), and is it up?
Offline now for MixMods Test (oxide), last seen 18 days 16 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 8 October 2026.
Where does MixMods Test (oxide) sit?
No region is published by MixMods Test (oxide). Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 104.28.250.150:28025 is its address.
Rules, settings, map
What rules and settings are recorded for MixMods Test (oxide)?
You will not find a gather rate in the string MixMods Test (oxide). Eight players per group: that is the game's default, and it applies here. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has MixMods Test (oxide) selected?
MixMods Test (oxide) runs a procedural map, which the game generates.
Wipe data
When does MixMods Test (oxide) wipe, and how often?
The record for MixMods Test (oxide) holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. A new world was started 21 days 19 hours ago, and that is the one in play.
What is wipe day on MixMods Test (oxide) like?
Across recent wipes the busiest point averaged 3 players. 0 hours after the latest wipe, the crowd reached its peak.
Lists and tags
Where does MixMods Test (oxide) appear among Rust Data lists and filters?
The Rust Data lists that MixMods Test (oxide) fits are: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on MixMods Test (oxide) hold?
Read by the game's server browser, the tags MixMods Test (oxide) publishes are: gmrust (Game mode): Survival play, standard Rust; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way to join MixMods Test (oxide)?
Enter client.connect 104.28.250.150:28025 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.