Channel
2026🇺🇸 BG&CR hijacking
@BGhijacking
On this record: Topic · Growth · Engagement · Cite this entry
2,172subscribers
+406 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003574905073 |
|---|---|
| Type | Channel |
| Username | @BGhijacking |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 22 September 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/BGhijacking |
Topic
Hacking & security — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 31 Oct 2026, 08:28 | 2,172 | +19 |
| 28 Oct 2026, 01:21 | 2,153 | +10 |
| 24 Oct 2026, 19:58 | 2,143 | +9 |
| 21 Oct 2026, 09:20 | 2,134 | +13 |
| 18 Oct 2026, 00:30 | 2,121 | +164 |
| 15 Oct 2026, 11:16 | 1,957 | +9 |
| 12 Oct 2026, 17:31 | 1,948 | +19 |
| 5 Oct 2026, 19:57 | 1,929 | +7 |
| 28 Sept 2026, 13:01 | 1,922 | +39 |
| 22 Sept 2026, 02:43 | 1,883 | no change |
| 15 Sept 2026, 20:59 | 1,883 | +10 |
| 12 Sept 2026, 04:15 | 1,873 | +16 |
| 8 Sept 2026, 07:59 | 1,857 | +5 |
| 2 Sept 2026, 18:29 | 1,852 | +10 |
| 30 Aug 2026, 15:46 | 1,842 | +11 |
| 27 Aug 2026, 12:25 | 1,831 | +9 |
| 24 Aug 2026, 20:24 | 1,822 | +11 |
| 21 Aug 2026, 02:27 | 1,811 | +16 |
| 17 Aug 2026, 18:34 | 1,795 | +14 |
| 14 Aug 2026, 20:06 | 1,781 | 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.
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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“2026🇺🇸 BG&CR hijacking” (@BGhijacking), 2,172 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/BGhijacking.
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.