Channel
Gym hab | جیم هاب
@gymihub
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,347subscribers
-359 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001681366779 |
|---|---|
| Type | Channel |
| Username | @gymihub |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/gymihub |
Topic
Health & wellness — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 75% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 18:01 | 5,347 | -16 |
| 31 Oct 2026, 04:10 | 5,363 | -16 |
| 28 Oct 2026, 03:57 | 5,379 | -7 |
| 25 Oct 2026, 14:25 | 5,386 | -12 |
| 22 Oct 2026, 10:00 | 5,398 | -15 |
| 18 Oct 2026, 23:08 | 5,413 | -7 |
| 16 Oct 2026, 01:06 | 5,420 | -20 |
| 12 Oct 2026, 15:08 | 5,440 | -24 |
| 5 Oct 2026, 16:56 | 5,464 | -31 |
| 28 Sept 2026, 11:02 | 5,495 | -48 |
| 15 Sept 2026, 19:00 | 5,543 | -10 |
| 11 Sept 2026, 22:01 | 5,553 | -12 |
| 7 Sept 2026, 18:36 | 5,565 | -31 |
| 2 Sept 2026, 10:46 | 5,596 | -5 |
| 30 Aug 2026, 21:31 | 5,601 | no change |
| 30 Aug 2026, 16:35 | 5,601 | -11 |
| 27 Aug 2026, 08:54 | 5,612 | -12 |
| 24 Aug 2026, 14:54 | 5,624 | -11 |
| 20 Aug 2026, 17:25 | 5,635 | -21 |
| 17 Aug 2026, 13:08 | 5,656 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@adidasss021 · 36,231
Telegram ranks this channel #60 of 77 here — alongside 76 others — read 1 September 2026
@Deej_sad · 19,560
Telegram ranks this channel #67 of 77 here — alongside 76 others — read 3 October 2026
@Faze_2sangin · 78,096
Telegram ranks this channel #75 of 78 here — alongside 77 others — read 19 August 2026
@ReMixeeRapY · 44,473
Telegram ranks this channel #76 of 87 here — alongside 86 others — read 28 August 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total, of which the 4 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Gym hab | جیم هاب” (@gymihub), 5,347 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/gymihub.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.