Channel
मिशन खाकी
@imp_kayade
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,775subscribers
+6 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001678011169 |
|---|---|
| Type | Channel |
| Username | @imp_kayade |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/imp_kayade |
Topic
Other / unclassifiable — 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 98% 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 |
|---|---|---|
| 3 Nov 2026, 21:05 | 4,775 | -4 |
| 31 Oct 2026, 18:58 | 4,779 | +23 |
| 29 Oct 2026, 02:46 | 4,756 | -13 |
| 25 Oct 2026, 18:19 | 4,769 | -8 |
| 22 Oct 2026, 13:19 | 4,777 | -4 |
| 19 Oct 2026, 17:20 | 4,781 | +5 |
| 16 Oct 2026, 19:18 | 4,776 | +31 |
| 13 Oct 2026, 11:48 | 4,745 | +8 |
| 7 Oct 2026, 08:15 | 4,737 | -19 |
| 30 Sept 2026, 13:00 | 4,756 | -14 |
| 16 Sept 2026, 03:58 | 4,770 | -15 |
| 12 Sept 2026, 15:36 | 4,785 | +31 |
| 8 Sept 2026, 07:19 | 4,754 | -33 |
| 3 Sept 2026, 06:45 | 4,787 | -16 |
| 2 Sept 2026, 12:15 | 4,803 | no change |
| 31 Aug 2026, 02:02 | 4,803 | +34 |
| 28 Aug 2026, 07:07 | 4,769 | +1 |
| 25 Aug 2026, 15:52 | 4,768 | -1 |
| 25 Aug 2026, 10:30 | 4,769 | 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.
@GadchiroliGK · 20,836
Telegram ranks this channel #22 of 48 here — alongside 47 others — read 4 October 2026
@MP_BOARD_OFFICIALJ · 23,565
Telegram ranks this channel #23 of 33 here — alongside 32 others — read 13 September 2026
@Lakshyvedh · 40,883
Telegram ranks this channel #29 of 62 here — alongside 61 others — read 29 August 2026
@UPSC_SSC_NCERT_POLITY_HISTORY_GK · 47,755
Telegram ranks this channel #67 of 72 here — alongside 71 others — read 25 August 2026
This channel appears in 4 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“मिशन खाकी” (@imp_kayade), 4,775 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/imp_kayade.
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.