Channel
_𝐡03𝐢𝐞𝐧𝐨
@hO3ieno
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,779subscribers
+23 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001578717312 |
|---|---|
| Type | Channel |
| Username | @hO3ieno |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/hO3ieno |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 13 Sept 2026, 07:21 | 2,779 | +12 |
| 13 Sept 2026, 01:29 | 2,767 | no change |
| 9 Sept 2026, 06:17 | 2,767 | +7 |
| 3 Sept 2026, 23:20 | 2,760 | +4 |
| 31 Aug 2026, 10:05 | 2,756 | -2 |
| 28 Aug 2026, 20:23 | 2,758 | -2 |
| 26 Aug 2026, 01:12 | 2,760 | +1 |
| 23 Aug 2026, 00:05 | 2,759 | +3 |
| 22 Aug 2026, 12:15 | 2,756 | 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.
@Majidbazdar_official · 25,261
Telegram ranks this channel #9 of 54 here — alongside 53 others — read 14 September 2026
@mohsenfirouziyan_real · 45,230
Telegram ranks this channel #13 of 74 here — alongside 73 others — read 28 August 2026
@dokht_kongi1 · 77,831
Telegram ranks this channel #28 of 63 here — alongside 62 others — read 22 August 2026
@musicesmaili · 26,617
Telegram ranks this channel #41 of 63 here — alongside 62 others — read 12 September 2026
@hamidrezazakeri_music · 61,815
Telegram ranks this channel #43 of 79 here — alongside 78 others — read 22 August 2026
@MojaMsc · 58,033
Telegram ranks this channel #51 of 60 here — alongside 59 others — read 22 August 2026
@Gamberon_info · 50,963
Telegram ranks this channel #57 of 87 here — alongside 86 others — read 25 August 2026
@momenzadeh_music · 29,272
Telegram ranks this channel #69 of 83 here — alongside 82 others — read 9 September 2026
This channel appears in 8 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“_𝐡03𝐢𝐞𝐧𝐨” (@hO3ieno), 2,779 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/hO3ieno.
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.