Channel
@BBXIM
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,936subscribers
+892 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004414531852 |
|---|---|
| Type | Channel |
| Username | @BBXIM |
| Created | 20 June 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/BBXIM |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 83% 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, 17:58 | 1,936 | +19 |
| 12 Sept 2026, 05:56 | 1,917 | +47 |
| 8 Sept 2026, 07:02 | 1,870 | +139 |
| 2 Sept 2026, 22:24 | 1,731 | -45 |
| 31 Aug 2026, 06:34 | 1,776 | +114 |
| 28 Aug 2026, 02:13 | 1,662 | +76 |
| 25 Aug 2026, 01:33 | 1,586 | +149 |
| 21 Aug 2026, 10:06 | 1,437 | +484 |
| 13 Aug 2026, 13:37 | 953 | -91 |
| 12 Aug 2026, 18:31 | 1,044 | first reading |
5 posts held, back to 20 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 1 page of 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 5 posts for this entry, the most recent from 27 June 2026. An engagement rate over an empty window would be a number about nothing.
⭕️【海华万金友季度供应】 🖥供应商品：bbx出海/IM手工粉 🇺🇸美掴兼职粉 3000+ 🇺🇸美掴兼职粉 3000+ 也可以供双向短信渠道 📣商品介绍：.保真保量可视频回访！永远不受风控限制！稳定出粉！T卡也可以发！不限制运营商！ 📱联系方式：@bbx_owner 海华公群：https://t.me/+iVPW1SE2GJwxZjI0 频道：https://t.me/BBXIM 🛡交易方式：支持海华担保交易
比比熊iMessage / SMS 群控接码系统 · 功能清单 主营：iMessage + 短信(SMS) 多设备集中管控 · 接码取号 · 自动推送系统 1. 设备管理 — 多 iPhone 集中接入、真实在线状态、WiFi Calling 状态监测、设备远程断开/刷新、按设备名/号码搜索 2. 账号管理 — iMessage / SMS 账号自动同步、激活与注册状态识别、掉线重连自动归位原分组、账号成熟度统计 3. 分组管控 — 父/子分组树形管理、账号批量分组与迁移、分组级数据隔离、按分组绑定接码密钥 4. 接码取号 API — 随机在线号取号、按号码取验证码、号码状态查询、号码释放、号码历史验证码批量查询、号码锁定时长可配 5. 接码密钥 — 多密钥独立管理、密钥绑定分组授权、按密钥限定可访问号码范围 6. 批量推送 — 推送任务批量下发、推送规则引擎、任务进度跟踪、发送/送达/失败/回复统计 7. 自动回…
⭕️【海华万金友季度供应】 🖥供应商品：bbx出海/IM手工粉 🇺🇸美掴兼职粉 3000+ 🇺🇸美掴兼职粉 3000+ 也可以供双向短信渠道 📣商品介绍：.保真保量可视频回访！永远不受风控限制！稳定出粉！T卡也可以发！不限制运营商！ 📱联系方式：@bbx_owner 海华公群：https://t.me/+dvrw1y4B28s4YjFk 频道：https://t.me/BBXIM 🛡交易方式：支持海华担保交易
🇺🇸 美区双 Yes 兼职粉 🇺🇸 —— 日产 5000+ 现货供应！ 🚀 【更灵活】 料子你定，话术你定，年龄你定！我们只负责高效率执行！ ⚙️ 【更专业】 百人团队手动代打，万台设备同时开工。 不管行情怎么变，我们这里全年无休！ 🛡 【更靠谱】 不敢视频验证的都是虚的！ 我们支持视频验证、支持现场考察！
Channel created
Showing the 5 most recent of 5 posts we hold for @BBXIM. 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.
Named by 1 registered channel — 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“BBX-IM出海工作室” (@BBXIM), 1,936 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/BBXIM.
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.