Channel
Didari.math(12)
@didarimath123
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,110subscribers
+618 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002070574348 |
|---|---|
| Type | Channel |
| Username | @didarimath123 |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/didarimath123 |
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 17 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 |
|---|---|---|
| 7 Nov 2026, 02:18 | 3,110 | -22 |
| 4 Nov 2026, 09:09 | 3,132 | -17 |
| 1 Nov 2026, 16:36 | 3,149 | -30 |
| 30 Oct 2026, 02:51 | 3,179 | -37 |
| 26 Oct 2026, 17:16 | 3,216 | -69 |
| 23 Oct 2026, 07:36 | 3,285 | -122 |
| 20 Oct 2026, 06:38 | 3,407 | -131 |
| 17 Oct 2026, 15:50 | 3,538 | +1,273 |
| 14 Oct 2026, 10:06 | 2,265 | -9 |
| 10 Oct 2026, 23:20 | 2,274 | -10 |
| 4 Oct 2026, 17:02 | 2,284 | -12 |
| 25 Sept 2026, 04:37 | 2,296 | -16 |
| 17 Sept 2026, 06:41 | 2,312 | -14 |
| 17 Sept 2026, 02:01 | 2,326 | no change |
| 13 Sept 2026, 14:18 | 2,326 | -17 |
| 10 Sept 2026, 03:58 | 2,343 | -28 |
| 4 Sept 2026, 18:20 | 2,371 | -13 |
| 31 Aug 2026, 17:55 | 2,384 | -17 |
| 28 Aug 2026, 14:17 | 2,401 | -16 |
| 25 Aug 2026, 20:27 | 2,417 | 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.
@Vaeziinhendese · 21,114
Telegram ranks this channel #11 of 72 here — alongside 71 others — read 5 October 2026
@hendesegosaste · 33,072
Telegram ranks this channel #33 of 90 here — alongside 89 others — read 3 September 2026
@alighayoomi_teacher · 113,267
Telegram ranks this channel #43 of 87 here — alongside 86 others — read 15 August 2026
@AsalSunn · 24,744
Telegram ranks this channel #47 of 57 here — alongside 56 others — read 22 September 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Didari.math(12)” (@didarimath123), 3,110 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/didarimath123.
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.