Channel
YDS /YDT PDF
@nothanesi
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,603subscribers
+521 since we began measuring on 23 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002058049622 |
|---|---|
| Type | Channel |
| Username | @nothanesi |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/nothanesi |
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 97% 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 |
|---|---|---|
| 4 Nov 2026, 16:46 | 4,603 | +4 |
| 1 Nov 2026, 16:21 | 4,599 | +3 |
| 29 Oct 2026, 22:59 | 4,596 | -1 |
| 26 Oct 2026, 13:56 | 4,597 | +7 |
| 23 Oct 2026, 12:58 | 4,590 | +2 |
| 20 Oct 2026, 09:46 | 4,588 | +13 |
| 16 Oct 2026, 23:05 | 4,575 | +34 |
| 13 Oct 2026, 13:21 | 4,541 | +56 |
| 7 Oct 2026, 23:37 | 4,485 | +64 |
| 1 Oct 2026, 06:56 | 4,421 | +180 |
| 16 Sept 2026, 03:21 | 4,241 | +36 |
| 12 Sept 2026, 06:59 | 4,205 | +29 |
| 7 Sept 2026, 23:18 | 4,176 | +24 |
| 4 Sept 2026, 22:46 | 4,152 | no change |
| 2 Sept 2026, 22:56 | 4,152 | +18 |
| 30 Aug 2026, 12:54 | 4,134 | +27 |
| 27 Aug 2026, 06:54 | 4,107 | +15 |
| 24 Aug 2026, 09:15 | 4,092 | +10 |
| 23 Aug 2026, 03:01 | 4,082 | 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.
@aykuthocayds · 21,507
Telegram ranks this channel #6 of 69 here — alongside 68 others — read 22 September 2026
@yks_kpss_pdf_kanalii · 28,324
Telegram ranks this channel #8 of 58 here — alongside 57 others — read 12 September 2026
@ecehocaydsyokdilyksdil · 32,963
Telegram ranks this channel #28 of 66 here — alongside 65 others — read 11 September 2026
@CBSEClass12_Boards · 53,919
Telegram ranks this channel #46 of 51 here — alongside 50 others — read 23 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“YDS /YDT PDF” (@nothanesi), 4,603 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/nothanesi.
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.