Channel
BPSC- "THE AiM"
@bpsc21
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,360subscribers
-29 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001399211782 |
|---|---|
| Type | Channel |
| Username | @bpsc21 |
| Created | Between 1 October 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 16 September 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 2 times, most recently 1 November 2026 |
| On Telegram | t.me/bpsc21 |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 29 Oct 2026, 14:00 | 2,360 | -2 |
| 24 Oct 2026, 04:20 | 2,362 | +1 |
| 21 Oct 2026, 10:59 | 2,361 | -3 |
| 18 Oct 2026, 15:34 | 2,364 | -2 |
| 15 Oct 2026, 20:54 | 2,366 | -5 |
| 12 Oct 2026, 11:09 | 2,371 | -3 |
| 5 Oct 2026, 08:17 | 2,374 | -9 |
| 26 Sept 2026, 16:58 | 2,383 | -5 |
| 17 Sept 2026, 23:17 | 2,388 | +1 |
| 16 Sept 2026, 22:23 | 2,387 | no change |
| 10 Sept 2026, 08:19 | 2,387 | -6 |
| 4 Sept 2026, 16:15 | 2,393 | +2 |
| 31 Aug 2026, 22:16 | 2,391 | +4 |
| 28 Aug 2026, 11:42 | 2,387 | -1 |
| 25 Aug 2026, 17:52 | 2,388 | -1 |
| 18 Aug 2026, 20:15 | 2,389 | 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.
@CivilsNetwork · 74,896
Telegram ranks this channel #22 of 73 here — alongside 72 others — read 19 August 2026
@gsmaster1973 · 40,056
Telegram ranks this channel #24 of 62 here — alongside 61 others — read 29 August 2026
@thelogicalscience · 24,505
Telegram ranks this channel #29 of 51 here — alongside 50 others — read 15 September 2026
@uppscmaterialonline · 42,612
Telegram ranks this channel #38 of 47 here — alongside 46 others — read 30 August 2026
@upsc_ssc_ras_railway_uppolice · 76,693
Telegram ranks this channel #80 of 83 here — alongside 82 others — read 18 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 29 October 2026 — this entry's latest reading, not the date you are reading this.
“BPSC- "THE AiM"” (@bpsc21), 2,360 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/bpsc21.
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.