Telegram RegisterThe public register of Telegram
Telegram profile photo for أ . سَـارا

Channel

أ . سَـارا

@ablas4

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

7,432subscribers

-119 since we began measuring on 10 September 2026

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

Register entry

Telegram ID-1001635125077
TypeChannel
Username@ablas4
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 September 2026
Last confirmed live2 November 2026
Measurements held13
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/ablas4

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

7,4327,5517,491.510 September 2026 — 7,551 subscribers10 September 2026 — 7,551 subscribers12 September 2026 — 7,542 subscribers16 September 2026 — 7,525 subscribers28 September 2026 — 7,491 subscribers6 October 2026 — 7,484 subscribers12 October 2026 — 7,473 subscribers15 October 2026 — 7,459 subscribers18 October 2026 — 7,453 subscribers21 October 2026 — 7,443 subscribers24 October 2026 — 7,440 subscribers30 October 2026 — 7,436 subscribers2 November 2026 — 7,432 subscribers10 September 20262 November 2026
13 measurements spanning 53 days, net -119. 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 7,414–7,569 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Nov 2026, 14:097,432-4
30 Oct 2026, 22:277,436-4
24 Oct 2026, 23:597,440-3
21 Oct 2026, 16:077,443-10
18 Oct 2026, 13:447,453-6
15 Oct 2026, 21:177,459-14
12 Oct 2026, 14:317,473-11
6 Oct 2026, 00:217,484-7
28 Sept 2026, 11:217,491-34
16 Sept 2026, 01:197,525-17
12 Sept 2026, 07:197,542-9
10 Sept 2026, 13:227,551no change
10 Sept 2026, 12:477,551first reading

Engagement

No public post preview. We read this entry on 3 November 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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

“أ . سَـارا” (@ablas4), 7,432 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/ablas4.

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.