Channel
AP DSC - 2026
@APTET26
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,080subscribers
+6 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001757492876 |
|---|---|
| Type | Channel |
| Username | @APTET26 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 September 2026 |
| Last confirmed live | 25 October 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 25 October 2026 |
| On Telegram | t.me/APTET26 |
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 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Oct 2026, 00:06 | 4,080 | +2 |
| 22 Oct 2026, 00:16 | 4,078 | -12 |
| 18 Oct 2026, 11:44 | 4,090 | +2 |
| 15 Oct 2026, 01:38 | 4,088 | +4 |
| 11 Oct 2026, 23:56 | 4,084 | -3 |
| 5 Oct 2026, 01:20 | 4,087 | -8 |
| 25 Sept 2026, 23:57 | 4,095 | -5 |
| 17 Sept 2026, 15:01 | 4,100 | -3 |
| 14 Sept 2026, 00:17 | 4,103 | +7 |
| 10 Sept 2026, 10:15 | 4,096 | +4 |
| 5 Sept 2026, 04:41 | 4,092 | +4 |
| 4 Sept 2026, 23:49 | 4,088 | no change |
| 1 Sept 2026, 18:25 | 4,088 | +13 |
| 29 Aug 2026, 11:35 | 4,075 | -1 |
| 26 Aug 2026, 18:42 | 4,076 | +8 |
| 24 Aug 2026, 02:43 | 4,068 | -1 |
| 20 Aug 2026, 18:36 | 4,069 | -4 |
| 17 Aug 2026, 10:35 | 4,073 | -1 |
| 15 Aug 2026, 20:30 | 4,074 | 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.
@YESPUBLICATION · 27,019
Telegram ranks this channel #6 of 70 here — alongside 69 others — read 12 September 2026
@apjobs9 · 20,024
Telegram ranks this channel #14 of 45 here — alongside 44 others — read 27 September 2026
@RamRameshgroup · 42,652
Telegram ranks this channel #20 of 64 here — alongside 63 others — read 28 August 2026
@shyaminstitutekakinada2001 · 100,700
Telegram ranks this channel #23 of 71 here — alongside 70 others — read 15 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 25 October 2026 — this entry's latest reading, not the date you are reading this.
“AP DSC - 2026” (@APTET26), 4,080 subscribers as measured 25 October 2026. Telegram Register, tgregister.com/channel/APTET26.
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.