和平卡密: KHCM7tt7z2XcQB7yJYdj KHBnXfpfnhBX4m5vB52n KHN3fibmxuhQZEEU48cT KHNNLuwyQxZTRJU23ZvZ KHbxJXeD25qnguZ39q7W 王者卡密: WZe2rB6ueMacptuKqccR WZujhrfD5RcjKmuhVMUc WZEGb3izhEK3uzTqKcV8 WZwYk3fzuTcw27Jxrn5k WZcDUTDWTVSG7dsf8uvP 其他游戏 MFXhycZ5pKGpj85gjJhy MFkNjdBSsqtaMz74s2wA MFzBbuS6Sh42VbstBSqs MFVgJiNJHsMYxpfMRTDk MFKj32QNPxzPzziX7z3n

Channel
BG CHANNEL FILES
@BGCHANNEL2
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
1,280subscribers
-14 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 | -1001339342766 |
|---|---|
| Type | Channel |
| Username | @BGCHANNEL2 |
| Created | Between 1 March 2018 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 22 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 22 August 2026 |
| On Telegram | t.me/BGCHANNEL2 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 22 Aug 2026, 19:23 | 1,280 | -4 |
| 19 Aug 2026, 19:42 | 1,284 | -1 |
| 16 Aug 2026, 20:58 | 1,285 | -4 |
| 13 Aug 2026, 11:24 | 1,289 | -4 |
| 10 Aug 2026, 16:31 | 1,293 | -1 |
| 7 Aug 2026, 15:01 | 1,294 | no change |
| 7 Aug 2026, 04:46 | 1,294 | first reading |
Engagement
20 posts held, back to 12 November 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 25 March 2025. An engagement rate over an empty window would be a number about nothing.
Recent posts
New key: ENENd2znL4U83n5mBj9b ENEN4rJZ3aQDhjwuwp9b ENEN7FnCwcvHQzr7XeaY ENENFgmnMa3JPuvrK9TB ENENRJhrnqZ4yavSaBpK ENENyKtckZHPM93cTJ89 ENEN9sPRkvCeRg7hnW39 ENENUKLGzzzjGvmy2gjh ENENvhs86keQVpDFd3EP ENENHhym9qcjgx3m3R2U ENENpv2C5SAetwV2qbc5 ENENZcTyBKvPqQLFJqPk ENEND9XF7MqUvMe2pqpq ENENpubVUkvHU7dWfzWB ENENbux8wzPK92in4G2W ENENYTStcac79ZskSUbN ENENnMpxjwtt2Q4Yg3Rn ENENRjd4ErgapfM7tuK5 ENEN4spVCRT2UvkNVUiU ENENbHWihVPG…
所有游戏到最新版本
ZYGISK ROOT WH 🟡 64/32 BIT FREE
New key enen 3.0/3.1 Download Apk Esp enen aimtouch 3.0 : https://t.me/BangSatGamingChannel/30884 Esp Enen 3.1 : https://t.me/BangSatGamingChannel/31427
NEW AIZEN Virtual For Mobile Android 12-13 Support 32/64bit Alternative Multispace Greenbox.
Work Google Work Auto Download Obb
Virtual For Non Root Users Support Android: 11, 12 ,13
Virtual New -Smooth And Soft -Fixed Crash -Support All version New Update
Posted without readable text
New key enen Download Apk Esp enen aimtouch 2.9 https://t.me/BGCHANNEL2/1037
New module BC yellow 64+32Bit & Fix BC 2.9 Don't forget subscribe, like, and comments. https://youtu.be/1XG2osuYplQ?si=AqqjLmZXPCm1lXX0
Showing the 12 most recent of 20 posts we hold for @BGCHANNEL2. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@BGCHANNEL2 named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 4 posts, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
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 22 August 2026 — this entry's latest reading, not the date you are reading this.
“BG CHANNEL FILES” (@BGCHANNEL2), 1,280 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/BGCHANNEL2.
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.