Rust Data

rustdata.spaceservers85.190.162.229:12401.ipynb

Run all rust-data · live

‹ All servers

Offline 85.190.162.229:12400 checked 1d ago

MX Server

moddedoxide

Connect

srv = rust.server("85.190.162.229:12401")
print(srv.connect_command)

Right now

srv.summary()
players now 0/50 # 0% full
7-day average 0 # peak –
rank #15,339 # top 69%
last wipe 27d ago # no schedule published
next wipe 7d 20h # Thu 5 Nov, 19:00 UTC FW
display(Image(srv.banner))

Players

srv.players.plot(range="48h")
AveragePeak
0123423:0002:0004:0007:0009:0012:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
02.557.51023:0002:0004:0007:0009:0012:00

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, measured since 27 Sep. 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
RankRank in region
15k10k15k20k27 Sep3 Oct9 Oct16 Oct22 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule · force wipes only

srv.wipe_schedule()

Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. # The force wipe · high confidence

wipe-day peak2players, last three wipes

Coming wipes

inatkind
07d 20hThu 5 Nov, 19:00 UTCFW force wipe
135d 20hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 39 hours in.

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Thu 1 Oct, 17:59 UTC FW27d ago 2 NaN running 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

4000 · seed 1877915644
Map of MX Server
map
Procedural Map
size
4000
seed
1877915644
Open on RustMaps

Server

srv.info()
address
85.190.162.229:12400
region
–
max players
50
group limit
8, the default
wipe schedule
–
last wipe
1 Oct 2026, 17:59 UTC
hostname
–
first seen
27 Sep 2026

Similar servers · the same kind of game, then region, group limit, rate and wipes

rust.similar(srv).head(6)
serverlike_thisplayers
0ShockRust | Blue | NoLimitno group limit · 157 on average67/500
1МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average122/100
2RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 116 on average68/225
3404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 91 on average60/700
4RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average16/200
5404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average10/1000

Quick answers

From the figures on this page.

Player counts

How does MX Server compare in the rankings?

Rank #15,339 on seven-day player hours for MX Server, within the top 69% of all ranked servers.

How full does MX Server run?

The current row shows MX Server offline; the last response was 34 hours ago. Over the last seven days it averaged 0 players.

Server facts

How well does MX Server perform?

Averaged over 48 hours: 10 server fps, never under 10. The entity count peaked at 112,360, covering buildings, deployables and the rest of the world. A high of 2,444 MB of memory used. Low fps plus an entity count on the way up is the lag players report.

What Rust version does MX Server run?

The build is Rust network protocol 2635 and build 168909 on Windows, run by MX Server. Steam updates your game for you, but the protocol must match to join.

How reliable is MX Server, and is it up?

The latest sample has MX Server offline, with a last sighting 34 hours ago. Count back 7 hours from its reported uptime to get the last restart. Uptime of 93% across the last 7 full days: 157 hours of 168. The first row Rust Data holds for it is dated 27 September 2026.

In which location is MX Server hosted?

There is no region published for MX Server. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 85.190.162.229:12400.

Map and rules

What rules and settings are recorded for MX Server?

You will not find a gather rate in the string MX Server. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the base game, where you gather, build and raid. Combat and raiding between players: both allowed. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.

Which map has MX Server selected?

MX Server runs a procedural map of size 4,000 with seed 1877915644, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.

Wipe data

When does MX Server wipe, and how often?

A single wipe each month, the force wipe, is all MX Server does. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 27 days 4 hours ago.

What is wipe day on MX Server like?

Across recent wipes the busiest point averaged 2 players. Peak population on the latest wipe came 39 hours in.

Lists and tags

Which Rust Data filters and lists contain MX Server?

The Rust Data lists that MX Server fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

How should you read the server tags on MX Server?

The game's server browser reads these tags from MX Server: gmvanilla (Game mode): Survival in vanilla form; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. 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.

Join steps

What is the way to join MX Server?

Enter client.connect 85.190.162.229:12400 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection. You will find its website at https://www.carbonnetwork.net.

Server tags · what each one means

srv.tags.decode()

Published as mp50,ptrak,$r?,v2635,gmvanilla,cs168909,ts8,^o^z

Game

gmvanilla
Game mode Survival in vanilla form.
mp50
Max players The server lists 50 slots.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs168909
Build Recorded game build: 168909.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Runs on Oxide (uMod) for plugins.
^z
Modded Modded listing: the game is changed by plugins or settings.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Rust Data 58,600 players 11,758 servers online