Telegram RegisterThe public register of Telegram
Telegram profile photo for حواديت تيتة

Channel

حواديت تيتة

@qassas_atfal

Has discussion group

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

6,815subscribers

-46 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001069965328
TypeChannel
Username@qassas_atfal
CreatedBetween 1 September 2016 and 30 June 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 August 2026
Last confirmed live16 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/qassas_atfal

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

6,8156,8616,8385 August 2026 — 6,861 subscribers9 August 2026 — 6,860 subscribers12 August 2026 — 6,855 subscribers15 August 2026 — 6,851 subscribers19 August 2026 — 6,842 subscribers21 August 2026 — 6,836 subscribers25 August 2026 — 6,833 subscribers27 August 2026 — 6,833 subscribers28 August 2026 — 6,832 subscribers31 August 2026 — 6,829 subscribers3 September 2026 — 6,824 subscribers8 September 2026 — 6,820 subscribers12 September 2026 — 6,817 subscribers16 September 2026 — 6,815 subscribers5 August 202616 September 2026
14 measurements spanning 41 days, net -46. 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 6,808–6,868 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 03:586,815-2
12 Sept 2026, 15:006,817-3
8 Sept 2026, 15:206,820-4
3 Sept 2026, 08:446,824-5
31 Aug 2026, 04:446,829-3
28 Aug 2026, 01:476,832-1
27 Aug 2026, 21:046,833no change
25 Aug 2026, 05:126,833-3
21 Aug 2026, 20:086,836-6
19 Aug 2026, 00:346,842-9
15 Aug 2026, 16:186,851-4
12 Aug 2026, 10:386,855-5
9 Aug 2026, 15:116,860-1
5 Aug 2026, 23:016,861first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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 16 September 2026 — this entry's latest reading, not the date you are reading this.

“حواديت تيتة” (@qassas_atfal), 6,815 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/qassas_atfal.

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.