Telegram RegisterThe public register of Telegram
Telegram profile photo for هوشكا چاكلت

Channel

هوشكا چاكلت

@hooshka

On this record: Topic · Growth · Engagement · Posts · Cite this entry

35subscribers

-1 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-1001105103593
TypeChannel
Username@hooshka
CreatedBetween 1 February 2017 and 5 November 2018 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live7 October 2026
Measurements held3
Confirmed unchanged5 times, most recently 7 October 2026
On Telegramt.me/hooshka

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 30 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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

353635.57 August 2026 — 36 subscribers10 August 2026 — 36 subscribers29 August 2026 — 35 subscribers7 August 202629 August 2026
3 measurements spanning 22 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 35–36 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 09:5435-1
10 Aug 2026, 22:3036no change
7 Aug 2026, 02:1236first reading

Engagement

10 posts held, back to 5 November 2018 — 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 10 posts for this entry, the most recent from 4 October 2021. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Nov 2018, 09:24 UTC200 viewsread 10 August 2026

گرانولا از #جو_دوسر_پرک فرآوری شده با #عسل 🍯 به همراه میوه های خشک یا مغزهای مغذی دانه ها تشکیل شده که به همراه شیر یا ماست یه صبحانه سالم و سلامت رو نتیجه میده 😋💪 شاید سوال داشته باشید که جو دوسر چیه و چه فرقی با جو معمولی داره!؟ 🤔 جو دوسر بسیار مغذی و سالم و با داشتن میزان #پروتئین کمتر تقریبا دو برابر جو معمولی #فیبر داره ✌️ولی تفاوت اساسی این دو در #فاقد#گلوتن بودن جو دوسر هست که محبوبیت این ماده غذایی رو در دنیا…

5 Nov 2018, 16:17 UTC189 viewsread 10 August 2026

ویفر شکلات سوییسی کاجی در 5 طعم 😋

Showing the 10 most recent of 10 posts we hold for @hooshka. 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 29 August 2026 — this entry's latest reading, not the date you are reading this.

“هوشكا چاكلت” (@hooshka), 35 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/hooshka.

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.