Channel
CUET Commerce Class 11 12
@Commerce_Class_11_12_CUET
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,310subscribers
-137 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001433018569 |
|---|---|
| Type | Channel |
| Username | @Commerce_Class_11_12_CUET |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/Commerce_Class_11_12_CUET |
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 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, 08:04 | 3,310 | -7 |
| 5 Nov 2026, 20:26 | 3,317 | -6 |
| 3 Nov 2026, 02:49 | 3,323 | +6 |
| 30 Oct 2026, 21:28 | 3,317 | -1 |
| 28 Oct 2026, 05:07 | 3,318 | -5 |
| 25 Oct 2026, 13:35 | 3,323 | -5 |
| 22 Oct 2026, 19:06 | 3,328 | -10 |
| 19 Oct 2026, 09:06 | 3,338 | -8 |
| 16 Oct 2026, 18:29 | 3,346 | -7 |
| 14 Oct 2026, 02:11 | 3,353 | -10 |
| 9 Oct 2026, 01:20 | 3,363 | -22 |
| 2 Oct 2026, 07:37 | 3,385 | -28 |
| 16 Sept 2026, 08:37 | 3,413 | -9 |
| 12 Sept 2026, 18:59 | 3,422 | -6 |
| 8 Sept 2026, 18:56 | 3,428 | -17 |
| 8 Sept 2026, 14:11 | 3,445 | no change |
| 3 Sept 2026, 16:58 | 3,445 | +2 |
| 31 Aug 2026, 14:54 | 3,443 | -4 |
| 27 Aug 2026, 19:30 | 3,447 | 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.
@rajataroraclasses · 41,582
Telegram ranks this channel #3 of 27 here — alongside 26 others — read 28 August 2026
@OfficialCommercewallah · 44,841
Telegram ranks this channel #9 of 55 here — alongside 54 others — read 27 August 2026
@Railway_RRB_NTPC_Group_D_RPF_ALP · 34,069
Telegram ranks this channel #16 of 48 here — alongside 47 others — read 2 September 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 Commerce Class 11 12” (@Commerce_Class_11_12_CUET), 3,310 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/Commerce_Class_11_12_CUET.
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.