![Telegram profile photo for Kargawal Misty [RAS Reader]](https://cdn.tgregister.com/av/cb/cb1a6593c91041d75855c653499a9b94d5ca2a558867e9f7ce095575ed8c3225.jpg)
Channel
Kargawal Misty [RAS Reader]
@dkargawal
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,197subscribers
-26 since we began measuring on 28 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001409040362 |
|---|---|
| Type | Channel |
| Username | @dkargawal |
| Created | Between 1 February 2019 and 30 November 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 October 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/dkargawal |
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 4 October 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 |
|---|---|---|
| 7 Nov 2026, 12:48 | 1,197 | -1 |
| 4 Nov 2026, 15:17 | 1,198 | -1 |
| 1 Nov 2026, 20:31 | 1,199 | +3 |
| 29 Oct 2026, 11:51 | 1,196 | -1 |
| 26 Oct 2026, 00:55 | 1,197 | -2 |
| 23 Oct 2026, 09:50 | 1,199 | -1 |
| 20 Oct 2026, 00:06 | 1,200 | -1 |
| 17 Oct 2026, 07:36 | 1,201 | -1 |
| 14 Oct 2026, 11:21 | 1,202 | -2 |
| 11 Oct 2026, 06:00 | 1,204 | -5 |
| 5 Oct 2026, 02:36 | 1,209 | -8 |
| 4 Oct 2026, 03:06 | 1,217 | no change |
| 26 Sept 2026, 15:20 | 1,217 | -4 |
| 18 Sept 2026, 00:38 | 1,221 | +3 |
| 13 Sept 2026, 10:57 | 1,218 | -2 |
| 9 Sept 2026, 11:22 | 1,220 | -2 |
| 31 Aug 2026, 13:08 | 1,222 | -1 |
| 28 Aug 2026, 20:45 | 1,223 | 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.
@deeptisinghacademy · 21,959
Telegram ranks this channel #16 of 45 here — alongside 44 others — read 20 September 2026
@agricultureutkarsh · 41,543
Telegram ranks this channel #37 of 64 here — alongside 63 others — read 28 August 2026
@raghavsvireal · 1,813
Telegram ranks this channel #52 of 52 here — alongside 51 others — read 21 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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“Kargawal Misty [RAS Reader]” (@dkargawal), 1,197 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/dkargawal.
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.