On the class lists: C (62), with population over 48 hours and no performance mark.
Players now2/ 367% full
7-day average2peak 2
Rank#8,405top 38%
Last wipe28d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
51/ 100
D
Room for more players: 2 of 3 on average.
Standingrank on player hours
62/ 100
C
Working its way up from the back of the class: #8,405 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
unmarked
–
No rank a week ago to compare with.
A fair term, with more to come.
Strongest in standing (C); population is the one to work on (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 38% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 31.28.241.211:28015 is the address to use.
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 2 days 23 hours ago. It was up 2% of the time over the last 2 full days, 1 of 48 hours. On 26 October 2026, Rust Server Score saw it for the first time.
Which Rust version is WM3_SERVER running?
The server WM3_SERVER is on Rust network protocol 2635 and build 168909 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does WM3_SERVER wipe its map?
There are too few wipes on record for WM3_SERVER 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 28 days.
Population
What position does WM3_SERVER hold in the rankings?
In the top 38% of all ranked servers, WM3_SERVER sits at #8,405 for player hours over the last seven days.
Is WM3_SERVER a busy server?
WM3_SERVER is offline at the moment; the last time it was seen was 2 days 23 hours ago. The seven-day average is 2 players, with a peak of 2.
Tags and filters
How should you read the tags on WM3_SERVER?
The game's browser takes its cue from the tags WM3_SERVER has set: 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): No region code has been set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show WM3_SERVER?
These Rust Server Score lists count WM3_SERVER among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
How is WM3_SERVER set up, and what rules does it keep?
You will find no gather rate in the name of WM3_SERVER. The group limit stays at the game's default of 8 players. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are not covered by VAC, Valve's anti-cheat.
Which map is in play on WM3_SERVER?
WM3_SERVER runs a procedural map, which the game generates.
How to join
What is the way to join WM3_SERVER?
To connect, start Rust, press F1, and type client.connect 31.28.241.211:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
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 codeNo region code has been set.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 fair term, with more to come. Strongest in standing (C); population is the one to work on (D).