Channel
طعم شیرین ریاضی
@AZvorHB21
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,010subscribers
-5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001121445801 |
|---|---|
| Type | Channel |
| Username | @AZvorHB21 |
| Created | Between 1 June 2017 and 30 April 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 2 times, most recently 5 November 2026 |
| On Telegram | t.me/AZvorHB21 |
Topic
Education — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 07:17 | 2,010 | +2 |
| 30 Oct 2026, 23:40 | 2,008 | +2 |
| 28 Oct 2026, 08:44 | 2,006 | +3 |
| 23 Oct 2026, 03:09 | 2,003 | +2 |
| 20 Oct 2026, 06:45 | 2,001 | +5 |
| 14 Oct 2026, 20:49 | 1,996 | +2 |
| 11 Oct 2026, 05:21 | 1,994 | -3 |
| 4 Oct 2026, 23:40 | 1,997 | +1 |
| 25 Sept 2026, 16:19 | 1,996 | -2 |
| 21 Sept 2026, 01:06 | 1,998 | no change |
| 17 Sept 2026, 00:02 | 1,998 | -2 |
| 9 Sept 2026, 09:56 | 2,000 | -1 |
| 4 Sept 2026, 11:20 | 2,001 | +1 |
| 29 Aug 2026, 05:47 | 2,000 | -3 |
| 26 Aug 2026, 09:27 | 2,003 | -1 |
| 19 Aug 2026, 19:02 | 2,004 | -5 |
| 16 Aug 2026, 18:46 | 2,009 | -2 |
| 13 Aug 2026, 07:18 | 2,011 | -2 |
| 10 Aug 2026, 14:14 | 2,013 | -2 |
| 6 Aug 2026, 17:53 | 2,015 | first 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@riazisara · 27,273
Telegram ranks this channel #1 of 82 here — alongside 81 others — read 4 October 2026
@academyfirooznia · 27,704
Telegram ranks this channel #32 of 60 here — alongside 59 others — read 18 September 2026
@pythoncoder92 · 71,478
Telegram ranks this channel #37 of 46 here — alongside 45 others — read 28 August 2026
@taraaznet · 19,881
Telegram ranks this channel #63 of 90 here — alongside 89 others — read 2 October 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“طعم شیرین ریاضی” (@AZvorHB21), 2,010 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/AZvorHB21.
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.