
Channel
CG E- Library pdf
@cgpscvyapam2024
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,070subscribers
+72 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001931826473 |
|---|---|
| Type | Channel |
| Username | @cgpscvyapam2024 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/cgpscvyapam2024 |
Topic
Other / unclassifiable — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 34% 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 |
|---|---|---|
| 16 Nov 2026, 01:21 | 3,070 | +10 |
| 7 Nov 2026, 12:57 | 3,060 | -3 |
| 4 Nov 2026, 18:15 | 3,063 | +8 |
| 1 Nov 2026, 13:56 | 3,055 | +5 |
| 29 Oct 2026, 06:26 | 3,050 | +6 |
| 25 Oct 2026, 17:51 | 3,044 | +8 |
| 23 Oct 2026, 00:26 | 3,036 | +6 |
| 20 Oct 2026, 03:26 | 3,030 | -3 |
| 17 Oct 2026, 05:46 | 3,033 | -2 |
| 14 Oct 2026, 04:57 | 3,035 | +1 |
| 10 Oct 2026, 13:36 | 3,034 | +1 |
| 4 Oct 2026, 20:57 | 3,033 | +7 |
| 25 Sept 2026, 05:59 | 3,026 | +5 |
| 15 Sept 2026, 17:56 | 3,021 | +9 |
| 12 Sept 2026, 02:39 | 3,012 | +1 |
| 11 Sept 2026, 13:58 | 3,011 | no change |
| 7 Sept 2026, 17:54 | 3,011 | +8 |
| 2 Sept 2026, 08:53 | 3,003 | +7 |
| 27 Aug 2026, 01:48 | 2,996 | -1 |
| 23 Aug 2026, 22:13 | 2,997 | 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,063
Telegram ranks this channel #4 of 63 here — alongside 62 others — read 31 August 2026
@yuvaiasacademykorba · 27,137
Telegram ranks this channel #21 of 56 here — alongside 55 others — read 11 September 2026
@CGPSC_CGVYAPAM_TEST · 53,825
Telegram ranks this channel #29 of 74 here — alongside 73 others — read 24 August 2026
@currentnewspaper · 60,440
Telegram ranks this channel #50 of 84 here — alongside 83 others — read 22 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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“CG E- Library pdf” (@cgpscvyapam2024), 3,070 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/cgpscvyapam2024.
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.