Channel
KPSC JUNCTION
@kpscjunction
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,007subscribers
-88 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001184687948 |
|---|---|
| Type | Channel |
| Username | @kpscjunction |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/kpscjunction |
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 14 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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 |
|---|---|---|
| 5 Nov 2026, 05:34 | 3,007 | -4 |
| 2 Nov 2026, 02:38 | 3,011 | -7 |
| 30 Oct 2026, 04:19 | 3,018 | -5 |
| 27 Oct 2026, 01:36 | 3,023 | -7 |
| 24 Oct 2026, 11:58 | 3,030 | -4 |
| 21 Oct 2026, 17:45 | 3,034 | -4 |
| 18 Oct 2026, 04:36 | 3,038 | -3 |
| 15 Oct 2026, 10:45 | 3,041 | -8 |
| 12 Oct 2026, 09:38 | 3,049 | -14 |
| 5 Oct 2026, 11:00 | 3,063 | -10 |
| 27 Sept 2026, 07:56 | 3,073 | -14 |
| 18 Sept 2026, 09:42 | 3,087 | -1 |
| 14 Sept 2026, 13:19 | 3,088 | -3 |
| 11 Sept 2026, 07:35 | 3,091 | +18 |
| 10 Sept 2026, 23:54 | 3,073 | no change |
| 6 Sept 2026, 13:01 | 3,073 | +5 |
| 1 Sept 2026, 23:35 | 3,068 | -2 |
| 30 Aug 2026, 05:11 | 3,070 | -3 |
| 27 Aug 2026, 01:58 | 3,073 | -2 |
| 23 Aug 2026, 20:26 | 3,075 | 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.
@kannadasamachar · 57,659
Telegram ranks this channel #36 of 65 here — alongside 64 others — read 22 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“KPSC JUNCTION” (@kpscjunction), 3,007 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/kpscjunction.
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.