Offline 37.139.100.131:28015 checked 5d ago
WM3_SERVER
Connect
srv = rust.server("37.139.100.131:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 48% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 12h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 12h | Thu 3 Dec, 19:00 UTC | FW force wipe |
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 21:47 UTC FW27d ago | 2 | NaN | 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- 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
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 59/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 135/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 96/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 31/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 10/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does WM3_SERVER rank?
Player hours over seven days put WM3_SERVER at #10,581, in the top 48% of the ranked set.
How full does WM3_SERVER run?
The current row shows WM3_SERVER offline; the last response was 5 days 8 hours ago. Over the last seven days it averaged 2 players and peaked at 2.
Server data
What Rust version does WM3_SERVER run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by WM3_SERVER. Steam updates your game for you, but the protocol must match to join.
Is WM3_SERVER up, and what does its uptime show?
WM3_SERVER is offline at this refresh; the last response came 5 days 8 hours ago. Over the last 7 full days the hours up number 2 of 168, 1%. Its earliest recorded date in Rust Data is 13 September 2026.
In which location is WM3_SERVER hosted?
There is no region published for WM3_SERVER. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 37.139.100.131:28015.
Settings and map
Which settings and rules does WM3_SERVER run?
You will not find a gather rate in the string WM3_SERVER. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. VAC is not running; Valve's anti-cheat is off.
Which map has WM3_SERVER selected?
A procedural map runs on WM3_SERVER, generated by the game.
Wipes and dates
On what schedule does WM3_SERVER wipe?
The only wipe WM3_SERVER takes is the monthly force wipe. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 27 days 7 hours ago.
What is wipe day on WM3_SERVER like?
The average peak over recent wipes is 2 players. The crowd on the latest wipe topped out 2 hours after it began.
Lists and tags
Where does WM3_SERVER appear among Rust Data lists and filters?
These Rust Data lists include WM3_SERVER: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on WM3_SERVER hold?
These tags are published by WM3_SERVER and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp3 (Max players): Slot count: 3; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into WM3_SERVER?
Enter client.connect 37.139.100.131:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.