Rust Server Analytics 48,284 players11,675 servers
All servers
Drill-through Server detail

MTRTEST2

Offline 64.40.8.143:22015 checked 9d ago

Drill-through
FilterServeris MTRTEST2
Attributes
moddedoxide
Last refreshed
Players now 0/ 100
7-day average 0 peak –
Rank #15,247 top 69%
Last wipe 11d ago no schedule published
Next wipe – no rhythm it keeps
Capacity 0% full

Players

average and peak, with its wipes marked
No hourly history yet.

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
This server has not answered a direct query in the last 48 hours.

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
RankRank in region
15k10k15k20k20 Sep24 Sep28 Sep17 Oct21 Oct25 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

Wipe schedule

no rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

usual gap1.1 daysbetween real wipes
on rhythm67%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1

The first 48 hours of its last wipes

Fri 16 OctThu 15 OctSun 20 Sep
00.511.52+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 2, 34 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 03:30 UTC11d ago 2 – running 1
Thu 15 Oct, 00:52 UTC13d ago 3 – 1.1 days 0
Sun 20 Sep, 15:40 UTC37d ago 2 halved by day 1 24.4 days 0
Sat 19 Sep, 15:41 UTC38d ago 14+3 queue – 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
ServerProfilePlayers now
ShockRust | Blue | NoLimit no group limit · 162 on average 35 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 EU · groups of 8+ · weekly · 128 on average 128 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 114 on average 50 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 87 on average 39 / 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 87 on average 7 / 200
CSL Scenery Budget Test groups of 8+ · 85 on average 0 / 500

Quick answers

from the figures on this page

Wipe data

The wipe schedule for MTRTEST2: what is it?

No next wipe can be predicted for MTRTEST2, which wipes at irregular times. The next force wipe, which every Rust server receives, is on Thursday 5 November at 19:00 UTC. The world now in play was created 11 days 19 hours ago.

On MTRTEST2, what happens on wipe day?

Recent wipes averaged a busiest count of 2 players. The highest player count on the latest wipe arrived 34 hours in. Above half that peak until the next wipe held in 0% of recent wipes. By day 1 it had fallen below half where the hold failed.

Server

Which location hosts MTRTEST2?

A region is not published by MTRTEST2. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. 64.40.8.143:22015 is its address.

What Rust build does MTRTEST2 run?

On Linux, MTRTEST2 runs Rust network protocol 2634 and build 167781. Your game must match the protocol to join, and Steam applies that update.

What uptime does MTRTEST2 show, and is it up?

Offline at this refresh: MTRTEST2, last seen 9 days 5 hours ago. Uptime over the last full days (7) was 0%, or 0 of 168 hours. It entered Rust Server Analytics records on 18 September 2026.

Tags

Which meanings do the tags on MTRTEST2 carry?

The game's server browser reads the tags MTRTEST2 publishes: gmvanilla (Game mode): Vanilla ruleset survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default team size of 8; v2634 (Protocol): Protocol 2634 is required: your game must match to connect; cs167781 (Build): Game build: 167781; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^o (Oxide): The Oxide (uMod) plugin framework is installed; ^z (Modded): The Modded section, because plugins or settings modify play. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

On Rust Server Analytics, which lists and filters feature MTRTEST2?

These Rust Server Analytics lists include MTRTEST2: Modded Rust servers: live data. On the server list, the filters that return it are: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player numbers

Where does MTRTEST2 sit among Rust servers?

The seven-day player-hours rank for MTRTEST2 is #15,247, inside the top 69% of all ranked servers.

How many players does MTRTEST2 carry?

MTRTEST2 is offline at this refresh; the last contact was 9 days 5 hours ago.

Settings

How is MTRTEST2 configured, and what rules apply?

The name of MTRTEST2 does not state a gather rate. The game's default 8-player group limit is in force. It runs survival, the standard game: gather, build, raid. Raiding and PvP combat are available. In the server browser it sits under Modded, where plugins or settings alter the game. Plugins from Oxide are in use. Anti-cheat status: VAC on.

Connection

How can a player join MTRTEST2?

In the Rust console (F1), enter client.connect 64.40.8.143:22015. Launch Rust on this page also works, opening Rust through Steam and connecting you.

Server tags

what each one means

Published as mp100,ptrak,$r?,v2634,gmvanilla,cs167781,ts8,^o^z

Game

gmvanilla
Game mode Vanilla ruleset survival.
mp100
Max players 100 slots in total.
ts8
Group limit Default team size of 8.
v2634
Protocol Protocol 2634 is required: your game must match to connect.
cs167781
Build Game build: 167781.
ptrak
Networking RakNet is the network layer, the game's standard one.
$r?
Region code No region code has been set.

Mods and access

^o
Oxide The Oxide (uMod) plugin framework is installed.
^z
Modded The Modded section, because plugins or settings modify play.

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.