Working its way up from the back of the class: #10,593 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
43/ 100
F
Slipped a little: down 1,432 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to D.
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.
AveragePeak
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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 48% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 10h.
The force wipe · high confidence
wipe-day peak2players, last three wipes
Coming wipes
7d 10hThu 5 Nov, 19:00 UTCFW
35d 10hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 21:47 UTCFW27d ago
2
–
running
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
You'll find no region listed by WM3_SERVER. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 37.139.100.131:28015.
How dependable is WM3_SERVER, and is it online at the moment?
The server is down: WM3_SERVER is offline now, with the last sighting 5 days 10 hours ago. It was up 1% of the time over the last 7 full days, 2 of 168 hours. It was first seen by Rust Server Score on 13 September 2026.
What Rust version is WM3_SERVER on?
Rust network protocol 2635 and build 168909 on Windows is what WM3_SERVER runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does WM3_SERVER wipe its map?
Once a month, WM3_SERVER wipes with the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. It has been running its current world for 27 days 8 hours.
What should you expect from wipe day on WM3_SERVER?
Across its recent wipes, the busiest moments averaged 2 players. 2 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does WM3_SERVER place in the wider field of Rust servers?
In the top 48% of all ranked servers, WM3_SERVER sits at #10,593 for player hours over the last seven days.
What does the population on WM3_SERVER look like?
It has been 5 days 10 hours since WM3_SERVER was last seen, and it is offline right now. The seven-day average is 2 players, with a peak of 2.
Tags
What is meant by the tags on WM3_SERVER?
You'll see WM3_SERVER tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp3 (Max players): Its slot count is 3; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature WM3_SERVER?
These Rust Server Score lists count WM3_SERVER among them: 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.
Rules and settings
What settings and rules apply on WM3_SERVER?
Nothing in the name of WM3_SERVER states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. VAC, Valve's anti-cheat, is not enabled.
Which map is in play on WM3_SERVER?
WM3_SERVER runs a procedural map, which the game generates.
Getting in
How should you connect to WM3_SERVER?
Enter client.connect 37.139.100.131: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 asmp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp3
Max playersIts slot count is 3.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins 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.
A term to build on. Even marks across the subjects, from F to D.