Telegram RegisterThe public register of Telegram
Telegram profile photo for 𓆩 مَـدار 𓆪

Channel

𓆩 مَـدار 𓆪

@aso_20a_16

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

2,987subscribers

-2,075 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002918959595
TypeChannel
Username@aso_20a_16
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live12 October 2026
Measurements held14
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/aso_20a_16

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

2,9875,0624,024.59 August 2026 — 5,062 subscribers16 August 2026 — 5,061 subscribers23 August 2026 — 5,053 subscribers26 August 2026 — 4,958 subscribers29 August 2026 — 4,842 subscribers1 September 2026 — 4,750 subscribers2 September 2026 — 4,750 subscribers6 September 2026 — 4,605 subscribers11 September 2026 — 4,447 subscribers14 September 2026 — 4,370 subscribers18 September 2026 — 4,237 subscribers27 September 2026 — 3,947 subscribers5 October 2026 — 3,506 subscribers12 October 2026 — 2,987 subscribers9 August 202612 October 2026
14 measurements spanning 64 days, net -2,075. 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 2,676–5,373 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 12:442,987-519
5 Oct 2026, 19:163,506-441
27 Sept 2026, 21:583,947-290
18 Sept 2026, 16:364,237-133
14 Sept 2026, 13:394,370-77
11 Sept 2026, 03:374,447-158
6 Sept 2026, 07:594,605-145
2 Sept 2026, 12:574,750no change
1 Sept 2026, 21:054,750-92
29 Aug 2026, 21:464,842-116
26 Aug 2026, 11:124,958-95
23 Aug 2026, 16:035,053-8
16 Aug 2026, 20:255,061-1
9 Aug 2026, 16:025,062first 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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“𓆩 مَـدار 𓆪” (@aso_20a_16), 2,987 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/aso_20a_16.

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.