Channel
All upsc toppers copy
@alltopperscopy
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,260subscribers
-21 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001568574285 |
|---|---|
| Type | Channel |
| Username | @alltopperscopy |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/alltopperscopy |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 89% 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 |
|---|---|---|
| 5 Nov 2026, 22:35 | 3,260 | +2 |
| 3 Nov 2026, 08:56 | 3,258 | -4 |
| 31 Oct 2026, 15:01 | 3,262 | -1 |
| 28 Oct 2026, 22:49 | 3,263 | -4 |
| 23 Oct 2026, 00:16 | 3,267 | -2 |
| 20 Oct 2026, 07:57 | 3,269 | -6 |
| 17 Oct 2026, 07:40 | 3,275 | -3 |
| 10 Oct 2026, 17:57 | 3,278 | -1 |
| 5 Oct 2026, 00:37 | 3,279 | +3 |
| 26 Sept 2026, 01:58 | 3,276 | -2 |
| 15 Sept 2026, 16:36 | 3,278 | +5 |
| 12 Sept 2026, 05:17 | 3,273 | -1 |
| 9 Sept 2026, 21:06 | 3,274 | no change |
| 7 Sept 2026, 19:55 | 3,274 | -8 |
| 27 Aug 2026, 17:52 | 3,282 | +5 |
| 24 Aug 2026, 13:14 | 3,277 | -1 |
| 20 Aug 2026, 12:02 | 3,278 | +2 |
| 17 Aug 2026, 13:04 | 3,276 | -7 |
| 14 Aug 2026, 07:25 | 3,283 | +4 |
| 10 Aug 2026, 14:52 | 3,279 | 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.
@Md_Classes_Official_Pdf_Mts_cgl · 45,086
Telegram ranks this channel #26 of 62 here — alongside 61 others — read 26 August 2026
@breaktimeclasses · 20,395
Telegram ranks this channel #28 of 64 here — alongside 63 others — read 27 September 2026
@sumitrewri · 55,607
Telegram ranks this channel #29 of 77 here — alongside 76 others — read 24 August 2026
@shankariasacademychennai · 59,824
Telegram ranks this channel #51 of 82 here — alongside 81 others — read 6 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“All upsc toppers copy” (@alltopperscopy), 3,260 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/alltopperscopy.
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.