Offline 64.40.8.143:22015 checked 9d ago
MTRTEST2
Connect
srv = rust.server("64.40.8.143:22017")
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 34 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 03:30 UTC11d ago | 2 | NaN | running | 1 |
| 1 | Thu 15 Oct, 00:52 UTC13d ago | 3 | NaN | 1.1 days | 0 |
| 2 | Sun 20 Sep, 15:40 UTC37d ago | 2 | halved by day 1 | 24.4 days | 0 |
| 3 | Sat 19 Sep, 15:41 UTC38d ago | 14+3 queue | NaN | 1 days | 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
- 64.40.8.143:22015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 05:23 UTC
- hostname
- –
- first seen
- 18 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 · 161 on average | 27/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 134/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 41/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 33/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 9/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 11/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does MTRTEST2 rank?
Player hours over seven days put MTRTEST2 at #15,247, in the top 69% of the ranked set.
How many players does MTRTEST2 hold at once?
The current row shows MTRTEST2 offline; the last response was 9 days 6 hours ago.
Server facts
Which Rust version is MTRTEST2 on?
Version Rust network protocol 2634 and build 167781 on Linux is reported by MTRTEST2. The protocol has to match before you can join, and Steam does the updating.
How reliable is MTRTEST2, and is it up?
Offline now for MTRTEST2, last seen 9 days 6 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Its earliest recorded date in Rust Data is 18 September 2026.
In which location is MTRTEST2 hosted?
No region is published by MTRTEST2. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 64.40.8.143:22015 is its address.
Settings and map
Which rules apply on MTRTEST2, and what settings?
No gather rate appears in the name: MTRTEST2. The group limit sits at the default of 8 players. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. The plugin count is Oxide. VAC is running: Valve's anti-cheat is on.
Wipes and dates
On what schedule does MTRTEST2 wipe?
MTRTEST2 wipes on no fixed rhythm, so there is nothing to predict. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 11 days 20 hours ago.
What is wipe day on MTRTEST2 like?
The average peak over recent wipes is 2 players. Peak population on the latest wipe came 34 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. In the wipes where it did not hold, half was lost by day 1.
Lists and tags
Where does MTRTEST2 appear among Rust Data lists and filters?
The Rust Data lists that MTRTEST2 fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the server tags on MTRTEST2?
Read by the game's server browser, the tags MTRTEST2 publishes are: gmvanilla (Game mode): Game mode: vanilla survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. 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 to join MTRTEST2?
In Rust, F1 opens the console: type client.connect 64.40.8.143:22015. Launch Rust on this page does the same by opening the game through Steam and connecting.