Channel
Beltron Study Group
@beltronstudygroup
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,662subscribers
-46 since we began measuring on 16 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001548250200 |
|---|---|
| Type | Channel |
| Username | @beltronstudygroup |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 September 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/beltronstudygroup |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 9 Nov 2026, 15:09 | 1,662 | -3 |
| 6 Nov 2026, 14:37 | 1,665 | -2 |
| 3 Nov 2026, 14:44 | 1,667 | -3 |
| 25 Oct 2026, 18:49 | 1,670 | -1 |
| 22 Oct 2026, 21:38 | 1,671 | -1 |
| 20 Oct 2026, 03:56 | 1,672 | -2 |
| 13 Oct 2026, 16:48 | 1,674 | -3 |
| 7 Oct 2026, 19:58 | 1,677 | -3 |
| 1 Oct 2026, 09:39 | 1,680 | -9 |
| 25 Sept 2026, 00:05 | 1,689 | no change |
| 16 Sept 2026, 06:16 | 1,689 | -5 |
| 12 Sept 2026, 20:17 | 1,694 | -4 |
| 8 Sept 2026, 12:02 | 1,698 | -2 |
| 31 Aug 2026, 08:24 | 1,700 | -2 |
| 24 Aug 2026, 20:54 | 1,702 | -3 |
| 20 Aug 2026, 20:04 | 1,705 | -2 |
| 17 Aug 2026, 13:44 | 1,707 | -1 |
| 16 Aug 2026, 07:15 | 1,708 | 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,202
Telegram ranks this channel #54 of 70 here — alongside 69 others — read 23 August 2026
@Video_Status_Lover · 114,620
Telegram ranks this channel #56 of 56 here — alongside 55 others — read 16 August 2026
@officialumeshk · 42,733
Telegram ranks this channel #67 of 67 here — alongside 66 others — read 28 August 2026
@biharjobportal · 90,781
Telegram ranks this channel #80 of 85 here — alongside 84 others — read 16 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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“Beltron Study Group” (@beltronstudygroup), 1,662 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/beltronstudygroup.
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.