Working its way up from the back of the class: #15,324 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 170 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
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.
usual gap0.3 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Fri 16 OctFri 16 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 15 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 15:35 UTC13d ago
1
–
running
0
Fri 16 Oct, 08:20 UTC13d ago
1
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
No region is published for Tribunal_Isolated_Dev. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 119.105.5.171:28915.
How reliable is Tribunal_Isolated_Dev, and is it up?
At this moment, Tribunal_Isolated_Dev is offline; the last time it was seen was 11 days 20 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 16 October 2026, Rust Server Score saw it for the first time.
On what Rust version does Tribunal_Isolated_Dev sit?
Rust network protocol 2634 and build 167781 on Windows is what Tribunal_Isolated_Dev runs. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does Tribunal_Isolated_Dev wipe its map?
There are too few wipes on record for Tribunal_Isolated_Dev to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 13 days 7 hours have passed since this world was made.
What should you expect from wipe day on Tribunal_Isolated_Dev?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 15 hours after it began.
Population
What position does Tribunal_Isolated_Dev hold in the rankings?
In the top 70% of all ranked servers, Tribunal_Isolated_Dev sits at #15,324 for player hours over the last seven days.
What does the population on Tribunal_Isolated_Dev look like?
It has been 11 days 20 hours since Tribunal_Isolated_Dev was last seen, and it is offline right now.
Tags
What do Tribunal_Isolated_Dev's tags stand for?
You'll see Tribunal_Isolated_Dev tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp8 (Max players): 8 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): This runs on build 167781; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which Rust Server Score filters and lists feature Tribunal_Isolated_Dev?
These Rust Server Score lists count Tribunal_Isolated_Dev among them: Modded Rust servers, graded. It shows under the following filters 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.
Rules and settings
How is Tribunal_Isolated_Dev set up, and what rules does it keep?
The name of Tribunal_Isolated_Dev gives no gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. VAC, Valve's anti-cheat, is enabled.
Getting in
How do you get onto Tribunal_Isolated_Dev?
To connect, start Rust, press F1, and type client.connect 119.105.5.171:28915. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp8,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp8
Max players8 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: Carbon.
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).