大量收王者抓包号,库存号,正常多少结多少,目前6一个 @MOBOCC
👍7

Channel
@BHCNB7
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
8,409subscribers
-487 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002237130723 |
|---|---|
| Type | Channel |
| Username | @BHCNB7 |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/BHCNB7 |
Gaming — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 33% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 08:18 | 8,409 | -27 |
| 11 Sept 2026, 07:39 | 8,436 | -40 |
| 6 Sept 2026, 15:56 | 8,476 | -47 |
| 1 Sept 2026, 23:16 | 8,523 | -39 |
| 29 Aug 2026, 20:13 | 8,562 | -25 |
| 27 Aug 2026, 01:43 | 8,587 | -49 |
| 23 Aug 2026, 23:33 | 8,636 | -51 |
| 20 Aug 2026, 06:12 | 8,687 | -39 |
| 17 Aug 2026, 15:24 | 8,726 | -54 |
| 14 Aug 2026, 07:55 | 8,780 | -39 |
| 11 Aug 2026, 10:12 | 8,819 | -74 |
| 7 Aug 2026, 23:28 | 8,893 | -3 |
| 7 Aug 2026, 11:33 | 8,896 | first reading |
21 posts held, back to 14 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 28 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.
| Window | Rolling 30 days · latest post in window 24 August 2026 |
|---|---|
| Posts held | 21 (14 June 2026 – 24 August 2026) |
| Views total | 122 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 16: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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
30 reactions across 11 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 15 | 50.0% | |
| ❤ | 14 | 46.7% | |
| 🤔 | 1 | 3.33% |
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 11 of the 21 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 30 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 14 June 2026 to 24 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.
大量收王者抓包号,库存号,正常多少结多少,目前6一个 @MOBOCC
👍7
😃😃😃😃😃😃😃😃😃😃 😂全网唯一一款云控和平全自动验号脚本公益了———JO公益😂 📣📣目前已经做了好几个赛季了,长期稳定,无任何卡点,验号速度全网最快,支持过滤所有问题,目前测试1w个号适配了和平全部弹窗,只为给号商一个家 ✅和平数据号圈迎来了新时代,使用此脚本测试验出来的号基本上都没有问题,80%验好直接上卡网即可,网页控制脚本和添加需要验的号,网页一键操作,验好后也是网页导出即可✅ 🌟🌟目前支持各大云机,打压和平数据号圈市场,不用人工手动验号了🌟🌟 ⚠️速度加入频道获取脚本⚠️ https://t.me/JOJB91 https://t.me/JOJB91 https://t.me/JOJB91
❤1
全网避雷7S数据号,供货商钱都能圈,还是人?这种cs都不知道卡网是什么垃圾号,供货商都圈看来卡网也好不到哪去,一个号供货才1.8,硬是圈了别人300来块钱的
❤1
直登号@BHNB0.txt
📣冰花数据号📣 🔥今日正式进入挂圈和数据号圈,希望各位多多包涵,也希望各位多多支持一下冰花,我会用实际的行动和真实的自己给各位服务以及我们数据号质量和划算的价格会倾向于谁都买得起,玩得起数据号🔥 ✅不进行夸张宣传是风范,不抬价格是良心,不做无良是本分,售后到位是真诚✅ 👈在此邀请各位加入我的频道👈 🌟 官方频道 🌟 🌟 官方频道 🌟 🌟 官方频道 🌟 🌟 官方频道 🌟🌟 官方频道 🌟 🌟 官方频道 🌟
❤1
各位号商,有王者号的可以卖我,我这边大量收,脚本自动验,正常多少给各位结算多少 @DENDH1
❤2
😃😃😃😃😃😃😃😃😃😃 😂全网唯一一款云控和平全自动验号脚本公益了———JO公益😂 📣📣目前已经做了好几个赛季了,长期稳定,无任何卡点,验号速度全网最快,支持过滤所有问题,目前测试1w个号适配了和平全部弹窗,只为给号商一个家 ✅和平数据号圈迎来了新时代,使用此脚本测试验出来的号基本上都没有问题,80%验好直接上卡网即可,网页控制脚本和添加需要验的号,网页一键操作,验好后也是网页导出即可✅ 🌟🌟目前支持各大云机,打压和平数据号圈市场,不用人工手动验号了🌟🌟 ⚠️速度加入频道获取脚本⚠️ https://t.me/JOJB91 https://t.me/JOJB91 https://t.me/JOJB91
❤2
免费定制上号器三合一,过滤器等 @BHCZZ2
❤3👍2🤔1
🥰冰红茶最新自动抓号器2.0版本发布🥰 ❤️最新2.0版本,加入防卡二维码以及扫码提示❤️ ⭐功能和UI和以前一样,过滤模式支持100线程最快过滤⭐ 抓号模式内置了全部游戏 使用简单 😇🙃😉 @BHCDD1 https://t.me/BHCDD1 https://t.me/BHCDD1 https://t.me/BHCDD1 https://t.me/BHCDD1
❤1
低价进
👍4
借个快手号 发的作品内容是和平精英打地铁的视频 必须要有热度 这两个月给你1000-3000 有意的d 只发和平游戏的 无违规 只要一个 联系 @gddyyds
❤3
GDD数据号 pinned a photo
Showing the 12 most recent of 21 posts we hold for @BHCNB7. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
@BHCNB7 named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“GDD数据号” (@BHCNB7), 8,409 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/BHCNB7.
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.