Channel
كاريزما MCQ
@karezmaaazzz
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,044subscribers
+39 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001152425813 |
|---|---|
| Type | Channel |
| Username | @karezmaaazzz |
| Created | Between 1 October 2018 and 30 June 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 October 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/karezmaaazzz |
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 8 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 11 Oct 2026, 22:15 | 1,044 | +4 |
| 8 Oct 2026, 05:12 | 1,040 | no change |
| 5 Oct 2026, 11:21 | 1,040 | +6 |
| 27 Sept 2026, 08:56 | 1,034 | +4 |
| 15 Sept 2026, 09:57 | 1,030 | +8 |
| 11 Sept 2026, 12:58 | 1,022 | +2 |
| 6 Sept 2026, 20:20 | 1,020 | +4 |
| 2 Sept 2026, 09:43 | 1,016 | +1 |
| 30 Aug 2026, 10:12 | 1,015 | +3 |
| 27 Aug 2026, 06:46 | 1,012 | +2 |
| 24 Aug 2026, 03:24 | 1,010 | -2 |
| 17 Aug 2026, 19:48 | 1,012 | +2 |
| 14 Aug 2026, 14:05 | 1,010 | +1 |
| 11 Aug 2026, 09:38 | 1,009 | +3 |
| 8 Aug 2026, 00:58 | 1,006 | +1 |
| 7 Aug 2026, 17:09 | 1,005 | 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.
@Gyna_Obs_Data · 26,181
Telegram ranks this channel #3 of 82 here — alongside 81 others — read 14 September 2026
@tabib7th · 31,072
Telegram ranks this channel #13 of 84 here — alongside 83 others — read 6 September 2026
@passusmle111 · 21,853
Telegram ranks this channel #19 of 81 here — alongside 80 others — read 23 September 2026
@Suffer_ya_doctor · 135,387
Telegram ranks this channel #24 of 88 here — alongside 87 others — read 16 August 2026
@FUTUREDOCTORS_194 · 43,132
Telegram ranks this channel #32 of 89 here — alongside 88 others — read 29 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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“كاريزما MCQ” (@karezmaaazzz), 1,044 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/karezmaaazzz.
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.