Channel
CUET EXAM PREPARTION
@CUET_UG_EXAM_PREPRATION
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,890subscribers
-183 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001877312050 |
|---|---|
| Type | Channel |
| Username | @CUET_UG_EXAM_PREPRATION |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 September 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/CUET_UG_EXAM_PREPRATION |
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 15 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 02:30 | 2,890 | -7 |
| 6 Nov 2026, 04:30 | 2,897 | -5 |
| 3 Nov 2026, 01:36 | 2,902 | -5 |
| 30 Oct 2026, 17:11 | 2,907 | -7 |
| 27 Oct 2026, 06:28 | 2,914 | -13 |
| 24 Oct 2026, 02:36 | 2,927 | -7 |
| 21 Oct 2026, 05:19 | 2,934 | -10 |
| 17 Oct 2026, 16:48 | 2,944 | -11 |
| 14 Oct 2026, 19:25 | 2,955 | -8 |
| 11 Oct 2026, 05:35 | 2,963 | -12 |
| 4 Oct 2026, 22:42 | 2,975 | -17 |
| 25 Sept 2026, 14:01 | 2,992 | -28 |
| 16 Sept 2026, 21:39 | 3,020 | -10 |
| 13 Sept 2026, 01:21 | 3,030 | -13 |
| 11 Sept 2026, 00:38 | 3,043 | no change |
| 9 Sept 2026, 08:40 | 3,043 | -12 |
| 3 Sept 2026, 21:36 | 3,055 | -9 |
| 31 Aug 2026, 13:42 | 3,064 | -4 |
| 28 Aug 2026, 05:04 | 3,068 | -5 |
| 25 Aug 2026, 03:45 | 3,073 | 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.
@etoos_neet_jee · 20,534
Telegram ranks this channel #12 of 48 here — alongside 47 others — read 26 September 2026
@skm_chemistry_lectures · 20,613
Telegram ranks this channel #21 of 57 here — alongside 56 others — read 26 September 2026
@UPSC_CivilServices_Prelims · 48,665
Telegram ranks this channel #70 of 73 here — alongside 72 others — read 25 August 2026
This channel appears in 3 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“CUET EXAM PREPARTION” (@CUET_UG_EXAM_PREPRATION), 2,890 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/CUET_UG_EXAM_PREPRATION.
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.