Skip to the page
Every Rust server graded on real, live numbers. 69,381 players on the roll · 11,801 servers present
Rust Server ScoreReport for the October 2026 term
Rust Server Score · Report for the term · marked 29 October 2026 Pupil no. 157.85.95.221:27057
Name of server

MOXESRUST | CUSTOM MAP | 2X | MAX 3

RegisterPresentOnline
Region–
Address157.85.95.221:27057
Last checked14m ago
2x moddedoxide
Launch Rust and join
Overall grade

Working towards

54 out of 100, the average of 5 subjects

On the class lists: F (43), with population over 48 hours and no performance mark.

Players now 0/ 100 0% full
7-day average0peak –
Rank#15,326top 69%
Last wipe14d agono schedule published
Next wipe–no rhythm it keeps

Subjects

SubjectMarkGradeTeacher's comment
Populationplayers against slots, 7-day average 0/ 100 A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours 31/ 100 Working its way up from the back of the class: #15,326 on player hours.
Uptimehours on the list, last 48 94/ 100 Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours 100/ 100 Runs smoothly: 119 server fps on average.
Wipeskeeping the crowd after a wipe unmarked Too few wipes seen to mark this yet.
Momentumrank now against a week ago 47/ 100 Slipped a little: down 987 places this week. Nothing a good wipe can't fix.

A term to build on. Strongest in performance (A+); population is the one to work on (F).

How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.

Progress through the term

Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.

Players

AveragePeak
0123414:0023:0008:0016:0002:0011:00

Hourly average and peak, UTC.

Server performance

05010015020014:0023:0008:0016:0002:0011: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.

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.

Attendance: the wipe record

7 wipe days in the last 16 weeks

W wiped that day F the force wipe · today. From the wipes in the table below.

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.

usual gap0.9 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, 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.

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 UTC17d 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

classmates: the same kind of game, then region, group limit, rate and wipes
Atlas - EU 2X Monthly | Vanilla+ | No BP Wipes
EU · groups of 16+ · 2x · monthly · 828 on average
830 / 900
Vital Rust - EU Monthly | 2x | Vanilla+ | No BP Wipes
EU · groups of 16+ · 2x · monthly · 611 on average
462 / 500
Atlas - US 2X Monthly | Vanilla+ | No BP Wipes
NA · groups of 16+ · 2x · monthly · 375 on average
122 / 150
EU RENEGADE 2x Monthly Main | 50% Upkeep | No BP Wipe | Noob Fr
EU · groups of 50+ · 2x · monthly · 354 on average
186 / 205
Magic Rust #18 — Vanilla 2x | Baйп 28.10
EU · groups of 150+ · 2x · weekly · 333 on average
1058 / 1110
MIRAGE RUST | SUNDAY 2x | VANILLA+ | Wipe 25.10
EU · groups of 300+ · 2x · weekly · 316 on average
167 / 1000

Quick answers

from the figures on this page

About the server

Where in the world is MOXESRUST | CUSTOM MAP | 2X | MAX 3?

You'll find no region listed by MOXESRUST | CUSTOM MAP | 2X | MAX 3. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 157.85.95.221:27057 is the address to use.

How reliable is MOXESRUST | CUSTOM MAP | 2X | MAX 3, and is it up?

The server is up: MOXESRUST | CUSTOM MAP | 2X | MAX 3 is online now. According to its reported uptime, the last restart was about 3 days ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. It was first seen by Rust Server Score on 5 October 2026.

Is MOXESRUST | CUSTOM MAP | 2X | MAX 3 smooth to play on?

The average over the last 48 hours was 119 server fps, and it never went below 116. Up to 15,596 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 3,542 MB. Players feel lag when fps drops and entities pile up.

On what Rust version does MOXESRUST | CUSTOM MAP | 2X | MAX 3 sit?

The server MOXESRUST | CUSTOM MAP | 2X | MAX 3 is on Rust network protocol 2635 and build 167781 under Linux. Steam updates your game for you, but you need the same protocol to join.

Wipe cycle

How frequently does MOXESRUST | CUSTOM MAP | 2X | MAX 3 wipe its map?

MOXESRUST | CUSTOM MAP | 2X | MAX 3 wipes at times that vary, so no next wipe can be predicted. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 14 days 21 hours.

What happens on MOXESRUST | CUSTOM MAP | 2X | MAX 3 when wipe day arrives?

Across its recent wipes, the busiest moments averaged 1 players. Peak numbers came 19 hours into the latest wipe.

Population

Where does MOXESRUST | CUSTOM MAP | 2X | MAX 3 sit among Rust servers?

In the top 69% of all ranked servers, MOXESRUST | CUSTOM MAP | 2X | MAX 3 sits at #15,326 for player hours over the last seven days.

What does the population on MOXESRUST | CUSTOM MAP | 2X | MAX 3 look like?

Right now, 0 players are on MOXESRUST | CUSTOM MAP | 2X | MAX 3, which has 100 slots. A seven-day average of 0 players applies here.

Lists and filters

What do MOXESRUST | CUSTOM MAP | 2X | MAX 3's tags stand for?

The game's browser takes its cue from the tags MOXESRUST | CUSTOM MAP | 2X | MAX 3 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.

Where does MOXESRUST | CUSTOM MAP | 2X | MAX 3 appear in the Rust Server Score lists and filters?

These Rust Server Score lists count MOXESRUST | CUSTOM MAP | 2X | MAX 3 among them: 2x Rust servers, graded and Modded Rust servers, graded. 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.

Rules and settings

How is MOXESRUST | CUSTOM MAP | 2X | MAX 3 set up, and what rules does it keep?

Going by its name, MOXESRUST | CUSTOM MAP | 2X | MAX 3 runs 2x gather. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.

Can you tell me which map MOXESRUST | CUSTOM MAP | 2X | MAX 3 uses?

A procedural map of size 1,850 and seed 2147483647, generated by the game, is what MOXESRUST | CUSTOM MAP | 2X | MAX 3 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: Custom Map.

How to join

How do you get onto 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 on this page to open Rust through Steam and connect automatically.

Server tags

what each one means

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

Game

gmrust
Game mode This one runs plain Rust survival, with nothing altered.
mp100
Max players Its slot count is 100.
ts8
Group limit Teams are capped at 8, the game's standard setting.
v2635
Protocol Join only if your game runs protocol 2635.
cs167781
Build The game build is 167781.
ptrak
Networking The network layer is RakNet, standard for the game.
$r?
Region code No region code has been set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings alter the game, so it sits 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.