❗️НАДХОДЖЕННЯ 420 CLASSIC / 420 LIGHT / UNITY 2.0 250G/ DEAD HORSE ❗️

Channel
MYHOOKAH.COM.UA
@myhookah
On this record: Topic · Growth · Engagement · Posts · Cite this entry
875subscribers
-20 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001137015827 |
|---|---|
| Type | Channel |
| Username | @myhookah |
| Created | Between 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/myhookah |
Topic
Ecommerce storefront — 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 19 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 12 Oct 2026, 15:01 | 875 | -5 |
| 2 Oct 2026, 10:21 | 880 | -2 |
| 16 Sept 2026, 21:37 | 882 | -4 |
| 8 Sept 2026, 19:19 | 886 | -5 |
| 29 Aug 2026, 11:24 | 891 | -1 |
| 22 Aug 2026, 19:36 | 892 | -1 |
| 16 Aug 2026, 09:07 | 893 | -2 |
| 8 Aug 2026, 01:04 | 895 | no change |
| 7 Aug 2026, 22:30 | 895 | first reading |
Engagement
20 posts held, back to 13 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 23 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
❗️НАДХОДЖЕННЯ 420 CLASSIC / 420 LIGHT / UNITY 2.0 250G/ DEAD HORSE ❗️
❗️НАДХОДЖЕННЯ 420 CLASSIC / 420 LIGHT / UNITY 2.0 250G/ DEAD HORSE ❗️
❗️НАДХОДЖЕННЯ 420 CLASSIC / UNITY 2.0 250G/ DEAD HORSE ❗️
❗️НАДХОДЖЕННЯ 420 CLASSIC / UNITY 2.0 250G/ DEAD HORSE ❗️
❗️НАДХОДЖЕННЯ 420 CLASSIC / UNITY 2.0 250G/ DEAD HORSE ❗️
❗️НАДХОДЖЕННЯ 420 LIGHT / UNITY 2.0 250G❗️
❗️НАДХОДЖЕННЯ 420 CLASSIC / UNITY 2.0 250G/ DEAD HORSE ❗️
❗️ОНОВЛЕННЯ ЦІН ❗️ НА ПОЗИЦІЇ: -420 Classic -420 Light -Unity 2.0
❗️НАДХОДЖЕННЯ 420 CLASSIC / UNITY 2.0 250G/ DEAD HORSE ❗️
❗️РАСПРОДАЖ AZURE BLACK 250G❗️ Оптові ціни для всіх: AZURE BLACK - 1050 грн
❗️РАСПРОДАЖ LAGOM MAIN / NAVI 200G❗️ Ціни нижчі за оптові: -Main 330 грн -Navi 370 грн Кількість обмежена ⏳
Showing the 12 most recent of 20 posts we hold for @myhookah. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“MYHOOKAH.COM.UA” (@myhookah), 875 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/myhookah.
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.