RUST METRICSFlight deck · live data
Data live Servers11,824 Players88,321 Populated3,715 Fresh wipes 3 h404 Scan5 min
‹ All servers42.117.242.54:28015
Offline Full Queue Fresh wipe Wipe due No query

TIRIFY LastMonth Test

Offline 42.117.242.54:28015 checked 12d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 0 /5

Players now

0% 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#15,228top 70%
Last wipe12d agono schedule published
Next wipe–too few wipes seen yet
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
15k10k15k20k17 Oct18 Oct20 Oct21 Oct23 Oct24 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 01:03 UTC12d ago 0 – 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.

ALTN

Similar servers

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

Quick answers

from the figures on this page

Wipe timing

What happens on TIRIFY LastMonth Test when wipe day comes?

At their busiest, its recent wipes drew 0 players on average. After the latest wipe, numbers topped out at 0 hours.

When does TIRIFY LastMonth Test wipe?

The rhythm of TIRIFY LastMonth Test's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 12 days 20 hours ago.

Tag meanings

Which tags does TIRIFY LastMonth Test carry, and what do they mean?

These are the tags TIRIFY LastMonth Test publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs165217 (Build): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show TIRIFY LastMonth Test?

These Rust Metrics lists carry TIRIFY LastMonth Test: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

Where does TIRIFY LastMonth Test sit in the rankings?

Ranking for TIRIFY LastMonth Test: #15,228 on seven-day player hours, top 70% of all ranked servers.

What player count does TIRIFY LastMonth Test carry?

Status for TIRIFY LastMonth Test: offline. Last seen 12 days 20 hours ago.

Operator and location

Where does TIRIFY LastMonth Test sit?

No region comes from TIRIFY LastMonth Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 42.117.242.54:28015.

What Rust version is TIRIFY LastMonth Test on?

Rust network protocol 2633 and build 165217 on Windows is the build TIRIFY LastMonth Test runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is TIRIFY LastMonth Test, and is it online now?

TIRIFY LastMonth Test reports offline. The last reading came 12 days 20 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 17 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on TIRIFY LastMonth Test?

Reading the name gives no gather rate for TIRIFY LastMonth Test. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.

Which map is live on TIRIFY LastMonth Test?

Procedural map on TIRIFY LastMonth Test, made by the game's generator.

How to join

How can you get onto TIRIFY LastMonth Test?

To join: start Rust, press F1 and type client.connect 42.117.242.54:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit Team cap of 8, which is the game default.
v2633
Protocol Match the game version: protocol 2633 is required.
cs165217
Build The server runs game build 165217.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

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.