Working its way up from the back of the class: #15,346 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
38/ 100
F
Slipped a little: down 3,571 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
·······
·····W·
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap23 daysbetween real wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Sat 10 OctThu 17 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 25 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 10 Oct, 23:04 UTC17d ago
1
–
running
0
Thu 17 Sep, 22:44 UTC40d ago
0
–
23 days
0
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
MostWanted 1.5X leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 45.18.162.232:28015.
How dependable is MostWanted 1.5X, and is it online at the moment?
At this moment, MostWanted 1.5X is offline; the last time it was seen was 8 days 5 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is MostWanted 1.5X on?
Rust network protocol 2634 and build 167781 on Windows is what MostWanted 1.5X runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does MostWanted 1.5X reset?
There are too few wipes on record for MostWanted 1.5X to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 17 days 14 hours.
What happens on MostWanted 1.5X when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 25 hours into the latest wipe.
Player numbers
Where does MostWanted 1.5X sit among Rust servers?
Over the last seven days, MostWanted 1.5X has #15,346 for player hours, in the top 70% of all ranked servers.
Is MostWanted 1.5X a busy server?
The last sighting of MostWanted 1.5X was 8 days 5 hours ago, and it is offline right now.
Tags and filters
What do MostWanted 1.5X's tags stand for?
The game's browser takes its cue from the tags MostWanted 1.5X 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): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature MostWanted 1.5X?
These Rust Server Score lists count MostWanted 1.5X among them: 1.5x Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 1.5x.
Rules and settings
What settings and rules apply on MostWanted 1.5X?
Going by its name, MostWanted 1.5X runs 1.5x gather. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: 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. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
MostWanted 1.5X runs which map?
The game generates the procedural map on MostWanted 1.5X at size 4,250 with seed 6738. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to MostWanted 1.5X?
Enter client.connect 45.18.162.232:28015 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 asmp100,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; you will find it 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.
A term to build on. Even marks across the subjects, from F to F.