Channel
بۆکانی پۆست🤍
@hid8k
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,790subscribers
+178 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001240997111 |
|---|---|
| Type | Channel |
| Username | @hid8k |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/hid8k |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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 |
|---|---|---|
| 8 Nov 2026, 22:46 | 1,790 | +15 |
| 5 Nov 2026, 06:18 | 1,775 | +7 |
| 2 Nov 2026, 09:18 | 1,768 | +2 |
| 27 Oct 2026, 04:48 | 1,766 | +11 |
| 23 Oct 2026, 19:37 | 1,755 | +2 |
| 21 Oct 2026, 03:38 | 1,753 | +15 |
| 18 Oct 2026, 01:48 | 1,738 | +11 |
| 14 Oct 2026, 15:56 | 1,727 | +7 |
| 11 Oct 2026, 11:42 | 1,720 | +5 |
| 4 Oct 2026, 17:58 | 1,715 | +13 |
| 25 Sept 2026, 04:02 | 1,702 | +30 |
| 25 Sept 2026, 02:16 | 1,672 | no change |
| 17 Sept 2026, 01:18 | 1,672 | +24 |
| 13 Sept 2026, 02:20 | 1,648 | +4 |
| 9 Sept 2026, 11:36 | 1,644 | +1 |
| 4 Sept 2026, 04:01 | 1,643 | +6 |
| 1 Sept 2026, 00:18 | 1,637 | +1 |
| 28 Aug 2026, 12:53 | 1,636 | +12 |
| 25 Aug 2026, 05:22 | 1,624 | +2 |
| 22 Aug 2026, 13:16 | 1,622 | 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.
@AwatPage · 84,891
Telegram ranks this channel #8 of 59 here — alongside 58 others — read 18 August 2026
@Awatbokani_org · 26,105
Telegram ranks this channel #9 of 32 here — alongside 31 others — read 15 September 2026
@alihawraz · 57,554
Telegram ranks this channel #14 of 43 here — alongside 42 others — read 15 September 2026
@Rahmatazary · 33,021
Telegram ranks this channel #33 of 77 here — alongside 76 others — read 7 September 2026
@photographicposts · 39,949
Telegram ranks this channel #37 of 56 here — alongside 55 others — read 29 August 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“بۆکانی پۆست🤍” (@hid8k), 1,790 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/hid8k.
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.