MOXESRUST | CUSTOM MAP | 2X | MAX 3
Online 157.85.95.221:27057 checked 8m ago
Vital stats
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 19 hours in.
Wipes
| Wiped | Peak | Crowd | Lasted | Players 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 UTC18d 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.
Similar servers
The same kind of game, then region, group limit, rate and wipes.
Quick answers
From the figures on this page.
Lists and tags
Which Rust Pop Watch lists and filters include MOXESRUST | CUSTOM MAP | 2X | MAX 3?
You'll find MOXESRUST | CUSTOM MAP | 2X | MAX 3 on the following Rust Pop Watch lists: 2x Rust servers, live and Modded Rust servers, live. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.
What do the server tags on MOXESRUST | CUSTOM MAP | 2X | MAX 3 mean?
For the server browser, MOXESRUST | CUSTOM MAP | 2X | MAX 3 lists these tags: gmrust (Game mode): Survival, standard Rust style; mp100 (Max players): It has 100 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): To join, your game must be on the same protocol version: 2635; cs167781 (Build): The game build is 167781; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): Region code left blank; ^o (Oxide): A plugin framework called Oxide (uMod) is running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. The tags also carry its current players, queue and world creation time, all shown at the top of this page.
Population
How does MOXESRUST | CUSTOM MAP | 2X | MAX 3 rank against other Rust servers?
Player hours over the last week rank MOXESRUST | CUSTOM MAP | 2X | MAX 3 at #15,344, within the top 69% of ranked servers.
How many players are on MOXESRUST | CUSTOM MAP | 2X | MAX 3 right now?
The current tally at MOXESRUST | CUSTOM MAP | 2X | MAX 3: 0 players across 100 slots. Across the past week it drew an average of 0 players.
Server facts
Is MOXESRUST | CUSTOM MAP | 2X | MAX 3 online, and how reliable is it?
MOXESRUST | CUSTOM MAP | 2X | MAX 3 is live at the moment. The uptime figure suggests it restarted roughly 3 days 2 hours ago. The last 7 full days saw uptime of 99%, with 167 out of 168 hours online. The first time Rust Pop Watch saw it was 5 October 2026.
Does MOXESRUST | CUSTOM MAP | 2X | MAX 3 run smoothly?
Its server fps over the last 48 hours averaged 119, with 116 as the lowest. At its peak it held 15,596 entities: buildings, deployables and all the rest. Memory use peaked at 3,542 MB. What players experience as lag comes from low fps and a rising entity count.
Where is MOXESRUST | CUSTOM MAP | 2X | MAX 3 located?
There is no region from MOXESRUST | CUSTOM MAP | 2X | MAX 3. It is where a server says it is that Rust Pop Watch shows; the machine's actual location is not looked up. Connect at 157.85.95.221:27057.
Which Rust version is MOXESRUST | CUSTOM MAP | 2X | MAX 3 on?
On Linux, MOXESRUST | CUSTOM MAP | 2X | MAX 3 runs Rust network protocol 2635 and build 167781. Joining requires your game to match the protocol, which Steam updates for you.
Wipe days
What happens on MOXESRUST | CUSTOM MAP | 2X | MAX 3 when wipe day comes around?
The average busiest crowd over recent wipes was 1 players. The crowd on the latest wipe topped out 19 hours in.
What is the wipe schedule on MOXESRUST | CUSTOM MAP | 2X | MAX 3?
No next wipe can be predicted for MOXESRUST | CUSTOM MAP | 2X | MAX 3: its wipes happen at irregular times. On Thursday 5 November at 19:00 UTC the force wipe arrives, and every Rust server wipes with it at monthly intervals. The world it is running now dates from 14 days 23 hours.
The rules
Which map does MOXESRUST | CUSTOM MAP | 2X | MAX 3 run?
Generated by the game with seed 2147483647, the map on MOXESRUST | CUSTOM MAP | 2X | MAX 3 is procedural and 1,850 in size. RustMaps has it from this page, since identical size and seed give an identical map. Custom Map is how the map name reads.
What are the rules and settings on MOXESRUST | CUSTOM MAP | 2X | MAX 3?
Gather comes at 2x on MOXESRUST | CUSTOM MAP | 2X | MAX 3, according to its name. Eight players per group: that is the game's default. the usual game of gathering, building and raiding: that is the survival mode. Raids and PvP are both on the table. The server browser files it under Modded, where plugins or settings change the game. Oxide plugins are running on it. The VAC anti-cheat from Valve is on.
How to join
How do I join MOXESRUST | CUSTOM MAP | 2X | MAX 3?
Enter client.connect 157.85.95.221:27057 in the console after pressing F1 in Rust. Or use Launch Rust here to open Rust through Steam and connect automatically.