Offline 188.27.146.206:28515 checked 43d ago
TIR Hotspot Profiler Diagnostic
Connect
srv = rust.server("188.27.146.206:28516")
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 bestWipe 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 188.27.146.206:28515
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 15 Sep 2026, 14:15 UTC
- hostname
- –
- first seen
- 16 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 | 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.
Population
How does TIR Hotspot Profiler Diagnostic compare in the rankings?
Over the last seven days TIR Hotspot Profiler Diagnostic sits at #15,497 on player hours, in the top – of ranked servers.
How many players does TIR Hotspot Profiler Diagnostic hold at once?
TIR Hotspot Profiler Diagnostic returns no live count at this refresh, having last been seen 43 days 5 hours ago.
Server data
Which Rust version is TIR Hotspot Profiler Diagnostic on?
Rust network protocol 2633 and build 163794 on Windows is what TIR Hotspot Profiler Diagnostic runs. Joining needs the same protocol on your game; Steam handles the update.
Is TIR Hotspot Profiler Diagnostic up, and what does its uptime show?
The latest sample has TIR Hotspot Profiler Diagnostic offline, with a last sighting 43 days 5 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 16 September 2026.
In which location is TIR Hotspot Profiler Diagnostic hosted?
No region is published by TIR Hotspot Profiler Diagnostic. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 188.27.146.206:28515 is its address.
Rules, settings, map
Which settings and rules does TIR Hotspot Profiler Diagnostic run?
You will not find a gather rate in the string TIR Hotspot Profiler Diagnostic. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Carbon. VAC, Valve's anti-cheat, is enabled.
What is the map on TIR Hotspot Profiler Diagnostic?
The game generates its map: procedural, on TIR Hotspot Profiler Diagnostic.
Wipe data
When does TIR Hotspot Profiler Diagnostic wipe, and on what schedule?
A rhythm cannot be read from the wipes of TIR Hotspot Profiler Diagnostic on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 44 days 4 hours ago, and that is the one in play.
Tags and filters
Where does TIR Hotspot Profiler Diagnostic appear among Rust Data lists and filters?
These Rust Data lists include TIR Hotspot Profiler Diagnostic: 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.
How should you read the server tags on TIR Hotspot Profiler Diagnostic?
Read by the game's server browser, the tags TIR Hotspot Profiler Diagnostic publishes are: gmrust (Game mode): Rust survival in its standard form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Team limit of 8, as shipped by default; v2633 (Protocol): To join, your game must run protocol 2633; cs163794 (Build): Build number: 163794; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): The region field is empty; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Plugin framework: 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
What is the way to join TIR Hotspot Profiler Diagnostic?
Enter client.connect 188.27.146.206:28515 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.