Offline 171.233.112.105:28015 checked 12d ago
TIRIFY Public Test
Connect
srv = rust.server("171.233.112.105:28017")
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 best
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 17 Oct, 01:57 UTC12d ago | 0 | NaN | 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 171.233.112.105:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 17 Oct 2026, 01:57 UTC
- hostname
- –
- first seen
- 17 Oct 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 512 on average | 341/400 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 317 on average | 449/500 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 280 on average | 974/1000 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 276 on average | 48/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 265 on average | 992/1000 |
| 5 | Rustoria.co - US Main | NA · groups of 16+ · weekly · 235 on average | 52/250 |
Quick answers
From the figures on this page.
Population data
How does TIRIFY Public Test compare in the rankings?
Rank #15,202 on seven-day player hours for TIRIFY Public Test, within the top 70% of all ranked servers.
How many players does TIRIFY Public Test hold at once?
Offline now for TIRIFY Public Test, with the last sample 12 days 15 hours ago.
Server facts
Which Rust version is TIRIFY Public Test on?
Version Rust network protocol 2634 and build 167781 on Windows is reported by TIRIFY Public Test. The protocol has to match before you can join, and Steam does the updating.
Is TIRIFY Public Test up, and what does its uptime show?
The latest sample has TIRIFY Public Test offline, with a last sighting 12 days 15 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Rust Data logged it first on 17 October 2026.
In which location is TIRIFY Public Test hosted?
For TIRIFY Public Test, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 171.233.112.105:28015.
Rules, settings, map
Which settings and rules does TIRIFY Public Test run?
No gather rate appears in the name: TIRIFY Public Test. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Combat and raiding between players: both allowed. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.
Which map has TIRIFY Public Test loaded?
The game generates its map: procedural, on TIRIFY Public Test.
Wipe data
On what schedule does TIRIFY Public Test wipe?
The record for TIRIFY Public Test holds too few wipes to show a rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 12 days 16 hours ago, and that is the one in play.
On TIRIFY Public Test, what happens on wipe day?
The average peak over recent wipes is 0 players. 0 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does TIRIFY Public Test appear among Rust Data lists and filters?
These Rust Data lists include TIRIFY Public Test: Rust community servers, unfiltered. It appears under these filters 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.
How should you read the server tags on TIRIFY Public Test?
These tags are published by TIRIFY Public Test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): The server lists 5 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): To join, your game must run protocol 2634; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into TIRIFY Public Test?
Enter client.connect 171.233.112.105:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.