RUST METRICSFlight deck · live data
Data live Servers11,738 Players62,312 Populated3,391 Fresh wipes 3 h192 Scan5 min
‹ All servers171.233.112.105:28015
Offline Full Queue Fresh wipe Wipe due No query

TIRIFY Public Test

Offline 171.233.112.105: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,202top 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

01234+0h+9h+19h+28h+38h+47h

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:57 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 schedule

What happens on TIRIFY Public 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 Public Test wipe?

The rhythm of TIRIFY Public Test's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 12 days 9 hours ago.

Tags

How should you read the tags on TIRIFY Public Test?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Build 167781; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set from TIRIFY Public Test. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Where does TIRIFY Public Test appear in Rust Metrics lists and filters?

Rust Metrics lists featuring TIRIFY Public Test: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

What position does TIRIFY Public Test hold among Rust servers?

Player hours over seven days put TIRIFY Public Test at #15,202, in the top 70% of all ranked servers.

How full does TIRIFY Public Test get?

Reading for TIRIFY Public Test: offline at this moment; last seen 12 days 8 hours ago.

Server details

What location is TIRIFY Public Test hosted in?

No region comes from TIRIFY Public Test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 171.233.112.105:28015.

What Rust version is TIRIFY Public Test on?

Rust network protocol 2634 and build 167781 on Windows is the build TIRIFY Public Test runs. Matching protocol is required to join. Let Steam update your game.

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

Reading: offline. TIRIFY Public Test last answered 12 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 17 October 2026.

Map and rules

What settings and rules apply on TIRIFY Public Test?

No gather rate appears in the name: TIRIFY Public Test. 8 players per group, the default value. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.

Which map is live on TIRIFY Public Test?

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

Join

What do you do to join TIRIFY Public Test?

Press F1 in Rust and enter client.connect 171.233.112.105:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players The server holds 5 slots.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Build 167781.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

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.