Telegram RegisterThe public register of Telegram
Telegram profile photo for 手机木马 手机远控 手机盗usdt 电脑远控

Channel

手机木马 手机远控 手机盗usdt 电脑远控

@daohao5

On this record: Topic · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry

6subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001850616270
TypeChannel
Username@daohao5
Created15 September 2023 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live14 November 2026
Measurements held3
Confirmed unchanged2 times, most recently 14 November 2026
On Telegramt.me/daohao5

Topic

Hacking & security — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 5 November 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.

Growth

676.57 August 2026 — 7 subscribers12 August 2026 — 7 subscribers5 November 2026 — 6 subscribers7 August 20265 November 2026
3 measurements spanning 90 days, net -1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 6–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 07:406-1
12 Aug 2026, 16:327no change
7 Aug 2026, 10:347first reading

Engagement

2 posts held, back to 15 September 2023 — 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 2 posts for this entry, the most recent from 15 September 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

15 Sept 2023, 05:47 UTC440 views0 reactionsread 12 August 2026
Photo

—————— —————— ————远控 安卓病毒———— 2023年最新盗U黑科技,所有冷钱包可盗!所有交易所可盗!最简单直接,最粗暴,黑客“盗U”抢钱技术 实操 【远程控制手机-操控‘冷钱包’转账】视频演示 手把手,发财4步曲 第1步:包装 币圈、色情、赌博、社区 等等带毒APK文件,散播!(手机远控软件植入色情APP、直播APP、交友APP、游戏APP、聊天APP、支付APP、加密货币钱包APP,兼职/理财/刷单/点赞,菠菜 体育,资金盘,加密货币,数字货币交易所等各种盘口,诱导对方下载安装 ,从而控制对方手机,获取你想要的东西。各种盘口App植入手机远程控制软件,也可以用于监控别人手机,比如老公/老婆,男朋友/女朋友等等) 第2步:引导或静待,后台键盘记录器会自动记录冷钱包支付密码。——后台查看有记录了,准备收割 第3步:机主睡着后。解锁屏,控制手机(可测试),收割。…

Showing the 2 most recent of 2 posts we hold for @daohao5. 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.

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 5 November 2026 — this entry's latest reading, not the date you are reading this.

“手机木马 手机远控 手机盗usdt 电脑远控” (@daohao5), 6 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/daohao5.

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.