Station XX-10565 · no signal
WM3_SERVER
Offline 37.139.100.131:28015 checked 5d ago
- Players now
- 2/ 3
- 67% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 2
- peak 2
- Rank
- #10,565
- top 48%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- 7d 8h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 2of 3 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 48% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 7d 8h. The force wipe · high confidence
- wipe-day peak
- 2players, last three wipes
Coming wipes
- 7d 8hThu 5 Nov, 19:00 UTCFW
- 35d 8hThu 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 | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 21:47 UTC FW27d ago | M0.3▲rising | 2 | – | running | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageServer rules
Which map is running on WM3_SERVER?
WM3_SERVER uses a procedural map, which the game generates.
Which settings and rules apply on WM3_SERVER?
No gather rate appears in the name of WM3_SERVER. Groups hold up to 8 players, which is the default for the game. In survival mode, standard play, with gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. The server has VAC off, Valve's anti-cheat.
Population
How many players are recorded on WM3_SERVER right now?
No players are recorded on WM3_SERVER at this moment; it is offline, and the last sighting was 5 days 13 hours ago. The seven-day average is 2 players, with a peak of 2.
How does WM3_SERVER rank against other Rust servers?
The last seven days of player hours place WM3_SERVER at #10,565, in the top 48% of all ranked servers.
Server facts
How reliably does WM3_SERVER stay online?
As recorded now, WM3_SERVER is not reachable, the last contact having been 5 days 13 hours ago. Of the 168 hours in the last 7 full days, it was up for 2, or 1% of the time. On 13 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does WM3_SERVER run from?
Nothing about a region comes from WM3_SERVER. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. The address it publishes is 37.139.100.131:28015.
What build of Rust does WM3_SERVER use?
WM3_SERVER is running Rust network protocol 2635 and build 168909 on a machine with Windows. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe pattern
What does wipe day look like on WM3_SERVER?
The recent wipes averaged a busiest count of 2 players. 2 hours after the latest wipe, the crowd peaked.
On what timetable does WM3_SERVER run its wipes?
Once a month WM3_SERVER wipes, at the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The present world dates from 27 days 11 hours.
Server tags
What do the server tags on WM3_SERVER mean?
The game's server browser reads the tags WM3_SERVER publishes: gmrust (Game mode): The game mode is standard Rust survival; mp3 (Max players): The server has 3 slots; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The server has no region code; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does WM3_SERVER appear?
These Rust Server Trends lists include WM3_SERVER: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Connecting
What steps get you onto WM3_SERVER?
Enter client.connect 37.139.100.131:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.