Channel
Answer writing Secrets for CGPSC Mains
@AnswerwritingSecretsCGPSCMains
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,709subscribers
+9 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001939650232 |
|---|---|
| Type | Channel |
| Username | @AnswerwritingSecretsCGPSCMains |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/AnswerwritingSecretsCGPSCMains |
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 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 12:58 | 4,709 | +4 |
| 13 Sept 2026, 05:59 | 4,705 | -6 |
| 9 Sept 2026, 11:19 | 4,711 | -1 |
| 4 Sept 2026, 05:58 | 4,712 | -1 |
| 2 Sept 2026, 20:07 | 4,713 | no change |
| 1 Sept 2026, 06:03 | 4,713 | +2 |
| 25 Aug 2026, 17:33 | 4,711 | +1 |
| 22 Aug 2026, 19:14 | 4,710 | +7 |
| 19 Aug 2026, 11:35 | 4,703 | +2 |
| 16 Aug 2026, 02:35 | 4,701 | +1 |
| 14 Aug 2026, 22:45 | 4,700 | 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.
@CGPSCKNOWLEDGE · 38,018
Telegram ranks this channel #9 of 63 here — alongside 62 others — read 31 August 2026
@itsofficersacademy · 25,880
Telegram ranks this channel #15 of 53 here — alongside 52 others — read 13 September 2026
@CGPSC_CGVYAPAM_TEST · 53,827
Telegram ranks this channel #23 of 74 here — alongside 73 others — read 24 August 2026
@successkey988 · 54,037
Telegram ranks this channel #35 of 59 here — alongside 58 others — read 23 August 2026
@va1ncchi1ni · 109,674
Telegram ranks this channel #69 of 89 here — alongside 88 others — read 14 August 2026
This channel appears in 5 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Answer writing Secrets for CGPSC Mains” (@AnswerwritingSecretsCGPSCMains), 4,709 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/AnswerwritingSecretsCGPSCMains.
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.