Rust Server Analytics 95,534 players11,865 servers
All servers
Drill-through Server detail

MOXESRUST | CUSTOM MAP | 2X | MAX 3

Online 157.85.95.221:27057 checked 10m ago

Drill-through
FilterServeris MOXESRUST | CUSTOM MAP | 2X | MAX 3
Attributes
2x moddedoxide
Last refreshed
Players now 0/ 100
7-day average 0 peak –
Rank #15,341 top 69%
Last wipe 15d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
0123417:0002:0011:0020:0005:0014:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
05010015020017:0002:0011:0020:0005:0014: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
RankRank in region
15k10k15k20k5 Oct10 Oct15 Oct19 Oct24 Oct29 Oct

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

Wipe schedule

no rhythm it keeps

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
WipedPeakCrowdLastedPlayers before
Wed 14 Oct, 15:45 UTC15d ago 2 – running 0
Tue 13 Oct, 08:11 UTC16d ago 1 – 1.3 days 0
Mon 12 Oct, 16:00 UTC17d ago 1 – 0.7 days 0
Sun 11 Oct, 20:24 UTC17d ago 1 – 0.8 days 0
Sun 11 Oct, 13:47 UTC18d ago 1 – 0.3 days 0
Sat 10 Oct, 15:10 UTC19d ago 1 – 0.9 days 0
Wed 7 Oct, 12:28 UTC22d ago 1 halved by day 2 3.1 days 0
Wed 7 Oct, 06:10 UTC22d ago 1 – 0.3 days 0
Mon 5 Oct, 18:52 UTC23d ago 1 – 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 841 on average 774 / 800
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes EU · groups of 16+ · 2x · monthly · 617 on average 455 / 475
Atlas - US 2X Monthly | Vanilla+ | No BP Wipes NA · groups of 16+ · 2x · monthly · 377 on average 148 / 200
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr EU · groups of 50+ · 2x · monthly · 350 on average 665 / 685
Magic Rust #18 — Vanilla 2x | Baйп 28.10 EU · groups of 150+ · 2x · weekly · 333 on average 919 / 960
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10 EU · groups of 300+ · 2x · weekly · 317 on average 165 / 1000

Quick answers

from the figures on this page

Wipe data

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

The next wipe on MOXESRUST | CUSTOM MAP | 2X | MAX 3 cannot be predicted, because it wipes at irregular times. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. The world now in play was created 15 days ago.

Wipe day on MOXESRUST | CUSTOM MAP | 2X | MAX 3: what should you expect?

The average busiest count over recent wipes is 1 players. Peak population for the latest wipe came 19 hours after it began.

Server

Which location hosts MOXESRUST | CUSTOM MAP | 2X | MAX 3?

No region is published by MOXESRUST | CUSTOM MAP | 2X | MAX 3. Where a server says it is, that is what Rust Server Analytics shows, without looking up where the machine stands. The address of the server is 157.85.95.221:27057.

What Rust build does MOXESRUST | CUSTOM MAP | 2X | MAX 3 run?

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

What uptime does MOXESRUST | CUSTOM MAP | 2X | MAX 3 show, and is it up?

MOXESRUST | CUSTOM MAP | 2X | MAX 3 reports online at the current check. Its reported uptime indicates a restart roughly 3 days 3 hours ago. 99% uptime over the last 7 full days, equal to 167 of 168 hours. It entered Rust Server Analytics records on 5 October 2026.

Is performance on MOXESRUST | CUSTOM MAP | 2X | MAX 3 stable?

Over 48 hours the average held at 119 server fps, and the minimum was 116. At its highest the entity count was 15,596, including buildings, deployables and all else. Peak memory was 3,542 MB. A climbing entity count and low fps are the lag players perceive.

Tags

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

Tags from MOXESRUST | CUSTOM MAP | 2X | MAX 3, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp100 (Max players): Player slots: 100; ts8 (Group limit): Default team size of 8; v2635 (Protocol): Joining needs your game on protocol 2635; cs167781 (Build): The game build is 167781; ptrak (Networking): Network layer: RakNet, Rust's default; $r? (Region code): A region code is not set; ^o (Oxide): It runs Oxide (uMod) for plugins; ^z (Modded): Plugins or settings change the game, so it sits under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Where does MOXESRUST | CUSTOM MAP | 2X | MAX 3 appear across Rust Server Analytics's lists and filters?

The following Rust Server Analytics lists count MOXESRUST | CUSTOM MAP | 2X | MAX 3 among their servers: Rust servers with a 2x gather rate and Modded Rust servers: live data. It appears on the server list under the following filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.

Population

What position does MOXESRUST | CUSTOM MAP | 2X | MAX 3 hold in the server rankings?

The seven-day player-hours rank for MOXESRUST | CUSTOM MAP | 2X | MAX 3 is #15,341, inside the top 69% of all ranked servers.

What is the population of MOXESRUST | CUSTOM MAP | 2X | MAX 3?

MOXESRUST | CUSTOM MAP | 2X | MAX 3 holds 0 players of its 100 slots as of the latest update. The seven-day mean for this server is 0 players.

Map and rules

What are the settings on MOXESRUST | CUSTOM MAP | 2X | MAX 3, and its rules?

MOXESRUST | CUSTOM MAP | 2X | MAX 3 names a 2x gather rate. No custom group limit: 8 players is the standard. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. Plugins or settings modify the game, and it is listed as Modded. The plugin framework is Oxide. VAC, Valve's anti-cheat, is enabled.

The map on MOXESRUST | CUSTOM MAP | 2X | MAX 3: which one is it?

MOXESRUST | CUSTOM MAP | 2X | MAX 3 uses a procedural map of size 1,850 with seed 2147483647, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page. The map is called Custom Map.

Connection

How do you connect to MOXESRUST | CUSTOM MAP | 2X | MAX 3?

In the Rust console (F1), enter client.connect 157.85.95.221:27057. Launch Rust on this page also works, opening Rust through Steam and connecting you.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp100
Max players Player slots: 100.
ts8
Group limit Default team size of 8.
v2635
Protocol Joining needs your game on protocol 2635.
cs167781
Build The game build is 167781.
ptrak
Networking Network layer: RakNet, Rust's default.
$r?
Region code A region code is not set.

Mods and access

^o
Oxide It runs Oxide (uMod) for plugins.
^z
Modded Plugins or settings change the game, so it sits under Modded.

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.