WM3_SERVER
ruststatistics.org · independent, not affiliated with Facepunch Studios
Offline · checked 5d ago · 37.139.100.131:28015
Abstract
We describe the public Rust server WM3_SERVER, reached at 37.139.100.131:28015. It is offline at the last check, against a seven-day mean of 2 and a peak of 21. It ranks #10,597 of all servers, the top 48%. It last wiped 27d ago; the next wipe is expected Thursday 5 November, 19:00 UTC, the force wipe.
Keywordsmodded oxide
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 48% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: force wipes only
The next wipe is expected Thursday 5 November, 19:00 UTC, in 7d 15h. The force wipe (high confidence).
| Measure | Value | Note |
|---|---|---|
| Wipe-day peak | 2 | players, last three wipes |
| When (UTC) | In | Kind |
|---|---|---|
| Thu 5 Nov, 19:00 | 7d 15h | force wipefw |
| Thu 3 Dec, 19:00 | 35d 15h | force wipefw |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Thu 1 Oct, 21:47fw27d 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| Address | 37.139.100.131:28015 |
|---|---|
| Region | – |
| Max players | 3 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 1 Oct 2026, 23:38 UTC |
| Hostname | – |
| First seen | 13 Sep 2026 |
| Map | Procedural Map |
| Size | – |
| Seed | – |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and predicted wipe schedule [3].
| Server | Players |
|---|---|
| ShockRust | Blue | NoLimitno group limit · 154 on average | 31/500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average | 133/100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average | 39/225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 93 on average | 11/700 |
| RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average | 3/200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average | 1/1000 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1What location does WM3_SERVER have?
There is no region published for WM3_SERVER. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 37.139.100.131:28015.
A.2What is the online status and reliability of WM3_SERVER?
WM3_SERVER is currently offline, with the last sighting 5 days 6 hours ago. The server was up 1% of the time over the last 7 full days, 2 of 168 hours. The first record of it by Rust Statistics dates to 13 September 2026.
A.3What is the Rust version for WM3_SERVER?
The version of Rust on WM3_SERVER is network protocol 2635 and build 168909, and the operating system is Windows. Steam updates your game for you, but you must be on the same protocol to join.
Wipe schedule
A.4What schedule does WM3_SERVER follow for wipes?
The only wipe for WM3_SERVER is the monthly force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC; this server's next wipe is then. 27 days 4 hours have passed since the current world was generated.
A.5What happens on WM3_SERVER when wipe day arrives?
The average busiest point of recent wipes was 2 players. The peak on the latest wipe came 2 hours after it began.
Player count
A.6What position does WM3_SERVER occupy in the ranking of Rust servers?
The seven-day player-hours ranking puts WM3_SERVER at #10,597, within the top 48% of ranked servers.
A.7How would you characterise the player activity on WM3_SERVER?
WM3_SERVER is not online now; 5 days 6 hours have passed since it was last seen. Over the last week the count averages 2 players and reaches 2 at its height.
Tags, lists
A.8How should the tags on WM3_SERVER be interpreted?
The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp3 (Max players): The slot count is 3; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): The region code is unset; ^o (Oxide): Plugins are handled by Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game, which WM3_SERVER publishes as its tags. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.
A.9Where can WM3_SERVER be found among the Rust Statistics lists and filters?
The Rust Statistics lists that WM3_SERVER fits are: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Settings and map
A.10Under what rules and settings does WM3_SERVER operate?
No gather rate appears in the name of WM3_SERVER. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. The server browser lists it as Modded, where plugins or settings alter the game. The plugin count is Oxide. VAC is not in use; Valve's anti-cheat is off.
A.11What map is in use on WM3_SERVER?
A procedural map, generated by the game, is what WM3_SERVER runs.
How to join
A.12How do you connect to WM3_SERVER?
Press F1 inside Rust to open the console and enter client.connect 37.139.100.131:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.
Appendix BServer tags
What each of the server's tags means. Published as mp3,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Survival on standard Rust rules. |
mp3 | Max players. The slot count is 3. |
ts8 | Group limit. The team cap is 8, which is the game default. |
v2635 | Protocol. Your game must run protocol 2635 to connect. |
cs168909 | Build. The game build is 168909. |
ptrak | Networking. RakNet is the network layer here, as it is by default in the game. |
$r? | Region code. The region code is unset. |
| Mods and access | |
^o | Oxide. Plugins are handled by Oxide (uMod). |
^z | Modded. Modded listing: plugins or settings modify the game. |
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.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.