Channel
🚔टार्गेट खाकी🚔
@target_khaki1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,781subscribers
+22 since we began measuring on 21 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001355037441 |
|---|---|
| Type | Channel |
| Username | @target_khaki1 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 23 September 2026 |
| Last confirmed live | 24 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 24 September 2026 |
| On Telegram | t.me/target_khaki1 |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 24 Sept 2026, 22:16 | 1,781 | -1 |
| 23 Sept 2026, 16:15 | 1,782 | no change |
| 16 Sept 2026, 20:58 | 1,782 | +4 |
| 12 Sept 2026, 19:40 | 1,778 | -1 |
| 9 Sept 2026, 00:40 | 1,779 | +3 |
| 3 Sept 2026, 21:56 | 1,776 | +11 |
| 31 Aug 2026, 10:44 | 1,765 | -2 |
| 28 Aug 2026, 01:17 | 1,767 | +2 |
| 25 Aug 2026, 05:27 | 1,765 | +7 |
| 22 Aug 2026, 11:09 | 1,758 | -1 |
| 21 Aug 2026, 09:30 | 1,759 | 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.
@tikkarmarathi · 55,572
Telegram ranks this channel #1 of 66 here — alongside 65 others — read 23 August 2026
@MPSCPolity · 64,273
Telegram ranks this channel #23 of 70 here — alongside 69 others — read 21 August 2026
@MahaDGIPR · 30,856
Telegram ranks this channel #24 of 70 here — alongside 69 others — read 6 September 2026
@class_11th_12th_Chemistry_Notes · 32,634
Telegram ranks this channel #31 of 60 here — alongside 59 others — read 5 September 2026
@MHT_CET_EXAM_NOTES · 38,783
Telegram ranks this channel #34 of 55 here — alongside 54 others — read 31 August 2026
@MPSCmaths · 32,640
Telegram ranks this channel #36 of 69 here — alongside 68 others — read 4 September 2026
@foujimotivation · 24,793
Telegram ranks this channel #39 of 59 here — alongside 58 others — read 15 September 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 24 September 2026 — this entry's latest reading, not the date you are reading this.
“🚔टार्गेट खाकी🚔” (@target_khaki1), 1,781 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/target_khaki1.
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.