Channel
TARGET KEA KSP 2026
@TargetKEAKSP
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,133subscribers
+59 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001620197458 |
|---|---|
| Type | Channel |
| Username | @TargetKEAKSP |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/TargetKEAKSP |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 62% 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 |
|---|---|---|
| 18 Sept 2026, 23:20 | 3,133 | +25 |
| 14 Sept 2026, 11:01 | 3,108 | +17 |
| 10 Sept 2026, 23:28 | 3,091 | no change |
| 10 Sept 2026, 10:59 | 3,091 | +19 |
| 5 Sept 2026, 12:01 | 3,072 | -8 |
| 1 Sept 2026, 12:07 | 3,080 | +3 |
| 29 Aug 2026, 15:34 | 3,077 | -7 |
| 26 Aug 2026, 12:13 | 3,084 | +5 |
| 23 Aug 2026, 01:28 | 3,079 | -4 |
| 19 Aug 2026, 03:44 | 3,083 | -5 |
| 15 Aug 2026, 18:05 | 3,088 | +9 |
| 12 Aug 2026, 10:47 | 3,079 | +5 |
| 11 Aug 2026, 21:15 | 3,074 | 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.
@POLICE_ASPIRANTS · 22,779
Telegram ranks this channel #11 of 66 here — alongside 65 others — read 20 September 2026
@vidyakashidharwad · 31,864
Telegram ranks this channel #16 of 76 here — alongside 75 others — read 5 September 2026
@VAOgoalforgovernmentjob · 24,370
Telegram ranks this channel #22 of 66 here — alongside 65 others — read 16 September 2026
@pariksha_vedike · 31,427
Telegram ranks this channel #30 of 66 here — alongside 65 others — read 6 September 2026
@kumarbhandarimath · 127,233
Telegram ranks this channel #45 of 74 here — alongside 73 others — read 13 August 2026
@IshwarGiri · 211,802
Telegram ranks this channel #47 of 85 here — alongside 84 others — read 11 August 2026
This channel appears in 6 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“TARGET KEA KSP 2026” (@TargetKEAKSP), 3,133 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/TargetKEAKSP.
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.