Channel
@dudun_qunfa
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
156subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001372325978 |
|---|---|
| Type | Channel |
| Username | @dudun_qunfa |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/dudun_qunfa |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 14 Sept 2026, 06:55 | 156 | -2 |
| 28 Aug 2026, 18:17 | 158 | -2 |
| 15 Aug 2026, 02:12 | 160 | -3 |
| 8 Aug 2026, 16:45 | 163 | no change |
| 7 Aug 2026, 18:14 | 163 | first reading |
15 posts held, back to 7 January 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 15 posts for this entry, the most recent from 18 March 2026. An engagement rate over an empty window would be a number about nothing.
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 3 of the 15 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 15 most recent posts we hold, published 7 January 2026 to 18 March 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.
🚀 系统公告 🚀 新增功能：用户名群关系查询 🔍 功能简介 输入 Telegram 用户名（例如 daoxu 或 @daoxu），即可查询该账号的深度关联数据： • 😇 基础信息：用户ID、历史用户名及变更记录 • 🔗 关联数据：关联账号ID、绑定手机号 • 👥 群组列表：账号所在的所有群组及身份属性（管理员/普通成员） • 📅 历史轨迹：用户名历史变更详情、个人签名历史 • 🍇 使用说明 • ⌨️ 查询方式：在输入框内提交用户名即可 • 📊 查询限制：每日 15 次，页面实时显示剩余次数 • ⏱ 响应时间：首次查询约 1-2 分钟，已缓存数据即时返回 ps：那种开小号来找试用的就别找我了，还不够烦的呢兄弟。。。 都挺忙的
服务器已经更新完成。。。
服务器升级中，预计半小时更新完成
新年快乐！！😇😇😇😇
🔄 版本更新公告 亲爱的用户，本次更新带来以下优化与改进，旨在提升您的使用体验： ✅ 优化稳定性 修复了已知的偶发性闪退问题 增强了整体系统稳定性，运行更顺畅 ✅ 加群支持自定义线程 现在在加群操作中，您可以自定义线程数量 根据自身需求灵活调整，提高加群效率 ✅ 链接时间优化至24小时不断开 连接保持时间显著延长，避免频繁重连 支持24小时持续在线，提升长时间使用体验 ✅ 优化内部AI处理细节 改进了AI消息处理逻辑，响应更智能 修复了部分场景下回复不准确的问题 感谢您一直以来的支持！如有问题或建议，欢迎反馈给我们。祝您使用愉快！
1. 优化群发稳定性 2. 更改启动方式 3. 优化t g
由于骗子太多，后续交易认准唯一NFT：@daoxu（道虚） 认准888 在进行交易
云控稳定强拉中。。。嘎嘎稳定。
TG云控(控AI)官方频道 系统更新 pinned Deleted message
一些顾客反馈云控的封频道实况， 注意：本人不代封任何频道。
1. 私信新增视频 2. 私信增加音频 3. 优化登录页面
已过新币公群验证/小微验证，等等各种，高达市面百分之90的群🐮🐮🐮 支持边加群边发消息
❤1
Showing the 12 most recent of 15 posts we hold for @dudun_qunfa. 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.
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.
Named by 2 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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“TG云控(控AI)官方频道 系统更新” (@dudun_qunfa), 156 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/dudun_qunfa.
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.