13 Jul 2026, 22:31 UTC386 viewsread 10 August 2026
远控盗U，商城盗U，电脑远控，私钥碰撞器，充电宝盗U 现在有空支持大家测试 支持，周购买，天购买 联系客服: @DAOHAO7
Channel
手机木马 手机远控 手机控制 电脑远控 盗USDT
@daohao8
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2,650subscribers
-28 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001616471374 |
|---|---|
| Type | Channel |
| Username | @daohao8 |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/daohao8 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 12:16 | 2,650 | -7 |
| 21 Aug 2026, 00:07 | 2,657 | -6 |
| 17 Aug 2026, 15:59 | 2,663 | -5 |
| 14 Aug 2026, 04:49 | 2,668 | -8 |
| 10 Aug 2026, 18:12 | 2,676 | -2 |
| 10 Aug 2026, 00:47 | 2,678 | first reading |
Engagement
15 posts held, back to 18 September 2025 — 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 15 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 2m 35s
- Average length
- 39s
Measured directly from 4 videos 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.
Recent posts
19 Mar 2026, 05:45 UTC≈1,380 viewsread 10 August 2026
Video
只要对方下载了我们伪装的app，如黄色网站或者博彩网站，我们就可以记录他的所有密码，还可以在他锁屏的时候输入密码打开他的屏幕操作，盗u和盗手机银行支付宝微信，就完全在自己掌控之中了！ 联系客服 : @daohao7 联系客服 : @daohao7 联系客服 : @daohao7
15 Mar 2026, 01:26 UTC≈1,260 viewsread 10 August 2026
Photo
【赚钱新项目有手机就能自动赚钱】 Fbi破解加密货币钱包碰撞器2024apk（安卓设备适配） 特征 -可在安卓设备上运行 -便于使用，操作简单 -4 种加密货币区块链 -只检查真实钱包 -可安装多台设备同步运行软件 -获得钱包的百分比非常高。 一周用了10台安卓手机赚了20多万 想了解项目的 联系客服： @daohao7
12 Mar 2026, 15:23 UTC977 viewsread 10 August 2026
有时间免费测试 联系客服 @daohao7
11 Mar 2026, 05:45 UTC≈1,080 viewsread 10 August 2026
Photo
https://v.kuaishou.com/2BFXipw 惊魂时刻！00后睡梦中被贷款49920元，又眼看手机自动输密码转走钱 "大象主播说 有钱卡扣 无钱京东白条贷款 都是只需要四要素 即可出款！ 无需支付密码！ 测试联系客服: @daohao7
8 Mar 2026, 10:45 UTC947 viewsread 10 August 2026
1. 手机远控· 2. 授权多签盗U · 3. 扫码二维码盗U· 4. 假钱包盗U · 5. 碰撞器盗U · 6. 电脑远控剪切板盗U · 7. 手机充电宝盗U· 在线客服 @daohao7
4 Mar 2026, 06:32 UTCviews —
手机木马 手机远控 手机控制 电脑远控 盗USDT pinned Deleted message
4 Mar 2026, 03:59 UTC≈1,090 viewsread 10 August 2026
Video
私钥碰撞器，挂机坐等赚钱！ 买了它等于买了一个24小时彩票机 不停的开奖，运气好大奖就来了 活动中！！！ 需要的联系客服 @daohao7
2 Mar 2026, 02:52 UTC≈1,010 viewsread 10 August 2026
远控盗U，商城盗U，电脑远控，私钥碰撞器，充电宝盗U 现在有空支持大家测试 支持，周购买，天购买 联系客服: @DAOHAO7
17 Feb 2026, 01:38 UTC≈1,220 viewsread 10 August 2026
联系 @daohao7
15 Feb 2026, 07:51 UTC≈1,260 viewsread 10 August 2026
有时间测试 联系客服 @daohao7
2 Nov 2025, 10:19 UTC≈3,420 viewsread 10 August 2026
有时间测试 联系客服 @daohao7
Showing the 12 most recent of 15 posts we hold for @daohao8. 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
Citation-graph rank — 319,985 of 1,604,598entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
Named by 3 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.
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.
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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“手机木马 手机远控 手机控制 电脑远控 盗USDT” (@daohao8), 2,650 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/daohao8.
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.