Channel
Excise Inspector Krishna
@Inspector_Krishna
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,347subscribers
+2 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001991808178 |
|---|---|
| Type | Channel |
| Username | @Inspector_Krishna |
| Description | I am Krishna NIT DGP), selected as an EXCISE & CUSTOM INSPECTOR through SSC CGL 2023 (UR-2195) Live every Sunday @12:01 PM Contact me- Instagram:https://www.instagram.com/krishnasahunit?igsh=c2ttNnp6cWdsYXlh |
| Created | Between 1 October 2023 and 30 April 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 1 October 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 10 |
| On Telegram | t.me/Inspector_Krishna |
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 1 October 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 03:01 | 1,347 | no change |
| 30 Sept 2026, 06:38 | 1,347 | +10 |
| 15 Sept 2026, 20:37 | 1,337 | -2 |
| 12 Sept 2026, 13:17 | 1,339 | -4 |
| 8 Sept 2026, 10:20 | 1,343 | -1 |
| 3 Sept 2026, 10:06 | 1,344 | -2 |
| 31 Aug 2026, 06:42 | 1,346 | -1 |
| 28 Aug 2026, 08:16 | 1,347 | -1 |
| 25 Aug 2026, 15:35 | 1,348 | +3 |
| 25 Aug 2026, 02:15 | 1,345 | 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.
@digitalassamofficial · 19,519
Telegram ranks this channel #15 of 69 here — alongside 68 others — read 1 October 2026
@bhragukulshresthapw · 53,957
Telegram ranks this channel #40 of 53 here — alongside 52 others — read 25 August 2026
@LakshyaTalk · 35,993
Telegram ranks this channel #48 of 80 here — alongside 79 others — read 1 September 2026
@ArabindaBorah · 46,980
Telegram ranks this channel #58 of 76 here — alongside 75 others — read 26 August 2026
@GK_with_Rimjhim · 50,459
Telegram ranks this channel #75 of 79 here — alongside 78 others — read 25 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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“Excise Inspector Krishna” (@Inspector_Krishna), 1,347 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/Inspector_Krishna.
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.