Working its way up from the back of the class: #16,011 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 415 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.
No daily history yet.
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
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
In what location does TIER.ID | Internal Competitive sit?
No region is published for TIER.ID | Internal Competitive. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 82.194.22.117:28015.
How reliable is TIER.ID | Internal Competitive, and is it up?
You cannot join now: TIER.ID | Internal Competitive is offline, last seen 25 days 22 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 3 October 2026, Rust Server Score saw it for the first time.
On what Rust version does TIER.ID | Internal Competitive sit?
The server TIER.ID | Internal Competitive is on Rust network protocol 2634 and build 166494 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does TIER.ID | Internal Competitive reset?
There are too few wipes on record for TIER.ID | Internal Competitive to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 26 days.
Population
Where does TIER.ID | Internal Competitive place in the wider field of Rust servers?
In the top 70% of all ranked servers, TIER.ID | Internal Competitive sits at #16,011 for player hours over the last seven days.
How many players does TIER.ID | Internal Competitive usually have?
The last sighting of TIER.ID | Internal Competitive was 25 days 22 hours ago, and it is offline right now.
Tags and filters
What is meant by the tags on TIER.ID | Internal Competitive?
gmrust (Game mode): Rust survival, played by the standard rules; mp1000 (Max players): 1,000 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166494 (Build): Build number: 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags TIER.ID | Internal Competitive publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does TIER.ID | Internal Competitive appear in the Rust Server Score lists and filters?
Rust Server Score lists that include TIER.ID | Internal Competitive: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Rules and settings
How is TIER.ID | Internal Competitive set up, and what rules does it keep?
You will find no gather rate in the name of TIER.ID | Internal Competitive. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Connecting
How do you get onto TIER.ID | Internal Competitive?
Enter client.connect 82.194.22.117:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp1000,ptrak,$r?,v2634,gmrust,cs166494,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1000
Max players1,000 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166494
BuildBuild number: 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonThe plugin framework in use is 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).