Channel
BEU BTECH Notes, PYQ, Organizer
@BEU_Bihar
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,367subscribers
+187 since we began measuring on 22 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001839310308 |
|---|---|
| Type | Channel |
| Username | @BEU_Bihar |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/BEU_Bihar |
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 18 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 |
|---|---|---|
| 6 Nov 2026, 03:28 | 2,367 | +4 |
| 2 Nov 2026, 16:29 | 2,363 | +3 |
| 30 Oct 2026, 06:36 | 2,360 | +5 |
| 27 Oct 2026, 13:56 | 2,355 | +13 |
| 24 Oct 2026, 12:56 | 2,342 | -2 |
| 15 Oct 2026, 01:55 | 2,344 | +5 |
| 11 Oct 2026, 19:21 | 2,339 | +22 |
| 5 Oct 2026, 11:21 | 2,317 | +4 |
| 27 Sept 2026, 17:00 | 2,313 | +30 |
| 18 Sept 2026, 00:22 | 2,283 | no change |
| 17 Sept 2026, 23:17 | 2,283 | +17 |
| 13 Sept 2026, 23:58 | 2,266 | +30 |
| 9 Sept 2026, 22:36 | 2,236 | +17 |
| 5 Sept 2026, 00:39 | 2,219 | +13 |
| 1 Sept 2026, 11:55 | 2,206 | +15 |
| 29 Aug 2026, 11:28 | 2,191 | +4 |
| 26 Aug 2026, 02:42 | 2,187 | +2 |
| 23 Aug 2026, 01:46 | 2,185 | +5 |
| 22 Aug 2026, 11:01 | 2,180 | 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.
@BiharExamWallah · 54,322
Telegram ranks this channel #45 of 70 here — alongside 69 others — read 23 August 2026
@ignou · 90,793
Telegram ranks this channel #51 of 72 here — alongside 71 others — read 22 August 2026
@sscelitee · 21,280
Telegram ranks this channel #52 of 57 here — alongside 56 others — read 30 September 2026
@solved_ignou_assignment · 69,522
Telegram ranks this channel #70 of 78 here — alongside 77 others — read 22 August 2026
This channel appears in 4 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“BEU BTECH Notes, PYQ, Organizer” (@BEU_Bihar), 2,367 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/BEU_Bihar.
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.