Rust PopulationField survey · Rust servers
Observing 75,437 players 11,810 servers 3,743 with someone on 107 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 10,610habitat unknownfirst seen 13 Sep 2026

WM3_SERVER

Offline 37.139.100.131:28015 checked 4d ago

moddedoxide

Measurements

Players now
2/ 3
= 1 player
67% full
7-day average
2
peak 2
Rank
#10,610
top 48%
Last wipe
26d ago
no schedule published
Next wipe
7d 21h
Thu 5 Nov, 19:00 UTC FW
Obs. 1 · sightings

Players

No hourly history yet.

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep26 Sep3 Oct9 Oct22 Oct28 Oct

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

Obs. 4 · the wipe cycle

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 21h. The force wipe · high confidence

2
wipe-day peak
players, last three wipes

Coming wipes

7d 21h
Thu 5 Nov, 19:00 UTC
FW
35d 21h
Thu 3 Dec, 19:00 UTC
FW

The first 48 hours of its last wipes

00.511.52+0h+9h+19h+28h+38h+47h

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

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 1 Oct, 21:47 UTC FW26d 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.

Field questions

Quick answers

from the figures on this page

Player counts

How does WM3_SERVER rank against other Rust servers?

The last seven days of player hours place WM3_SERVER at #10,610, within the top 48% of all ranked servers.

How busy is WM3_SERVER?

WM3_SERVER is offline at this count; we last saw it 4 days 23 hours ago. Averaged over seven days, it drew 2 players and reached a peak of 2.

Lists and tags

What do the server tags on WM3_SERVER mean?

The game's server browser reads the tags WM3_SERVER publishes: gmrust (Game mode): Survival in the standard Rust style; mp3 (Max players): The server has 3 slots; ts8 (Group limit): 8 per team is the default limit; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): RakNet is the network layer here, as standard for the game; $r? (Region code): This server has no region code; ^o (Oxide): The plugin framework Oxide (uMod) runs on this server; ^z (Modded): Plugins or settings change the game; it is listed under Modded. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.

Which Rust Population lists and filters include WM3_SERVER?

WM3_SERVER appears among the Rust Population lists that follow: Modded Rust servers, counted. Filter the server list by Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more and it will show up.

Wipe schedule

What does wipe day look like on WM3_SERVER?

The busiest point of its recent wipes averaged 2 players. Peak came 2 hours into the latest wipe.

What is the wipe schedule on WM3_SERVER?

WM3_SERVER wipes with the force wipe and at no other time, once a month. On Thursday 5 November at 19:00 UTC comes its next wipe: the force wipe, when all Rust servers wipe. 26 days 21 hours ago the current world was made.

Settings

Which map does WM3_SERVER run?

A procedural map, generated by the game, is in use on WM3_SERVER.

What are the rules and settings on WM3_SERVER?

No gather rate appears in the name of WM3_SERVER. No limit is set beyond the standard 8 players per group. You get survival here, raid, build and gather: the standard game. Combat between players, raids included, is permitted. Modded is its browser category: plugins or settings change the game. The plugins it runs are Oxide. VAC, Valve's anti-cheat, is not running.

About the server

Which version of Rust does WM3_SERVER run?

Rust network protocol 2635 and build 168909 on Windows is what WM3_SERVER uses. The protocol must match for you to join, and Steam updates it for you.

Is WM3_SERVER online, and how reliable is it?

Currently offline, WM3_SERVER was last seen 4 days 23 hours ago. It was up 1% of the time over the last 7 full days, 2 out of 168 hours. The first sighting by Rust Population was on 13 September 2026.

Where is WM3_SERVER located?

Nothing published by WM3_SERVER states a region. Rust Population does not look up where the machine stands; it shows where the server says it is. You will find it at 37.139.100.131:28015.

Getting in

How do I join WM3_SERVER?

To connect directly, open Rust's console with F1 and type client.connect 37.139.100.131:28015; or press Launch Rust on this page and Steam opens Rust and joins for you.

Key to its markings

Server tags

what each one means

Published as mp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Survival in the standard Rust style.
mp3
Max players The server has 3 slots.
ts8
Group limit 8 per team is the default limit.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking RakNet is the network layer here, as standard for the game.
$r?
Region code This server has no region code.

Mods and access

^o
Oxide The plugin framework Oxide (uMod) runs on this server.
^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.