Offline 140.225.208.60:28015 checked 28d ago
MR14 Future Map Test
Connect
srv = rust.server("140.225.208.60: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 best
Top 69% 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 6d 17h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 17h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 34d 17h | 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 19:00 UTC FW28d ago | 0 | NaN | running | 1 |
# 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
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 140.225.208.60:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 19:00 UTC
- hostname
- –
- first seen
- 1 Oct 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 491 on average | 84/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 115/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 284 on average | 397/450 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 277 on average | 21/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 266 on average | 476/525 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 253 on average | 362/425 |
Quick answers
From the figures on this page.
Population data
How does MR14 Future Map Test compare in the rankings?
Player hours over seven days put MR14 Future Map Test at #16,032, in the top 69% of the ranked set.
What population does MR14 Future Map Test carry?
MR14 Future Map Test returns no live count at this refresh, having last been seen 28 days 5 hours ago.
Server facts
Which Rust version is MR14 Future Map Test on?
Rust network protocol 2634 and build 166494 on Windows is what MR14 Future Map Test runs. Steam updates your game for you, but the protocol must match to join.
How reliable is MR14 Future Map Test, and is it online now?
MR14 Future Map Test is offline at this refresh; the last response came 28 days 5 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 1 October 2026.
Which location does MR14 Future Map Test run from?
There is no region published for MR14 Future Map Test. 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 140.225.208.60:28015.
Rules, settings, map
What rules and settings are recorded for MR14 Future Map Test?
You will not find a gather rate in the string MR14 Future Map Test. The group limit sits at the default of 8 players. Recorded as survival, the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Community is its browser category. VAC, Valve's anti-cheat, is enabled.
Wipes and dates
On what schedule does MR14 Future Map Test wipe?
Once a month MR14 Future Map Test wipes, with the 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 28 days 6 hours ago.
On MR14 Future Map Test, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Which lists on Rust Data hold MR14 Future Map Test, and which filters?
The Rust Data lists that MR14 Future Map Test fits are: Rust community servers, unfiltered. It appears under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on MR14 Future Map Test hold?
These tags are published by MR14 Future Map Test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way to join MR14 Future Map Test?
In Rust, F1 opens the console: type client.connect 140.225.208.60:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.