Offline 82.194.22.117:28015 checked 26d ago
TIER.ID | Internal Competitive
Connect
srv = rust.server("82.194.22.117:65000")
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
srv.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
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
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, 14:34 UTC
- hostname
- –
- first seen
- 3 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 · 151 on average | 127/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 195/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 95 on average | 74/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 89 on average | 222/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 84 on average | 348/350 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does TIER.ID | Internal Competitive rank?
Rank #16,011 on seven-day player hours for TIER.ID | Internal Competitive, within the top 70% of all ranked servers.
What population does TIER.ID | Internal Competitive carry?
TIER.ID | Internal Competitive returns no live count at this refresh, having last been seen 26 days 2 hours ago.
Server facts
Which Rust version is TIER.ID | Internal Competitive on?
Rust network protocol 2634 and build 166494 on Linux is what TIER.ID | Internal Competitive runs. Joining needs the same protocol on your game; Steam handles the update.
Is TIER.ID | Internal Competitive up, and what does its uptime show?
TIER.ID | Internal Competitive is offline at this refresh; the last response came 26 days 2 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. The first row Rust Data holds for it is dated 3 October 2026.
In which location is TIER.ID | Internal Competitive hosted?
For TIER.ID | Internal Competitive, no region is published. 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
What rules and settings are recorded for TIER.ID | Internal Competitive?
You will not find a gather rate in the string TIER.ID | Internal Competitive. The group limit sits at the default of 8 players. Recorded as survival, the usual game, with gathering, building and raiding. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Carbon plugins run on it. VAC, Valve's anti-cheat, is enabled.
Wipe schedule
When does TIER.ID | Internal Competitive wipe, and on what schedule?
A rhythm cannot be read from the wipes of TIER.ID | Internal Competitive on record, which are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 26 days 4 hours ago.
Tags and filters
Where does TIER.ID | Internal Competitive appear among Rust Data lists and filters?
The Rust Data lists that TIER.ID | Internal Competitive fits are: 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.
Which meanings do the tags on TIER.ID | Internal Competitive hold?
The game's server browser reads these tags from TIER.ID | Internal Competitive: gmrust (Game mode): Survival play, standard Rust; mp1000 (Max players): Slot count: 1,000; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): To join, your game must run protocol 2634; cs166494 (Build): Build number: 166494; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^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 | Internal Competitive?
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.