Station XX-15310 · recording
MOXESRUST | CUSTOM MAP | 2X | MAX 3
Online 157.85.95.221:27057 checked 11m ago
- Players now
- 0/ 100
- 0% full
- Motion · 24 h
- M0.0■steady
- +0 players on the day
- 7-day average
- 0
- peak –
- Rank
- #15,310
- top 69%
- Last wipe
- 15d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 100 slots
- Motion · 24 h
- M0.0■steady+0 players
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 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.
- usual gap
- 0.9 daysbetween real wipes
- on rhythm
- 25%of its recent wipes
- wipe-day peak
- 1players, last three wipes
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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Wed 14 Oct, 15:45 UTC15d ago | M0.3▲rising | 2 | – | running | 0 | |
| Tue 13 Oct, 08:11 UTC16d ago | M0.0▲rising | 1 | – | 1.3 days | 0 | |
| Mon 12 Oct, 16:00 UTC17d ago | M0.0▲rising | 1 | – | 0.7 days | 0 | |
| Sun 11 Oct, 20:24 UTC17d ago | M0.0▲rising | 1 | – | 0.8 days | 0 | |
| Sun 11 Oct, 13:47 UTC18d ago | M0.0▲rising | 1 | – | 0.3 days | 0 | |
| Sat 10 Oct, 15:10 UTC19d ago | M0.0▲rising | 1 | – | 0.9 days | 0 | |
| Wed 7 Oct, 12:28 UTC22d ago | M0.0▲rising | 1 | halved by day 2 | 3.1 days | 0 | |
| Wed 7 Oct, 06:10 UTC22d ago | M0.0▲rising | 1 | – | 0.3 days | 0 | |
| Mon 5 Oct, 18:52 UTC23d ago | M0.0■steady | 1 | – | 1.5 days | 1 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 rules
Which map is running on MOXESRUST | CUSTOM MAP | 2X | MAX 3?
The procedural map on MOXESRUST | CUSTOM MAP | 2X | MAX 3 is size 1,850 with seed 2147483647, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. Its map carries the name Custom Map.
Which settings and rules apply on MOXESRUST | CUSTOM MAP | 2X | MAX 3?
2x gather is what MOXESRUST | CUSTOM MAP | 2X | MAX 3 runs, judging by its name. At the game's default, groups can have up to 8 players. In survival mode, the usual game of gathering, building and raiding. You can raid and fight other players here. Plugins or settings alter the game here; the browser lists it as Modded. Its plugins are run through Oxide. Anti-cheat is on: VAC, from Valve.
Live population
How many players are recorded on MOXESRUST | CUSTOM MAP | 2X | MAX 3 right now?
At this moment, MOXESRUST | CUSTOM MAP | 2X | MAX 3 records 0 players across 100 slots. The seven-day average for this server is 0 players.
How does MOXESRUST | CUSTOM MAP | 2X | MAX 3 rank against other Rust servers?
On player hours for the past week, MOXESRUST | CUSTOM MAP | 2X | MAX 3 sits at #15,310, which puts it inside the top 69% of every ranked server.
Operator and location
How reliably does MOXESRUST | CUSTOM MAP | 2X | MAX 3 stay online?
Right now, you can reach MOXESRUST | CUSTOM MAP | 2X | MAX 3. Going by the uptime figure it reports, it restarted about 3 days 5 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. Its earliest appearance in the records of Rust Server Trends dates to 5 October 2026.
Does MOXESRUST | CUSTOM MAP | 2X | MAX 3 hold a steady tick rate?
The 48-hour average is 119 server fps; 116 is the lowest observed. The world held up to 15,596 entities at its peak, buildings and deployables included. Its highest memory use was 3,542 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.
Which region does MOXESRUST | CUSTOM MAP | 2X | MAX 3 run from?
Nothing about a region comes from MOXESRUST | CUSTOM MAP | 2X | MAX 3. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. The address it publishes is 157.85.95.221:27057.
Which Rust version is MOXESRUST | CUSTOM MAP | 2X | MAX 3 running?
Rust network protocol 2635 and build 167781 on Linux is what MOXESRUST | CUSTOM MAP | 2X | MAX 3 runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe schedule
What does wipe day look like on MOXESRUST | CUSTOM MAP | 2X | MAX 3?
On average, the busiest point of its recent wipes drew 1 players. 19 hours after the latest wipe, the crowd peaked.
On what timetable does MOXESRUST | CUSTOM MAP | 2X | MAX 3 run its wipes?
There is no next wipe to predict at MOXESRUST | CUSTOM MAP | 2X | MAX 3, since its wipes fall at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 15 days 2 hours.
Tags
What do the server tags on MOXESRUST | CUSTOM MAP | 2X | MAX 3 mean?
The game's server browser reads the tags MOXESRUST | CUSTOM MAP | 2X | MAX 3 publishes: gmrust (Game mode): You'll find standard Rust survival here; mp100 (Max players): 100 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does MOXESRUST | CUSTOM MAP | 2X | MAX 3 appear?
The Rust Server Trends lists that take in MOXESRUST | CUSTOM MAP | 2X | MAX 3 are: 2x Rust servers, listed live and Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.
How to join
How do you connect to MOXESRUST | CUSTOM MAP | 2X | MAX 3?
Enter client.connect 157.85.95.221:27057 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.