
Channel
Mission Bihar Police 2026 🚨
@missionbiharpolic
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,140subscribers
+394 since we began measuring on 17 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002117901827 |
|---|---|
| Type | Channel |
| Username | @missionbiharpolic |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 September 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/missionbiharpolic |
Topic
Job listings — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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, 14:09 | 3,140 | -4 |
| 2 Nov 2026, 17:17 | 3,144 | -5 |
| 30 Oct 2026, 23:19 | 3,149 | -5 |
| 27 Oct 2026, 14:17 | 3,154 | -1 |
| 24 Oct 2026, 08:05 | 3,155 | +6 |
| 21 Oct 2026, 01:45 | 3,149 | +101 |
| 17 Oct 2026, 13:46 | 3,048 | +1 |
| 14 Oct 2026, 09:56 | 3,047 | -2 |
| 11 Oct 2026, 01:22 | 3,049 | -4 |
| 4 Oct 2026, 23:17 | 3,053 | +112 |
| 25 Sept 2026, 15:20 | 2,941 | -15 |
| 17 Sept 2026, 05:41 | 2,956 | +23 |
| 13 Sept 2026, 11:18 | 2,933 | +41 |
| 12 Sept 2026, 13:53 | 2,892 | no change |
| 9 Sept 2026, 06:58 | 2,892 | +39 |
| 31 Aug 2026, 04:28 | 2,853 | +79 |
| 28 Aug 2026, 04:13 | 2,774 | +3 |
| 25 Aug 2026, 03:47 | 2,771 | +1 |
| 22 Aug 2026, 01:19 | 2,770 | +17 |
| 18 Aug 2026, 14:03 | 2,753 | 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.
@RAHULSTUDYGROUP · 37,372
Telegram ranks this channel #7 of 32 here — alongside 31 others — read 31 August 2026
@BIHAR_DAROGA_BPSC_AEDO_BSSC_CGL · 87,319
Telegram ranks this channel #58 of 70 here — alongside 69 others — read 17 August 2026
@guruinsightful · 58,454
Telegram ranks this channel #64 of 66 here — alongside 65 others — read 22 August 2026
This channel appears in 3 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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“Mission Bihar Police 2026 🚨” (@missionbiharpolic), 3,140 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/missionbiharpolic.
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.