主号被封需要的联系@hanjie89896
Signed 韩杰

Channel
@yuankon11
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Handles named that no longer answer · Cite this entry
268subscribers
-2,100 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003822084137 |
|---|---|
| Type | Channel |
| Username | @yuankon11 |
| Created | Between 1 February 2026 and 8 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/yuankon11 |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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 |
|---|---|---|
| 3 Oct 2026, 02:39 | 268 | -208 |
| 19 Sept 2026, 05:20 | 476 | -391 |
| 10 Sept 2026, 23:38 | 867 | -158 |
| 5 Sept 2026, 23:40 | 1,025 | -139 |
| 2 Sept 2026, 00:37 | 1,164 | -87 |
| 30 Aug 2026, 10:48 | 1,251 | -145 |
| 27 Aug 2026, 16:15 | 1,396 | -162 |
| 24 Aug 2026, 08:03 | 1,558 | -137 |
| 21 Aug 2026, 02:35 | 1,695 | -85 |
| 18 Aug 2026, 01:42 | 1,780 | -208 |
| 14 Aug 2026, 19:26 | 1,988 | -118 |
| 11 Aug 2026, 15:14 | 2,106 | -185 |
| 8 Aug 2026, 19:08 | 2,291 | -77 |
| 7 Aug 2026, 20:17 | 2,368 | no change |
| 7 Aug 2026, 19:24 | 2,368 | first reading |
14 posts held, back to 8 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 14 posts for this entry, the most recent from 17 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 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.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 100.0% |
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 2 of the 14 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 8 June 2026 to 17 July 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.
主号被封需要的联系@hanjie89896
Signed 韩杰
30都没有还看片
龙控一套测试的来
安卓远控网页版 国内天花板 支持开通子账单多人同时操控支持八大行密码记录➕冷钱包密码记录 对比国内其他控增加的功能和特点 1, 网页版支持开通子账单多人同时使用 2,黑屏操作增加系统升级的图案,减少了鱼乱动手机的情况 “实现黑屏时显示本手机自带的LOOG,更加逼真,白天鲨鱼不是梦” 3,弹窗➕注入功能,强制弹窗自定义文字让鱼打开指定app,注入界面对应的app输密码界面,(例如zfb,wx,八大行,冷钱包。“以上功能全网独家” 4,真实实现了卸载隐藏,和安装后直接隐藏,客户亲自卸载掉毒包依然可控 不掉线,提升了很高的保鸡率! (实现多种构建模式自定义选择) 5,不止控端是网页版使用,包括构建器全部在网页实现。安全(可实现后台独立构建操作,做包不求人,不限制做包数量,不限制内容。) 6,增加了很多适配机型,优化了电池策略。(解决远控权限拿不完整,有些权限拿不到情况,包机不稳定情况) 其次就不做过多介绍了简单举例功能…
这个鱼真能熬
偶遇币圈大佬
全面升级,免杀,谷歌,超长保机
上货
Video, posted without a caption
这老女人
Signed 顺鑫
专注远控 pinned «杀鱼方法 客户下载完成后,检查一下无障碍是否已经打开完成控制住了 进入短信记录(可查看手机号/银行卡余额截图下来)及相册 查到客户讯息 1:手机号 2:证件(证号及有效日) 3:生活照 4:银行卡余额在他的短信里面就可以查看 进入键盘记录查看等讯息 1:屏幕解锁密码 2:银行卡号 3:微信登入密码/支付密码 4:支付宝 登入密码/支付密码 等相关讯息 ---- 采集重要信息: 1:姓名 2:手机号 3:身份证号码 4:身份证有效期 5:生活照正脸 6:银行卡号及余额 7:微信/支付宝 支付密码…»
杀鱼方法 客户下载完成后,检查一下无障碍是否已经打开完成控制住了 进入短信记录(可查看手机号/银行卡余额截图下来)及相册 查到客户讯息 1:手机号 2:证件(证号及有效日) 3:生活照 4:银行卡余额在他的短信里面就可以查看 进入键盘记录查看等讯息 1:屏幕解锁密码 2:银行卡号 3:微信登入密码/支付密码 4:支付宝 登入密码/支付密码 等相关讯息 ---- 采集重要信息: 1:姓名 2:手机号 3:身份证号码 4:身份证有效期 5:生活照正脸 6:银行卡号及余额 7:微信/支付宝 支付密码 8:支付宝信用分 9:花呗/借呗额度 10:美团额度 11:京东额度 12:云闪付 都采集完毕后查看摄像头客户是否使用手机 如无使用手机 查看解锁密码是数字还是图案密码 进行屏幕阅读解锁屏幕 进入远程屏幕 黑屏设置-默认 1:设置上面收寻键盘/支付/误触 (键盘安全/支付安全) 都要关闭 移动网路-查看SIM卡手机…
❤1
Signed 顺鑫
Showing the 12 most recent of 14 posts we hold for @yuankon11. 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.
@yuankon11 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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“专注远控” (@yuankon11), 268 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/yuankon11.
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.