MOXESRUST | CUSTOM MAP | 2X | MAX 3
Online 157.85.95.221:27057 checked 11m ago
Server instruments
last reading Thu 14:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 116 · below 20 is lag, below 10 is badEntities
48 h range 13,223–15,596 · memory 2,791 MBUptime
3 days 3 hours since its last restart, at the last readingPlayers
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 bestTop 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 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 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- 770/900
- 465/425
- 140/200
- 642/220
- 907/1060
- 163/1000
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on MOXESRUST | CUSTOM MAP | 2X | MAX 3?
The busiest point of its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 19 hours in.
How often does MOXESRUST | CUSTOM MAP | 2X | MAX 3 wipe, and when?
No next wipe can be predicted for MOXESRUST | CUSTOM MAP | 2X | MAX 3, which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 14 days 23 hours ago.
Lists and filters
How should you read the tags on MOXESRUST | CUSTOM MAP | 2X | MAX 3?
These are the tags MOXESRUST | CUSTOM MAP | 2X | MAX 3 publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp100 (Max players): The server holds 100 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to get in; cs167781 (Build): Build 167781; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does MOXESRUST | CUSTOM MAP | 2X | MAX 3 appear in Rust Metrics lists and filters?
On Rust Metrics, MOXESRUST | CUSTOM MAP | 2X | MAX 3 sits in these lists: 2x Rust servers, checked live and Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.
Population
Where does MOXESRUST | CUSTOM MAP | 2X | MAX 3 sit in the rankings?
Player hours over seven days put MOXESRUST | CUSTOM MAP | 2X | MAX 3 at #15,344, in the top 69% of all ranked servers.
How full does MOXESRUST | CUSTOM MAP | 2X | MAX 3 get?
Current headcount on MOXESRUST | CUSTOM MAP | 2X | MAX 3: 0 players, 100 slots available. A seven-day average of 0 players is the reading.
Server details
What location is MOXESRUST | CUSTOM MAP | 2X | MAX 3 hosted in?
No region comes from MOXESRUST | CUSTOM MAP | 2X | MAX 3. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 157.85.95.221:27057.
What Rust version is MOXESRUST | CUSTOM MAP | 2X | MAX 3 on?
Version check: Rust network protocol 2635 and build 167781 on Linux, run by MOXESRUST | CUSTOM MAP | 2X | MAX 3. To get in, your game needs the same protocol; Steam applies the update.
How does MOXESRUST | CUSTOM MAP | 2X | MAX 3 perform?
Reading: 119 server fps on average across the last 48 hours. It never dropped below 116. Reading: 15,596 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 3,542 MB. Lag, as players feel it, is low fps plus a climbing entity count.
Is MOXESRUST | CUSTOM MAP | 2X | MAX 3 up, and how often does it stay up?
MOXESRUST | CUSTOM MAP | 2X | MAX 3 reports online. Status: normal. Reading: uptime. About 3 days 3 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 5 October 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on MOXESRUST | CUSTOM MAP | 2X | MAX 3?
Gather rate check: 2x. That comes from the name MOXESRUST | CUSTOM MAP | 2X | MAX 3. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.
Which map is live on MOXESRUST | CUSTOM MAP | 2X | MAX 3?
From seed 2147483647, the game generates the procedural map on MOXESRUST | CUSTOM MAP | 2X | MAX 3. Its size is 1,850. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Read the map name: Custom Map.
Connection
What do you do to join MOXESRUST | CUSTOM MAP | 2X | MAX 3?
To join: start Rust, press F1 and type client.connect 157.85.95.221:27057. Or press Launch Rust here and Steam opens the game and connects you.