⭐金鸣战神v5 🤙功能 ✅据点 ✅午后 ✅防抖 ✅强锁自瞄 😁适配枪械 ✅mp5k ✅uzi ✅维克托 ✅mk14 ✅sks ✅slr ✅dp28 ✅m249 ✅akm ✅aug ✅狗砸 ✅m416 ✅m762 ✅qbz ✅死噶 👑内置防封值👑 👑百分百稳定👑 👑不稳金鸣剁鸡鸡👑 ➡️点我查看反馈 🌟下单链接 https://new.818fka.com/shop/YGNRI945
👍2
Signed 金鸣『Sere』

Channel
@bmgwjnb
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
9,531subscribers
-746 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002367063100 |
|---|---|
| Type | Channel |
| Username | @bmgwjnb |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/bmgwjnb |
Gaming — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 50% 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 why it has no browse page of its own yet.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @bmnb78/75565 Aug 2026, 11:52 UTC | @bmgwjnb/29211 · this entry5 Aug 2026, 11:52 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @bmnb78 | 11 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @bmnb78 (10–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 3 of the 4 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 21 comparable posts for this entry, running 24 July 2026 to 8 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @bmgwjnb — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 8 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 02:19 | 9,531 | -237 |
| 14 Sept 2026, 15:02 | 9,768 | -182 |
| 11 Sept 2026, 09:36 | 9,950 | -113 |
| 8 Sept 2026, 12:41 | 10,063 | +104 |
| 3 Sept 2026, 00:19 | 9,959 | -96 |
| 2 Sept 2026, 01:03 | 10,055 | -48 |
| 1 Sept 2026, 03:54 | 10,103 | -45 |
| 31 Aug 2026, 04:14 | 10,148 | -27 |
| 30 Aug 2026, 02:25 | 10,175 | -72 |
| 29 Aug 2026, 05:06 | 10,247 | -67 |
| 28 Aug 2026, 03:25 | 10,314 | +30 |
| 27 Aug 2026, 05:55 | 10,284 | -37 |
| 26 Aug 2026, 06:44 | 10,321 | +20 |
| 25 Aug 2026, 05:33 | 10,301 | -80 |
| 24 Aug 2026, 06:25 | 10,381 | +27 |
| 22 Aug 2026, 17:34 | 10,354 | -17 |
| 21 Aug 2026, 10:34 | 10,371 | -30 |
| 20 Aug 2026, 09:57 | 10,401 | -5 |
| 19 Aug 2026, 11:12 | 10,406 | -53 |
| 18 Aug 2026, 09:52 | 10,459 | first reading |
107 posts held, back to 24 July 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 38 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 19 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 107 (24 July 2026 – 28 August 2026) |
| Views total | 1,651 |
| Reactions total | 104 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 02:58 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
297 reactions across 79 posts, in 6 distinct kinds. The most used accounts for 86.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 256 | 86.2% | |
| ❤ | 36 | 12.1% | |
| 😍 | 2 | 0.673% | |
| ❤🔥 | 1 | 0.337% | |
| 🤯 | 1 | 0.337% | |
| 🥰 | 1 | 0.337% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 82 of the 107 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 297 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 107 most recent posts we hold, published 24 July 2026 to 28 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
⭐金鸣战神v5 🤙功能 ✅据点 ✅午后 ✅防抖 ✅强锁自瞄 😁适配枪械 ✅mp5k ✅uzi ✅维克托 ✅mk14 ✅sks ✅slr ✅dp28 ✅m249 ✅akm ✅aug ✅狗砸 ✅m416 ✅m762 ✅qbz ✅死噶 👑内置防封值👑 👑百分百稳定👑 👑不稳金鸣剁鸡鸡👑 ➡️点我查看反馈 🌟下单链接 https://new.818fka.com/shop/YGNRI945
👍2
Signed 金鸣『Sere』
和平/PUBG/三角洲/无畏契约低价游戏账号购买
👍4
Signed 北冥
北冥新赛季公益V25『最强公益』 ⭐支持功能 ✅无后100%✅防抖100% ✅十字架 ✅快速切枪 ✅强锁自瞄 ✅无跳弹100% ⭐有效枪械 ✅AUG ✅M4 ✅AK ✅MK ✅MG3 ✅FAMAS ✅M1 ✅TMP ✅M249 ✅M762 ✅QBZ ✅MP5K ✅狗砸 ✅维克多 ✅SKS ✅M338 到消息评论区下面发送 /sign_in 随机抽人送定制或者拦截 1️⃣搭配至尊北冥拦截 2.0 2️⃣转转数据号『低价货源』 3️⃣北冥高速公益网盘下载 📥📥📥📥📥📥📥📥 点击我跳转高速网盘下载链接 点击我跳转高速网盘下载链接
👍8
Signed 北冥
TG最强公益破解资源分享频道 ❤️『无畏契约』❤️『和平精英』 🎚『王者荣耀』🎚『失控进化』 🎚『三 角 洲 』🎚『香肠派对』 🤣直装 🤣内核 🤣注入 🤣国体 点击蓝色字体加入官方频道 点击蓝色字体加入官方频道 点击蓝色字体加入官方频道
👍6❤1
Signed 北冥
北冥新赛季公益V24『最强公益』 ⭐支持功能 ✅无后100%✅防抖100% ✅十字架 ✅快速切枪 ✅强锁自瞄 ✅无跳弹100% ⭐有效枪械 ✅AUG ✅M4 ✅AK ✅MK ✅MG3 ✅FAMAS ✅M1 ✅TMP ✅M249 ✅M762 ✅QBZ ✅MP5K ✅狗砸 ✅维克多 ✅SKS ✅M338 1️⃣搭配至尊北冥拦截 2.0 2️⃣转转数据号『低价货源』 3️⃣北冥高速公益网盘下载 📥📥📥📥📥📥📥📥 点击我跳转高速网盘下载链接 点击我跳转高速网盘下载链接
👍4❤1
Signed 北冥
🇨🇳『转转』数据号【质量】🙈 ✅售后24小时在线 (服务拉满!) 主营:『和平无限授权号』『和平Q直登V扫码号 『安卓iOS和平数据号』『三角洲无畏契约数据号』 😀新增全网最低价无限授权号😀 😙卡网售卖游戏账号 🎚和平精英 👍无畏契约 ❤️三角洲 🎚PUBG 🔗24小时自助下单链接🔗 👍购买链接: 卡网1: https://luoye.chyidc.cn/shop/LQ2XVETA 卡网2:https://luoye.chyidc.cn/shop/LQ2XVETA 【全网唯一低价质量靠谱数据号】 😋二卖出门被车撞死😋 👍圈钱出门被车撞死👍 😡 售后客服 @NIMEIPY 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道
Signed 北冥
北冥公益人物范围V4.0 ✅0.50超稳全身范围 ✅支持全部枪械 ✅支持地铁/经典/绿洲全模式 ✅尽量搭配端口或拦截 到每条消息评论区下面发送 /sign_in 随机抽人送定制或者拦截 1️⃣搭配至尊北冥拦截 2.0 2️⃣『和平精英』官方数据号 3️⃣北冥高速公益网盘下载 📥📥📥📥📥📥📥📥 点击我跳转高速网盘下载链接 点击我跳转高速网盘下载链接
👍8
Signed 凄美
🇨🇳『转转』数据号【质量】🙈 ✅售后24小时在线 (服务拉满!) 主营:『和平无限授权号』『和平Q直登V扫码号 『安卓iOS和平数据号』『三角洲无畏契约数据号』 😀新增全网最低价无限授权号😀 😙卡网售卖游戏账号 🎚和平精英 👍无畏契约 ❤️三角洲 🎚王者荣耀 🔗24小时自助下单链接🔗 👍购买链接: 卡网1: https://luoye.chyidc.cn/shop/LQ2XVETA 卡网2:https://luoye.chyidc.cn/shop/LQ2XVETA 【全网唯一低价质量靠谱数据号】 😋二卖出门被车撞死😋 👍圈钱出门被车撞死👍 😡 售后客服 @NIMEIPY 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道
👍4
Signed 凄美
北冥公益内透V5 ✅全地图透视 ✅头部黄色上色 ✅人物头部发光 ✅HDR画质发光 到每条消息评论区下面发送 /sign_in 随机抽人送定制或者拦截 1️⃣搭配至尊北冥拦截 2.0 2️⃣转转数据号『低价货源』 3️⃣北冥高速公益网盘下载 📥📥📥📥📥📥📥📥 点击我跳转高速网盘下载链接 点击我跳转高速网盘下载链接
👍10
Signed 凄美
北冥新赛季公益V23『独家思路』 ⭐支持功能 ✅无后100%✅防抖100% ✅十字架 ✅快速切枪 ✅强锁自瞄 ✅无跳弹100% ⭐有效枪械 ✅AUG ✅M4 ✅AK ✅MK ✅MG3 ✅FAMAS ✅M1 ✅TMP ✅M249 ✅M762 ✅QBZ ✅MP5K ✅狗砸 ✅维克多 ✅SKS ✅S12K 1️⃣搭配至尊北冥拦截 2.0 2️⃣转转数据号『低价货源』 3️⃣北冥高速公益网盘下载 📥📥📥📥📥📥📥📥 点击我跳转高速网盘下载链接 点击我跳转高速网盘下载链接
👍4❤2
Signed 凄美
🇨🇳『转转』数据号【质量】🙈 ✅售后24小时在线 (服务拉满!) 主营:『和平无限授权号』『和平Q直登V扫码号 『安卓iOS和平数据号』『三角洲无畏契约数据号』 😀新增全网最低价无限授权号😀 😙卡网售卖游戏账号 🎚和平精英 👍无畏契约 ❤️三角洲 🎚王者荣耀 🔗24小时自助下单链接🔗 👍购买链接: 卡网1: https://luoye.chyidc.cn/shop/LQ2XVETA 卡网2:https://luoye.chyidc.cn/shop/LQ2XVETA 【全网唯一低价质量靠谱数据号】 😋二卖出门被车撞死😋 👍圈钱出门被车撞死👍 😡 售后客服 @NIMEIPY 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道 进入每周免费发放100+数据号频道
👍5
Signed 将小杀.黑资报警 SOSO
✔️瑶少高质量无限授权自营✔️ 😀和平/数据号/授权号/直登号/😀 ➡️😃😃退游号😃😃退游号 ➡️😃😃😃😃 源头直营最低价格 ➡️😃😃不鉴别、无人脸、不冻结 🥇一年诚信经营,三年售后兜底 😙😍😗😋😝🙃😜🤨😜 👍👍购买链接:https://wkaiw.oqzgb.com/shop/YSSJHNB 😐上号器下载/使用教程:点我跳转 🔗永久导航地址: https://t.me/cannian6 ➡️所有账号问题都包售后✅ 👑全新自动去鉴别上号器👑 🔥一手号商、无敌售后😁 🧸光头强/LV/RT/橘子/葫芦娃/落叶/小烧鸡/A内核/巴巴托斯//DY/贫民窟都推荐的数据号🧸 📣点我免费领取数据号/授权号 😀😀😀😀😀😀 🔥全天在线客服联系:@KFnb666bot
👍4
Showing the 12 most recent of 107 posts we hold for @bmgwjnb. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
明天更新什么?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 107 most recent posts we hold, published 24 July 2026 to 28 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
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.
Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“北冥和平精英&PUBG《改文件》” (@bmgwjnb), 9,531 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/bmgwjnb.
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.