Offline 119.105.5.171:28915 checked 11d ago
Tribunal_Isolated_Dev
Connect
srv = rust.server("119.105.5.171:28917")
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 1, 15 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 16 Oct, 15:35 UTC13d ago | 1 | NaN | running | 0 |
| 1 | Fri 16 Oct, 08:20 UTC13d ago | 1 | NaN | 0.3 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.
display(srv.map, srv.info())
Map
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 119.105.5.171:28915
- region
- –
- max players
- 8
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 16 Oct 2026, 15:35 UTC
- hostname
- –
- first seen
- 16 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 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 62/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 121/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 112/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 36/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 119/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 347/350 |
Quick answers
From the figures on this page.
Population
How does Tribunal_Isolated_Dev compare in the rankings?
Over the last seven days Tribunal_Isolated_Dev sits at #15,324 on player hours, in the top 70% of ranked servers.
What population does Tribunal_Isolated_Dev carry?
Tribunal_Isolated_Dev returns no live count at this refresh, having last been seen 11 days 19 hours ago.
Server data
Which Rust version is Tribunal_Isolated_Dev on?
The build is Rust network protocol 2634 and build 167781 on Windows, run by Tribunal_Isolated_Dev. The protocol has to match before you can join, and Steam does the updating.
Is Tribunal_Isolated_Dev up, and what does its uptime show?
Tribunal_Isolated_Dev is offline at this refresh; the last response came 11 days 19 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 16 October 2026.
Where does Tribunal_Isolated_Dev sit?
There is no region published for Tribunal_Isolated_Dev. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 119.105.5.171:28915.
Rules, settings, map
Which rules apply on Tribunal_Isolated_Dev, and what settings?
The name Tribunal_Isolated_Dev carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the base game, where you gather, build and raid. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
Wipe schedule
On what schedule does Tribunal_Isolated_Dev wipe?
A rhythm cannot be read from the wipes of Tribunal_Isolated_Dev on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 13 days 5 hours ago, and that is the one in play.
What is wipe day on Tribunal_Isolated_Dev like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 15 hours after it began.
Tags and filters
Where does Tribunal_Isolated_Dev appear among Rust Data lists and filters?
On Rust Data, Tribunal_Isolated_Dev appears in these lists: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Which meanings do the tags on Tribunal_Isolated_Dev hold?
Read by the game's server browser, the tags Tribunal_Isolated_Dev publishes are: gmrust (Game mode): Rust survival in its standard form; mp8 (Max players): The server lists 8 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): Recorded game build: 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join Tribunal_Isolated_Dev?
The manual route: launch Rust, F1, then client.connect 119.105.5.171:28915. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.