Channel
@Hubao88
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
17,501subscribers
-226 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001518822760 |
|---|---|
| Type | Channel |
| Username | @Hubao88 |
| Created | Between 1 August 2021 and 19 March 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 August 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 27 August 2026 |
| On Telegram | t.me/Hubao88 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Aug 2026, 06:37 | 17,501 | -6 |
| 26 Aug 2026, 04:46 | 17,507 | -8 |
| 25 Aug 2026, 06:52 | 17,515 | -11 |
| 24 Aug 2026, 05:17 | 17,526 | -20 |
| 22 Aug 2026, 12:02 | 17,546 | -15 |
| 21 Aug 2026, 01:25 | 17,561 | -11 |
| 19 Aug 2026, 21:54 | 17,572 | -15 |
| 18 Aug 2026, 19:02 | 17,587 | -20 |
| 17 Aug 2026, 15:36 | 17,607 | -26 |
| 16 Aug 2026, 08:54 | 17,633 | -15 |
| 14 Aug 2026, 19:44 | 17,648 | -18 |
| 13 Aug 2026, 08:33 | 17,666 | -12 |
| 12 Aug 2026, 11:07 | 17,678 | -12 |
| 11 Aug 2026, 12:46 | 17,690 | -4 |
| 10 Aug 2026, 14:51 | 17,694 | -13 |
| 9 Aug 2026, 14:17 | 17,707 | -6 |
| 8 Aug 2026, 17:37 | 17,713 | -13 |
| 7 Aug 2026, 20:12 | 17,726 | -1 |
| 7 Aug 2026, 01:30 | 17,727 | no change |
| 7 Aug 2026, 01:20 | 17,727 | first reading |
20 posts held, back to 19 March 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 44 pagesof 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 18 September 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 28 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
✅ 人工付费查询 👍效率出单👌 开房纪录 / 同住纪录 身分证使用纪录轨迹（人鬼） 身分证大关联 / 手机定位 微信反查绑定电话（注册时的） 飞机/火车/高铁监控👈抓人神器 菠菜业 营销神器 👈赚钱利器 手机大关联地址👈寻人神器 银行流水 / 名下资产银行卡余额 联通 / 电信 / 移动 通话纪录 微信好友提取 / QQ好友提取 婚姻纪录 / 全户信息 身分证复印件 / 户籍信息 模糊查找身分号 银行卡冻结原因查询 名下电话 外卖收货地址查询 👉价格表👈 💰USDT / BTC购买教学💰 📣 预存活动进行中🎉🎉🎉 🤭新年调查优惠活动 限时进行中🥳 🧏🏻♂️ 报单经发现为 🙇 ❌钓鱼单 ❌领导单 ❌名人 ❌记者单 ❌诈骗用途单 ✅一律收款 🙅🏻不退费 🙅🏻♂️不出单 🙆🏻请把资源留给真正有需求的人 ⚠️收款方式每日更新⚠️ ⚠️私自打款 一律不认⚠️ 需要的请手刀👉 @SGKGO
想找人却找不到？ 想查他的资产产背景却没门路？ 菠菜行业没客户碰到瓶颈？ 我们专业团队有解决方案！ 👉价格表 立即联系我们！ 让您的问题迎刃而解！共创成功！ 👉 @SGKgo
公安 - 快递 - 银行 在这些地方上班的朋友 来找我带你赚金豆子 👉合作安全 无忧 详情内洽 @SGKgo
强力征求！ 强力征求微信好友提取渠道 日收百单起 安全无忧 👇 @SGKgo
不用再猜！ 手机定位变得更加准确、快速， 就在我们这里！ 只需要提供手机号码，就能够获得极其准确的定位数据。立即来试试吧！ （基站定位 有误差属正常现象） @SGKgo
“博彩舞台，对手防不胜防，获取对手客户资源，业界首选！携手共进，胜利共享，博彩公司的梦幻神队友” 博彩营销方案 详情内洽 @SGKgo
重金寻求： 公安 - 快递 - 银行 在这些地方上班的朋友 来找我带你赚金豆子 👉合作安全 无忧 详情内洽 @SGKgo
样本频道 pinned «⚠️报单重要需知👇🏼 公检法 军人及其家属 明星 记者 网红 记者 富商 富豪 逝者 公务员 央企 国企 事业单位 以上一律视为敏感 正常收费用 单不出»
⚠️报单重要需知👇🏼 公检法 军人及其家属 明星 记者 网红 记者 富商 富豪 逝者 公务员 央企 国企 事业单位 以上一律视为敏感 正常收费用 单不出
本频道友情提醒：在TG请勿信任任何模仿机器人，以免造成财产损失，近期已有大量用户遭遇类似骗局，真正做到完全免费的机器人仅有本频道机器人。
7/11最新价格项目表📅 下单热线 ✅ 直接索取USDT地址下单 👉 @SGKgo 👈
非常抱歉的通知您，不可抗因素影响，机器人及官方频道无限期停用，后续事宜将于本频道通知。您的信息安全不受影响。 人工高级查询业务不受影响👉 @SGKGO
Showing the 12 most recent of 20 posts we hold for @Hubao88. 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.
Citation-graph rank — 463,651 of 1,621,754entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 27 August 2026 — this entry's latest reading, not the date you are reading this.
“样本频道” (@Hubao88), 17,501 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/Hubao88.
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.