Telegram RegisterThe public register of Telegram
Telegram profile photo for INSIGHT CAPF

Channel

INSIGHT CAPF

@insightcapf

On this record: Growth · Engagement · Telegram's recommendations · Cite this entry

4,184subscribers

-29 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002046049934
TypeChannel
Username@insightcapf
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live10 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/insightcapf

Growth

4,1814,2144,197.512 August 2026 — 4,213 subscribers13 August 2026 — 4,214 subscribers16 August 2026 — 4,204 subscribers20 August 2026 — 4,197 subscribers23 August 2026 — 4,192 subscribers26 August 2026 — 4,186 subscribers29 August 2026 — 4,184 subscribers1 September 2026 — 4,181 subscribers4 September 2026 — 4,183 subscribers4 September 2026 — 4,183 subscribers10 September 2026 — 4,184 subscribers4,18412 August 202610 September 2026
11 measurements spanning 28 days, net -29. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 4,176–4,219 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 00:194,184+1
4 Sept 2026, 22:194,183no change
4 Sept 2026, 12:164,183+2
1 Sept 2026, 10:034,181-3
29 Aug 2026, 14:544,184-2
26 Aug 2026, 07:254,186-6
23 Aug 2026, 15:494,192-5
20 Aug 2026, 08:064,197-7
16 Aug 2026, 22:034,204-10
13 Aug 2026, 05:244,214+1
12 Aug 2026, 15:004,213first 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.

INSIGHT AFCAT
@Insightssbafcat · 58,677
Telegram ranks this channel #2 of 52 here — alongside 51 others — read 22 August 2026
Insight SSB
@insightssb · 165,587
Telegram ranks this channel #53 of 54 here — alongside 53 others — read 12 August 2026
DEFENCE MANIA
@defencemanialive · 51,615
Telegram ranks this channel #58 of 59 here — alongside 58 others — read 24 August 2026
Drishti IAS: KAROL BAGH
@drishtiIAS_KB · 37,075
Telegram ranks this channel #61 of 62 here — alongside 61 others — read 1 September 2026
Raj Malhotra's IAS
@rajmalhotraias · 39,346
Telegram ranks this channel #78 of 78 here — alongside 77 others — read 30 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 10 September 2026 — this entry's latest reading, not the date you are reading this.

“INSIGHT CAPF” (@insightcapf), 4,184 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/insightcapf.

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.