StatusLive Servers online11,695 Players53,904 Populated3,130 Wiped · 3 h120 Interval5 min Date30 OCT 2026

DWG RG-S15284Server sheetchecked 11m ago

MOXESRUST | CUSTOM MAP | 2X | MAX 3

Online 157.85.95.221:27057 checked 11m ago

2x moddedoxide
Connect
Players now 0/ 100 0% full
7-day average0peak –
Rank#15,284top 69%
Last wipe15d agono schedule published
Next wipe–no rhythm it keeps
Fig. 1

Players

AveragePeak
0123402:0011:0021:0006:0015:0000:00

Hourly average and peak, UTC.

Fig. 1Players on MOXESRUST | CUSTOM MAP | 2X | MAX 3
Fig. 2

Server performance

05010015020002:0011:0021:0006:0015:0000: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.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k5 Oct10 Oct15 Oct20 Oct25 Oct30 Oct

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

Fig. 3Rank on player hours, daily
Schedule

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
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

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 UTC18d 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 UTC24d 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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
Atlas - EU 2X Monthly | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 803 on average
255 / 300
02
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP WipesEU · groups of 16+ · 2x · monthly · 626 on average
655 / 700
03
Atlas - US 2X Monthly | Vanilla+ | No BP WipesNA · groups of 16+ · 2x · monthly · 364 on average
123 / 150
04
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob FrEU · groups of 50+ · 2x · monthly · 356 on average
275 / 320
05
Magic Rust #18 — Vanilla 2x | Baйп 28.10EU · groups of 150+ · 2x · weekly · 339 on average
182 / 240
06
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10EU · groups of 300+ · 2x · weekly · 319 on average
13 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

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

MOXESRUST | CUSTOM MAP | 2X | MAX 3 is up at this moment. The uptime it reports puts the last restart at about 3 days 13 hours ago. 167 of 168 hours up over the last 7 full days, which is 99% of the time. First seen by Rust Graphs on 5 October 2026.

What does the recorded performance of MOXESRUST | CUSTOM MAP | 2X | MAX 3 show?

The last 48 hours give an average of 119 server fps and a floor of 116. Counted at its highest: 15,596 entities, buildings, deployables and the rest of the world included. Memory use peaked at 3,597 MB. What players feel as lag is low fps together with a climbing entity count.

In which location is MOXESRUST | CUSTOM MAP | 2X | MAX 3 hosted?

No region is published by MOXESRUST | CUSTOM MAP | 2X | MAX 3. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 157.85.95.221:27057 is its address.

On which Rust version is MOXESRUST | CUSTOM MAP | 2X | MAX 3 running?

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

Population

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

0 of 100 slots on MOXESRUST | CUSTOM MAP | 2X | MAX 3 are taken at the latest refresh. The seven-day mean on this server is 0 players.

What rank has been recorded for MOXESRUST | CUSTOM MAP | 2X | MAX 3?

Over the last seven days, MOXESRUST | CUSTOM MAP | 2X | MAX 3 records #15,284 for player hours: the top 69% of all ranked servers.

Wipe data

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

At their busiest, its recent wipes drew 1 players on average. 19 hours after the latest wipe, the crowd peaked.

Which times and days are wipes plotted at on MOXESRUST | CUSTOM MAP | 2X | MAX 3?

MOXESRUST | CUSTOM MAP | 2X | MAX 3 wipes at times that follow no pattern, so no next wipe can be predicted. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. 15 days 9 hours ago the current world was made.

Settings

What settings and rules apply on MOXESRUST | CUSTOM MAP | 2X | MAX 3?

2x gather is stated in the name of MOXESRUST | CUSTOM MAP | 2X | MAX 3. Eight players per group: the default for the game. survival, the standard game: gather, build, raid, is the game mode. Fighting and raiding between players are enabled. Plugins or settings change the game, and the browser lists it as Modded. Plugins run: Oxide. VAC is on: that is Valve's anti-cheat.

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

MOXESRUST | CUSTOM MAP | 2X | MAX 3 runs a procedural map of size 1,850 with seed 2147483647, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing. Recorded map name: Custom Map.

Lists and filters

On Rust Graphs, which lists and filters contain MOXESRUST | CUSTOM MAP | 2X | MAX 3?

On Rust Graphs, MOXESRUST | CUSTOM MAP | 2X | MAX 3 is placed in these lists: Servers with a 2x gather rate and Modded Rust servers. It is returned by these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.

On MOXESRUST | CUSTOM MAP | 2X | MAX 3, what is meant by each tag?

The game's server browser reads these tags from MOXESRUST | CUSTOM MAP | 2X | MAX 3: gmrust (Game mode): Survival in standard Rust style; mp100 (Max players): 100 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): To join, your game must be on protocol 2635; cs167781 (Build): 167781 is the game build; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): Region code not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

Connect

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

Enter client.connect 157.85.95.221:27057 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

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

Game

gmrust
Game mode Survival in standard Rust style.
mp100
Max players 100 player slots.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol To join, your game must be on protocol 2635.
cs167781
Build 167781 is the game build.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code Region code not set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is 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.

KeyTag string decoded