RUST METRICSFlight deck · live data
Data live Servers11,685 Players51,425 Populated3,180 Fresh wipes 3 h127 Scan5 min
‹ All servers64.40.8.143:21015
Offline Full Queue Fresh wipe Wipe due No query

MTRTEST

Offline 64.40.8.143:21015 checked 14d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 2 /1

Players now

200% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#11,503top 53%
Last wipe15d agono schedule published
Next wipe–no rhythm it keeps
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep26 Sep2 Oct9 Oct15 Oct21 Oct

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

PLAN

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 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak2players, last three wipes

The first 48 hours of its last wipes

Wed 14 OctTue 13 OctMon 12 Oct
00.511.52+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 14 Oct, 07:44 UTC15d ago 2 – running 2
Tue 13 Oct, 17:29 UTC15d ago 2 – 0.6 days 2
Mon 12 Oct, 10:31 UTC16d ago 2 – 1.3 days 1
Sun 11 Oct, 15:51 UTC17d ago 3 – 0.8 days 3
Sun 11 Oct, 03:04 UTC18d ago 3 – 0.5 days 0
Fri 9 Oct, 21:46 UTC19d ago 3 – 1.2 days 1
Tue 6 Oct, 19:47 UTC22d ago 2 held half 3.1 days 2
Thu 1 Oct, 22:36 UTC FW27d ago 1 held half 4.9 days 1
Thu 1 Oct, 01:33 UTC28d ago 2 – 0.9 days 1
Tue 29 Sep, 06:01 UTC30d ago 2 – 1.8 days 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What should you expect from wipe day on MTRTEST?

The busiest point of its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 0 hours in.

When does MTRTEST wipe?

There is no next wipe to predict: MTRTEST wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 15 days ago.

Tags

Which tags does MTRTEST carry, and what do they mean?

These are the tags MTRTEST publishes, and the server browser reads them: gmvanilla (Game mode): Survival on vanilla settings; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167584 (Build): Build 167584; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does MTRTEST appear in Rust Metrics lists and filters?

On Rust Metrics, MTRTEST sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does MTRTEST sit in the rankings?

Ranking for MTRTEST: #11,503 on seven-day player hours, top 53% of all ranked servers.

What is the population on MTRTEST?

Status for MTRTEST: offline. Last seen 14 days 21 hours ago.

Server details

Which location does MTRTEST run from?

No region tag on MTRTEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 64.40.8.143:21015.

What Rust version is MTRTEST on?

Rust network protocol 2634 and build 167584 on Linux is the build MTRTEST runs. Matching protocol is required to join. Let Steam update your game.

Is MTRTEST up, and how often does it stay up?

Check: connection. MTRTEST is offline at this moment. Last contact was 14 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.

Map and rules

What rules does MTRTEST enforce, and what are its settings?

Check: gather rate. The name MTRTEST does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Connection

How do you connect to MTRTEST?

Check: join. Open Rust, press F1, then enter client.connect 64.40.8.143:21015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmvanilla,cs167584,ts8,^o^z

Game

gmvanilla
Game mode Survival on vanilla settings.
mp1
Max players The server holds 1 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167584
Build Build 167584.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^z
Modded Check: category. Modded, because plugins or settings alter 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.