Channel
Maths By Adutiya Sir@735
@audityasirbymaths
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,735subscribers
-162 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001511264156 |
|---|---|
| Type | Channel |
| Username | @audityasirbymaths |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 22 October 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 22 October 2026 |
| On Telegram | t.me/audityasirbymaths |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Oct 2026, 16:18 | 4,735 | -6 |
| 19 Oct 2026, 11:05 | 4,741 | -4 |
| 16 Oct 2026, 05:57 | 4,745 | -15 |
| 13 Oct 2026, 03:47 | 4,760 | -16 |
| 6 Oct 2026, 17:58 | 4,776 | -20 |
| 29 Sept 2026, 11:58 | 4,796 | -22 |
| 19 Sept 2026, 08:14 | 4,818 | -8 |
| 14 Sept 2026, 16:59 | 4,826 | -2 |
| 11 Sept 2026, 11:41 | 4,828 | -4 |
| 6 Sept 2026, 18:59 | 4,832 | -6 |
| 2 Sept 2026, 08:03 | 4,838 | -10 |
| 1 Sept 2026, 23:17 | 4,848 | no change |
| 30 Aug 2026, 18:13 | 4,848 | -11 |
| 27 Aug 2026, 07:54 | 4,859 | -9 |
| 24 Aug 2026, 04:36 | 4,868 | -6 |
| 20 Aug 2026, 12:57 | 4,874 | -5 |
| 17 Aug 2026, 19:26 | 4,879 | -7 |
| 15 Aug 2026, 00:17 | 4,886 | -11 |
| 10 Aug 2026, 10:45 | 4,897 | 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.
@piyushvarshneysirji · 112,781
Telegram ranks this channel #15 of 71 here — alongside 70 others — read 14 August 2026
@careerwillrailwayexam · 31,603
Telegram ranks this channel #28 of 52 here — alongside 51 others — read 6 September 2026
@GopalSir_Eng · 134,521
Telegram ranks this channel #54 of 81 here — alongside 80 others — read 13 August 2026
@reasoningbyarunsir · 317,618
Telegram ranks this channel #56 of 89 here — alongside 88 others — read 10 August 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 22 October 2026 — this entry's latest reading, not the date you are reading this.
“Maths By Adutiya Sir@735” (@audityasirbymaths), 4,735 subscribers as measured 22 October 2026. Telegram Register, tgregister.com/channel/audityasirbymaths.
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.