Channel
CUET Utkarsh
@CUETUtkarsh
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,784subscribers
-189 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001704864367 |
|---|---|
| Type | Channel |
| Username | @CUETUtkarsh |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 September 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/CUETUtkarsh |
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 93% 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 |
|---|---|---|
| 19 Sept 2026, 10:14 | 4,784 | -23 |
| 14 Sept 2026, 16:18 | 4,807 | -19 |
| 10 Sept 2026, 22:41 | 4,826 | -23 |
| 6 Sept 2026, 01:21 | 4,849 | -25 |
| 1 Sept 2026, 22:56 | 4,874 | no change |
| 1 Sept 2026, 16:59 | 4,874 | -14 |
| 30 Aug 2026, 03:28 | 4,888 | -23 |
| 27 Aug 2026, 03:33 | 4,911 | -21 |
| 24 Aug 2026, 02:02 | 4,932 | -23 |
| 20 Aug 2026, 11:27 | 4,955 | -12 |
| 17 Aug 2026, 19:05 | 4,967 | -6 |
| 16 Aug 2026, 21:15 | 4,973 | 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.
@CCSUniversityMRT · 50,704
Telegram ranks this channel #12 of 49 here — alongside 48 others — read 25 August 2026
@cuetAdda247 · 89,345
Telegram ranks this channel #13 of 68 here — alongside 67 others — read 16 August 2026
@royaljeticarbhuneet · 34,494
Telegram ranks this channel #14 of 67 here — alongside 66 others — read 3 September 2026
@deeptisinghacademy · 22,486
Telegram ranks this channel #15 of 45 here — alongside 44 others — read 20 September 2026
@humanatease · 25,901
Telegram ranks this channel #17 of 46 here — alongside 45 others — read 13 September 2026
@pwcuetwallah · 65,050
Telegram ranks this channel #21 of 45 here — alongside 44 others — read 20 August 2026
@agricultureutkarsh · 42,681
Telegram ranks this channel #25 of 64 here — alongside 63 others — read 28 August 2026
This channel appears in 7 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“CUET Utkarsh” (@CUETUtkarsh), 4,784 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/CUETUtkarsh.
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.