Rust PopulationField survey · Rust servers
Observing 83,167 players 11,844 servers 3,755 with someone on 280 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 15,335habitat unknownfirst seen 5 Oct 2026

MOXESRUST | CUSTOM MAP | 2X | MAX 3

Online 157.85.95.221:27057 checked 13m ago

2x moddedoxide

Measurements

Players now
0/ 100
0% full
7-day average
0
peak –
Rank
#15,335
top 69%
Last wipe
14d ago
no schedule published
Next wipe
–
no rhythm it keeps
Obs. 1 · sightings

Players

AveragePeak
0123415:0000:0009:0019:0004:0013:00

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

05010015020015:0000:0009:0019:0004:0013: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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
15k10k15k20k5 Oct10 Oct15 Oct19 Oct24 Oct29 Oct

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

Obs. 4 · the wipe cycle

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.

0.9 days
usual gap
between real wipes
25%
on rhythm
of its recent wipes
1
wipe-day peak
players, 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

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

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers 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.

Field questions

Quick answers

from the figures on this page

Player counts

How does MOXESRUST | CUSTOM MAP | 2X | MAX 3 rank against other Rust servers?

By player hours over the last seven days, MOXESRUST | CUSTOM MAP | 2X | MAX 3 places at #15,335, within the top 69% of ranked servers.

How busy is MOXESRUST | CUSTOM MAP | 2X | MAX 3?

Of its 100 slots, MOXESRUST | CUSTOM MAP | 2X | MAX 3 is using 0 right now. We counted 0 players on average across the past week.

Lists and tags

What do the server tags on MOXESRUST | CUSTOM MAP | 2X | MAX 3 mean?

These are the tags MOXESRUST | CUSTOM MAP | 2X | MAX 3 publishes, as read by the game's server browser: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): You can join up to 100 slots; ts8 (Group limit): This is the game default: at most 8 per team; v2635 (Protocol): Your game needs the same version, protocol 2635, to join; cs167781 (Build): Game build: 167781; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank; ^o (Oxide): A plugin framework, Oxide (uMod), is in use; ^z (Modded): Plugins or settings change the game; it is listed under Modded. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.

Which Rust Population lists and filters include MOXESRUST | CUSTOM MAP | 2X | MAX 3?

MOXESRUST | CUSTOM MAP | 2X | MAX 3 appears among the Rust Population lists that follow: 2x Rust servers: the live count and Modded Rust servers, counted. Filter the server list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x and it will show up.

Wipe schedule

What does wipe day look like on MOXESRUST | CUSTOM MAP | 2X | MAX 3?

The busiest point of its recent wipes averaged 1 players. The crowd on the latest wipe peaked 19 hours in.

What is the wipe schedule on MOXESRUST | CUSTOM MAP | 2X | MAX 3?

Irregular times are when MOXESRUST | CUSTOM MAP | 2X | MAX 3 wipes, which leaves no next wipe to predict. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. The world it runs now dates from 14 days 23 hours ago.

Map and rules

Which map does MOXESRUST | CUSTOM MAP | 2X | MAX 3 run?

The map on MOXESRUST | CUSTOM MAP | 2X | MAX 3 is procedural, made by the game at size 1,850 from seed 2147483647. You can look at it on RustMaps from this page: size and seed determine the map. The name on the map is Custom Map.

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

MOXESRUST | CUSTOM MAP | 2X | MAX 3 advertises a 2x gather rate in its title. No limit is set beyond the standard 8 players per group. survival is what it runs, raid, build and gather: the standard game. Fighting and raiding between players is allowed. The server browser files it under Modded, where plugins or settings alter the game. You will find Oxide running as plugins. You play with Valve's anti-cheat on: VAC.

Server details

Which version of Rust does MOXESRUST | CUSTOM MAP | 2X | MAX 3 run?

The setup is Rust network protocol 2635 and build 167781 on Linux for MOXESRUST | CUSTOM MAP | 2X | MAX 3. Your game needs the same protocol to join; Steam takes care of updating it.

Does MOXESRUST | CUSTOM MAP | 2X | MAX 3 run smoothly?

In the last 48 hours, it averaged 119 server fps, with a low of 116. Entities peaked at 15,596, including buildings, deployables and everything else. Up to 3,542 MB of memory was used. Players feel lag when fps is low and the entity count climbs.

Is MOXESRUST | CUSTOM MAP | 2X | MAX 3 online, and how reliable is it?

MOXESRUST | CUSTOM MAP | 2X | MAX 3 is up and running at the moment. The uptime it reports suggests a restart roughly 3 days 2 hours ago. It was up 99% of the time over the last 7 full days, 167 out of 168 hours. The first sighting by Rust Population was on 5 October 2026.

Where is MOXESRUST | CUSTOM MAP | 2X | MAX 3 located?

Nothing published by MOXESRUST | CUSTOM MAP | 2X | MAX 3 states a region. Rust Population does not look up where the machine stands; it shows where the server says it is. Connect at 157.85.95.221:27057.

Getting in

How do I join MOXESRUST | CUSTOM MAP | 2X | MAX 3?

Either enter client.connect 157.85.95.221:27057 in Rust's console after pressing F1, or use Launch Rust here to open Rust through Steam and be connected.

Key to its markings

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust style.
mp100
Max players You can join up to 100 slots.
ts8
Group limit This is the game default: at most 8 per team.
v2635
Protocol Your game needs the same version, protocol 2635, to join.
cs167781
Build Game build: 167781.
ptrak
Networking The standard network layer, RakNet, is in use.
$r?
Region code The region code is left blank.

Mods and access

^o
Oxide A plugin framework, Oxide (uMod), is in use.
^z
Modded Plugins or settings change the game; it is listed under 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.