Skip to the page
Rust TrackerRTRC · Radar control
ATIS RTRC INFO S SRV11,836online PAX72,948playing OCC3,667with players WIPED 3H218
MODModded traffic
Callsign

MXS15326=

MOXESRUST | CUSTOM MAP | 2X | MAX 3

Online 157.85.95.221:27057 checked 9m ago

2x moddedoxide
Clearance · join
Players now 0/ 100 0% full
7-day average0peak –
Rank#15,326top 69%
Last wipe14d agono schedule published
Next wipe–no rhythm it keeps
Track history

Players

AveragePeak
0123414:0023:0008:0017:0003:0012:00

Hourly average and peak, UTC.

Server performance

05010015020014:0023:0008:0017:0003: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 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.

Flight plan

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 UTC14d ago 2 – running 0
Tue 13 Oct, 08:11 UTC16d ago 1 – 1.3 days 0
Mon 12 Oct, 16:00 UTC16d ago 1 – 0.7 days 0
Sun 11 Oct, 20:24 UTC17d ago 1 – 0.8 days 0
Sun 11 Oct, 13:47 UTC17d ago 1 – 0.3 days 0
Sat 10 Oct, 15:10 UTC18d 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.

Nearby traffic

Similar servers

The same kind of game, then region, group limit, rate and wipes.

  1. 01MOD
    Callsign ATL015EU · groups of 16+ · 2x · monthly · 828 on average Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes
    Players 823/900
  2. 02MOD
    Callsign VTL015EU · groups of 16+ · 2x · monthly · 611 on average Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes
    Players 441/500
  3. 03MOD
    Callsign ATL015NA · groups of 16+ · 2x · monthly · 375 on average Atlas - US 2X Monthly | Vanilla+ | No BP Wipes
    Players 121/150
  4. 04MOD
    Callsign RNG017EU · groups of 50+ · 2x · monthly · 354 on average EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr
    Players 194/205
  5. 05MOD
    Callsign MGC010EU · groups of 150+ · 2x · weekly · 333 on average Magic Rust #18 — Vanilla 2x | Baйп 28.10
    Players 1,058/1110
  6. 06MOD
    Callsign MRG002EU · groups of 300+ · 2x · weekly · 316 on average MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10
    Players 172/1000
ATIS · this server

Quick answers

From the figures on this page.

Tags

Where does MOXESRUST | CUSTOM MAP | 2X | MAX 3 appear in Rust Tracker lists and filters?

On Rust Tracker, MOXESRUST | CUSTOM MAP | 2X | MAX 3 sits in these lists: 2x Rust servers, tracked live and Modded servers, tracked live. These filters surface it on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.

Which tags does MOXESRUST | CUSTOM MAP | 2X | MAX 3 carry, and what do they mean?

The game's server browser reads these tags from MOXESRUST | CUSTOM MAP | 2X | MAX 3: gmrust (Game mode): Survival as standard Rust plays; mp100 (Max players): 100 slots on this server; ts8 (Group limit): Default team size: 8; v2635 (Protocol): Join only if your game is on protocol 2635; cs167781 (Build): Build: 167781; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Under Modded: the game is changed by plugins or settings. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.

Wipe Schedule

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

The average peak across recent wipes: 1 players. The peak on the latest wipe came 19 hours after it.

When does MOXESRUST | CUSTOM MAP | 2X | MAX 3 wipe?

Wipe times at MOXESRUST | CUSTOM MAP | 2X | MAX 3 are irregular, so no next wipe can be predicted. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. This world has been running 14 days 21 hours.

Server Details

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

Tracking shows MOXESRUST | CUSTOM MAP | 2X | MAX 3 online as of now. About 3 days 1 hours ago it restarted last, based on reported uptime. Uptime stood at 99% for the last 7 full days, 167 of 168 hours online. First contact for Rust Tracker: 5 October 2026.

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

Rust network protocol 2635 and build 167781 on Linux is what MOXESRUST | CUSTOM MAP | 2X | MAX 3 runs. The same protocol is required to join, and Steam updates it for you.

Is MOXESRUST | CUSTOM MAP | 2X | MAX 3 holding performance?

For the last 48 hours it averaged 119 server fps; the floor was 116. Peak entity count: 15,596, covering buildings, deployables and all else in the world. Peak memory use: 3,542 MB. Lag, as players experience it, comes from low fps and a rising entity count.

What location is MOXESRUST | CUSTOM MAP | 2X | MAX 3 hosted in?

Region: none published by MOXESRUST | CUSTOM MAP | 2X | MAX 3. Rust Tracker displays the location a server claims; it does not verify where the machine sits. Connect on 157.85.95.221:27057.

Player Count

How many players are on MOXESRUST | CUSTOM MAP | 2X | MAX 3 right now?

Tracking MOXESRUST | CUSTOM MAP | 2X | MAX 3: 0 of 100 slots filled. Across the past seven days, 0 players on average.

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

Top 69% of all ranked servers, and #15,326 on seven-day player hours: MOXESRUST | CUSTOM MAP | 2X | MAX 3.

Settings

Which settings and rules are confirmed on MOXESRUST | CUSTOM MAP | 2X | MAX 3?

The name says it: MOXESRUST | CUSTOM MAP | 2X | MAX 3 runs 2x gather. Up to 8 players per group, the game's default. survival is the game mode, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. Plugins or settings change the game, and the server browser lists it under Modded. Plugins on it: Oxide. On: VAC, Valve's anti-cheat.

Which map is loaded on MOXESRUST | CUSTOM MAP | 2X | MAX 3?

The map on MOXESRUST | CUSTOM MAP | 2X | MAX 3 is procedural, size 1,850, seed 2147483647, generated by the game. Same size, same seed, same map. RustMaps shows it, linked from this page. Its map goes by the name Custom Map.

How to Join

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

Open the console in Rust with F1 after starting the game, then type client.connect 157.85.95.221:27057. Alternatively, Launch Rust here opens Rust via Steam and connects you.

Transponder codes

Server tags

What each one means.

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

Game

gmrust
Game mode Survival as standard Rust plays.
mp100
Max players 100 slots on this server.
ts8
Group limit Default team size: 8.
v2635
Protocol Join only if your game is on protocol 2635.
cs167781
Build Build: 167781.
ptrak
Networking Network layer is RakNet, which is standard for the game.
$r?
Region code Region code: not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Under Modded: 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.