Offline 82.194.22.117:28015 checked 24d ago
TIER.ID
Connect
srv = rust.server("82.194.22.117:28016")
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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 13:16 UTC25d ago | 1 | NaN | running | 1 |
| 1 | Fri 2 Oct, 11:39 UTC26d ago | 1 | NaN | 1.1 days | 1 |
| 2 | Thu 1 Oct, 18:43 UTC FW27d ago | 1 | NaN | 0.7 days | 1 |
| 3 | Thu 1 Oct, 08:38 UTC27d ago | 1 | NaN | 0.4 days | 1 |
| 4 | Wed 30 Sep, 21:45 UTC28d ago | 1 | NaN | 0.5 days | 1 |
# 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
- 82.194.22.117:28015
- region
- –
- max players
- 1000
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 13:16 UTC
- hostname
- –
- first seen
- 30 Sep 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 | RustReborn.gg EU - Bedwars | AimTrain | Creative | Arena | FFA | EU · no group limit · 724 on average | 364/350 |
| 1 | R2 - Aim training / Matchmaking / Facechecks - RU Main | EU · groups of 12+ · 218 on average | 157/400 |
| 2 | RustGames.gg | Lucky Pillars - EU 1 | EU · groups of 100+ · 83 on average | 20/400 |
| 3 | DOGFIGHT 2 | BATTLEFIELD/HELI/MINI/FFA/MM/AIMTRAINING/PVP | groups of 30+ · weekly · 67 on average | 44/250 |
| 4 | R2 - Aim training / Matchmaking / Facechecks - EU Main | EU · groups of 12+ · 37 on average | 20/400 |
| 5 | [EU] BekerMelk's Bow Aim Training Server | AimTrain | ukNLD | EU · no group limit · 30 on average | 10/50 |
Quick answers
From the figures on this page.
Population data
How does TIER.ID compare in the rankings?
Over the last seven days TIER.ID sits at #13,801 on player hours, in the top 61% of ranked servers.
How full does TIER.ID run?
Offline now for TIER.ID, with the last sample 24 days 8 hours ago.
About the server
Which Rust version is TIER.ID on?
Rust network protocol 2634 and build 166494 on Linux is what TIER.ID runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is TIER.ID, and is it online now?
Offline now for TIER.ID, last seen 24 days 8 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 30 September 2026.
Which location does TIER.ID run from?
There is no region published for TIER.ID. Rust Data does not look up where the machine stands; it shows where a server says it is. 82.194.22.117:28015 is its address.
Map and rules
Which rules apply on TIER.ID, and what settings?
The name TIER.ID carries no gather rate. The group limit sits at the default of 8 players. Game mode minigames & battle royale, with this note: parkour, Bedwars, battle royale, arenas. Modded is the browser category: plugins or settings alter the game. The plugin count is Carbon. Anti-cheat status: VAC on.
Wipe data
When does TIER.ID wipe, and how often?
No next wipe can be predicted for TIER.ID, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 25 days 18 hours ago.
On TIER.ID, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. Peak population on the latest wipe came 0 hours in.
Lists and tags
Where does TIER.ID appear among Rust Data lists and filters?
The Rust Data lists that TIER.ID fits are: Modded Rust servers and Rust aim training servers. These filters bring it up on the server list: Type: Modded; Server tag: Minigames ^e, Combat training ^d, Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on TIER.ID?
Read by the game's server browser, the tags TIER.ID publishes are: gmrust (Game mode): Rust survival in its standard form; mp1000 (Max players): Slot count: 1,000; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Recorded game build: 166494; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^e (Minigames): The format is minigames: arenas, Bedwars, parkour and others; ^d (Combat training): Practise aim and PvP; the loot is provided; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
How can I connect to TIER.ID?
Enter client.connect 82.194.22.117:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.