TIER.ID
Offline 82.194.24.233:28015 checked 9d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 72% of all ranked servers. Ranked on player hours over the last seven days.
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
the same kind of game, then region, group limit, rate and wipes
- 283/ 350
- 25/ 400
- 19/ 400
- 1/ 400
- 14/ 50
- 5/ 200
Quick answers
Tags and filters
Where does TIER.ID appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry TIER.ID are: Modded Rust servers and Rust aim training servers. Its entry appears under the filters Type: Modded; Server tag: Minigames ^e, Combat training ^d, Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the tags on TIER.ID?
The server browser shows these tags for TIER.ID: gmrust (Game mode): Survival, as standard Rust does it; mp1000 (Max players): The slot count is 1,000; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): To join, your game has to be on protocol 2634; cs167231 (Build): This server runs build 167231; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set; ^e (Minigames): Minigames here include arenas, Bedwars and parkour; ^d (Combat training): Loot is supplied so you can work on aim and PvP; ^z (Modded): Plugins or settings make changes, so it's listed as Modded; ^y (Carbon): Carbon is the plugin framework it uses. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
About the server
What location is TIER.ID in?
No region comes from TIER.ID. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 82.194.24.233:28015.
What's the uptime like for TIER.ID?
The server TIER.ID is not reachable at the moment; the last sighting was 9 days 12 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. Rust Going Deep has had it on record since 8 October 2026.
What Rust version is TIER.ID on?
On Linux, TIER.ID runs Rust network protocol 2634 and build 167231. Steam handles the update; you just need your game on the matching protocol to join.
Wipe info
What schedule does TIER.ID follow for wipes?
Too few wipes are on record for TIER.ID to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. 14 days 14 hours is how long ago this world came into being.
Map and rules
Which rules and settings is TIER.ID running?
Its name does not state a gather rate for TIER.ID. 8 players is the group cap, the game's default. It runs minigames & battle royale, battle royale, parkour, arenas, Bedwars. The server browser puts it under Modded, as plugins or settings alter the game. Plugins in use: Carbon. VAC is on: Valve's anti-cheat is active.
Player stats
Is TIER.ID busy?
The last sighting of TIER.ID was 9 days 12 hours ago; it is offline right now.
What's TIER.ID's rank among Rust servers?
For player hours in the last seven days, TIER.ID ranks #15,848, within the top 72% of ranked servers.
Join info
What's the process to join TIER.ID?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 82.194.24.233:28015.