Channel
HB
@hamibabajanii_org
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,327subscribers
+16 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001440315231 |
|---|---|
| Type | Channel |
| Username | @hamibabajanii_org |
| Description | 🎖️کانال رسمی " #حامی_باباجانی🎹 🔻ارتباط با مدیر🔻 👨🏻💻 @AbolfazlLotfix |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| On Telegram | t.me/hamibabajanii_org |
Topic
Other / unclassifiable — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 14:35 | 2,327 | no change |
| 17 Sept 2026, 07:17 | 2,327 | +29 |
| 13 Sept 2026, 06:38 | 2,298 | +11 |
| 9 Sept 2026, 15:56 | 2,287 | +46 |
| 4 Sept 2026, 06:41 | 2,241 | -6 |
| 31 Aug 2026, 13:58 | 2,247 | -12 |
| 28 Aug 2026, 10:23 | 2,259 | -2 |
| 25 Aug 2026, 01:35 | 2,261 | -13 |
| 21 Aug 2026, 05:27 | 2,274 | -6 |
| 17 Aug 2026, 20:19 | 2,280 | -7 |
| 14 Aug 2026, 19:46 | 2,287 | -11 |
| 11 Aug 2026, 04:46 | 2,298 | -9 |
| 8 Aug 2026, 09:44 | 2,307 | -4 |
| 7 Aug 2026, 11:01 | 2,311 | 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.
@vahid_moradi_amoli · 23,489
Telegram ranks this channel #2 of 76 here — alongside 75 others — read 18 September 2026
@kamran_khalilii · 27,593
Telegram ranks this channel #35 of 70 here — alongside 69 others — read 10 September 2026
@mazani_reels · 23,670
Telegram ranks this channel #48 of 82 here — alongside 81 others — read 17 September 2026
@amirbabajanzadeh · 22,427
Telegram ranks this channel #76 of 91 here — alongside 90 others — read 20 September 2026
@Mahankhademi_org · 33,206
Telegram ranks this channel #92 of 93 here — alongside 92 others — read 4 September 2026
This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“HB” (@hamibabajanii_org), 2,327 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/hamibabajanii_org.
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.