Rust Data

rustdata.spaceservers157.85.95.221:27058.ipynb

Run all rust-data · live

‹ All servers

Online 157.85.95.221:27057 checked 9m ago

MOXESRUST | CUSTOM MAP | 2X | MAX 3

2x moddedoxide

Connect

srv = rust.server("157.85.95.221:27058")
print(srv.connect_command)

Right now

srv.summary()
players now 0/100 # 0% full
7-day average 0 # peak –
rank #15,269 # top 68%
last wipe 15d ago # no schedule published
next wipe – # no rhythm it keeps

Players

srv.players.plot(range="48h")
AveragePeak
0123421:0006:0015:0001:0010:0019:00

Hourly average and peak, UTC.

Server performance

srv.performance.plot(measure="fps", range="48h")
05010015020021:0006:0015:0001:0010:0019: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 5 Oct. 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
15k10k15k20k5 Oct10 Oct15 Oct19 Oct24 Oct29 Oct

Top 68% 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.

usual gap0.9 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

Wed 14 OctTue 13 OctMon 12 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

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

Wipes · newest first

srv.wipes.head(20)
wipedpeakcrowdlastedplayers_before
0 Wed 14 Oct, 15:45 UTC15d ago 2 NaN running 0
1 Tue 13 Oct, 08:11 UTC16d ago 1 NaN 1.3 days 0
2 Mon 12 Oct, 16:00 UTC17d ago 1 NaN 0.7 days 0
3 Sun 11 Oct, 20:24 UTC18d ago 1 NaN 0.8 days 0
4 Sun 11 Oct, 13:47 UTC18d ago 1 NaN 0.3 days 0
5 Sat 10 Oct, 15:10 UTC19d ago 1 NaN 0.9 days 0
6 Wed 7 Oct, 12:28 UTC22d ago 1 halved by day 2 3.1 days 0
7 Wed 7 Oct, 06:10 UTC22d ago 1 NaN 0.3 days 0
8 Mon 5 Oct, 18:52 UTC24d ago 1 NaN 1.5 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

1850 · seed 2147483647
Map of MOXESRUST | CUSTOM MAP | 2X | MAX 3
map
Custom Map
size
1850
seed
2147483647

Server

srv.info()
address
157.85.95.221:27057
region
–
max players
100
group limit
8, the default
wipe schedule
–
last wipe
14 Oct 2026, 15:45 UTC
hostname
–
first seen
5 Oct 2026

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

rust.similar(srv).head(6)
serverlike_thisplayers
0Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 819 on average633/750
1Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 611 on average1456/1575
2Atlas - US 2X Monthly | Vanilla+ | No BP WipesNA · groups of 16+ · 2x · monthly · 380 on average154/200
3EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob FrEU · groups of 50+ · 2x · monthly · 350 on average772/850
4Magic Rust #18 — Vanilla 2x | Baйп 28.10EU · groups of 150+ · 2x · weekly · 335 on average600/820
5MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10EU · groups of 300+ · 2x · weekly · 318 on average84/1000

Quick answers

From the figures on this page.

Player counts

How does MOXESRUST | CUSTOM MAP | 2X | MAX 3 compare in the rankings?

Player hours over seven days put MOXESRUST | CUSTOM MAP | 2X | MAX 3 at #15,269, in the top 68% of the ranked set.

How many players does MOXESRUST | CUSTOM MAP | 2X | MAX 3 hold at once?

MOXESRUST | CUSTOM MAP | 2X | MAX 3 reports 0 players at this refresh, with 100 slots configured. Over the last seven days it averaged 0 players.

About the server

What does performance look like on MOXESRUST | CUSTOM MAP | 2X | MAX 3?

The 48-hour average is 119 server fps, with a low of 116. Entity numbers reached 15,596, and that includes buildings, deployables and the rest. Memory peaked at 3,542 MB. Low fps plus an entity count on the way up is the lag players report.

What is the Rust version on MOXESRUST | CUSTOM MAP | 2X | MAX 3?

Rust network protocol 2635 and build 167781 on Linux is what MOXESRUST | CUSTOM MAP | 2X | MAX 3 runs. Joining needs the same protocol on your game; Steam handles the update.

How reliable is MOXESRUST | CUSTOM MAP | 2X | MAX 3, and is it up?

Online is the state at the latest refresh for MOXESRUST | CUSTOM MAP | 2X | MAX 3. Count back 3 days 8 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. Rust Data logged it first on 5 October 2026.

Which location does MOXESRUST | CUSTOM MAP | 2X | MAX 3 run from?

No region is published by MOXESRUST | CUSTOM MAP | 2X | MAX 3. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 157.85.95.221:27057.

Map and rules

What rules and settings are recorded for MOXESRUST | CUSTOM MAP | 2X | MAX 3?

2x gather is what the name states, and the name is MOXESRUST | CUSTOM MAP | 2X | MAX 3. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. 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. VAC is running: Valve's anti-cheat is on.

What is the map on MOXESRUST | CUSTOM MAP | 2X | MAX 3?

The game generates the map on MOXESRUST | CUSTOM MAP | 2X | MAX 3: procedural, size 1,850, seed 2147483647. Because size and seed determine the map, it can be viewed on RustMaps via this page. Recorded under map name: Custom Map.

Wipe data

On what schedule does MOXESRUST | CUSTOM MAP | 2X | MAX 3 wipe?

Irregular wipe times on MOXESRUST | CUSTOM MAP | 2X | MAX 3 leave no next wipe to forecast. 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 15 days 4 hours ago, and that is the one in play.

What is wipe day on MOXESRUST | CUSTOM MAP | 2X | MAX 3 like?

Recent wipes averaged 1 players at their peak. Peak population on the latest wipe came 19 hours in.

Tags, lists

Which Rust Data filters and lists contain MOXESRUST | CUSTOM MAP | 2X | MAX 3?

On Rust Data, MOXESRUST | CUSTOM MAP | 2X | MAX 3 appears in these lists: Modded Rust servers and 2x 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; Gather rate: 2x.

How should you read the server tags on MOXESRUST | CUSTOM MAP | 2X | MAX 3?

These tags are published by MOXESRUST | CUSTOM MAP | 2X | MAX 3 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): To join, your game must run protocol 2635; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.

How to join

What is the way to join MOXESRUST | CUSTOM MAP | 2X | MAX 3?

In Rust, F1 opens the console: type client.connect 157.85.95.221:27057. Launch Rust on this page does the same by opening the game through Steam and connecting.

Server tags · what each one means

srv.tags.decode()

Published as mp100,ptrak,$r?,v2635,gmrust,cs167781,ts8,^o^z

Game

gmrust
Game mode Rust survival in its standard form.
mp100
Max players Slot count: 100.
ts8
Group limit The default cap applies: 8 per team.
v2635
Protocol To join, your game must run protocol 2635.
cs167781
Build The server runs build 167781.
ptrak
Networking Standard network layer for Rust: RakNet.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide The plugin framework in use is Oxide (uMod).
^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 98,615 players 11,847 servers online