Element card · group Modded · atomic number 15,327, its rank
MOXESRUST | CUSTOM MAP | 2X | MAX 3
Online 157.85.95.221:27057 checked 11m ago
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
daily · 1 is best
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts 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
newest first| Wiped | Peak | Crowd | Lasted | Players 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 wipesQuick answers
from the figures on this pageServer setup
What map is in play on MOXESRUST | CUSTOM MAP | 2X | MAX 3?
The map on MOXESRUST | CUSTOM MAP | 2X | MAX 3 is procedural at size 1,850 with seed 2147483647, made by the game. Same size and seed give the same map, so this page lets you look at it on RustMaps. Its map carries the name: Custom Map.
What rules has MOXESRUST | CUSTOM MAP | 2X | MAX 3 set, and what settings are in force?
The name says it: gather runs at 2x on MOXESRUST | CUSTOM MAP | 2X | MAX 3. Eight players per group is the limit, the game's default. Play runs as survival, gather, build and raid, as in the standard game. Fighting and raiding between players are allowed. Plugins or settings change the game, so the browser lists it under Modded. Oxide plugins are running on it. VAC is on, Valve's anti-cheat.
About the server
In what location does MOXESRUST | CUSTOM MAP | 2X | MAX 3 sit?
No region is published by MOXESRUST | CUSTOM MAP | 2X | MAX 3. Rust Data Lab shows a server's stated location, not a verified position of the machine. 157.85.95.221:27057 is the address it uses.
What Rust version does MOXESRUST | CUSTOM MAP | 2X | MAX 3 currently run?
On Linux, MOXESRUST | CUSTOM MAP | 2X | MAX 3 is running Rust network protocol 2635 and build 167781. Your game needs to match the protocol to join, and Steam updates it automatically.
How dependable is MOXESRUST | CUSTOM MAP | 2X | MAX 3 for staying online?
Right now, MOXESRUST | CUSTOM MAP | 2X | MAX 3 is reachable. The uptime it reports suggests it restarted roughly 3 days 4 hours ago. It was online for 167 of 168 hours in the last 7 full days, which is 99% uptime. It first appeared to Rust Data Lab on 5 October 2026.
Is MOXESRUST | CUSTOM MAP | 2X | MAX 3 known for smooth running?
Server fps averaged 119 over the last 48 hours, with 116 as the lowest. The maximum entity count was 15,596, covering buildings, deployables and all else in the world. The highest memory usage was 3,542 MB. What players experience as lag comes from low fps and a rising entity count.
Wipes and resets
When does MOXESRUST | CUSTOM MAP | 2X | MAX 3 wipe, and how often?
With no fixed rhythm, MOXESRUST | CUSTOM MAP | 2X | MAX 3 wipes at irregular times, so the next wipe cannot be predicted. The next monthly force wipe, which wipes all Rust servers, is scheduled for Thursday 5 November at 19:00 UTC. Counting back, the current world began 15 days 1 hours ago.
What does a typical wipe day on MOXESRUST | CUSTOM MAP | 2X | MAX 3 involve?
Recent wipes on average reached 1 players at their busiest. The latest wipe's peak fell 19 hours after it began.
Where it appears
What should you understand from the tags MOXESRUST | CUSTOM MAP | 2X | MAX 3 carries?
These are the tags MOXESRUST | CUSTOM MAP | 2X | MAX 3 makes public for the server browser to read: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): It has 100 slots; ts8 (Group limit): This uses the game's default: 8 per team; v2635 (Protocol): To join, your game must match protocol 2635; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard in the game; $r? (Region code): The region field is left blank; ^o (Oxide): A plugin framework called Oxide (uMod) powers the plugins; ^z (Modded): You will find it under Modded: the game is altered by plugins or settings. Also in the tags are the players on now, the queue length and the world's creation time, and you can see them at the top of this page.
Where among the Rust Data Lab lists and filters does MOXESRUST | CUSTOM MAP | 2X | MAX 3 come up?
These themed Rust Data Lab lists carry MOXESRUST | CUSTOM MAP | 2X | MAX 3: 2x gather rate servers and Modded Rust servers, measured. 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.
Population
Against other Rust servers, where does MOXESRUST | CUSTOM MAP | 2X | MAX 3 place?
The seven-day player-hours table has MOXESRUST | CUSTOM MAP | 2X | MAX 3 at #15,327, in the top 69% of ranked servers.
How many players does MOXESRUST | CUSTOM MAP | 2X | MAX 3 have at the moment?
Of 100 slots, 0 are taken on MOXESRUST | CUSTOM MAP | 2X | MAX 3 right now. Over seven days the mean player count is 0.
Getting on
What is the way to join MOXESRUST | CUSTOM MAP | 2X | MAX 3?
Open the console with F1 in Rust and type client.connect 157.85.95.221:27057. The Launch Rust button on this page does the same job through Steam.