Channel
@DuluYun
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
646subscribers
+76 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002229719381 |
|---|---|
| Type | Channel |
| Username | @DuluYun |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/DuluYun |
Technology — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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 |
|---|---|---|
| 15 Sept 2026, 17:58 | 646 | +22 |
| 7 Sept 2026, 02:22 | 624 | +13 |
| 29 Aug 2026, 12:28 | 611 | +17 |
| 22 Aug 2026, 14:25 | 594 | +19 |
| 15 Aug 2026, 12:35 | 575 | +5 |
| 8 Aug 2026, 03:32 | 570 | no change |
| 7 Aug 2026, 13:17 | 570 | first reading |
20 posts held, back to 28 January 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 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 20 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
11 reactions across 5 posts, in 4 distinct kinds. The most used accounts for 36.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 36.4% | |
| 👍 | 3 | 27.3% | |
| 💩 | 3 | 27.3% | |
| 👏 | 1 | 9.09% |
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 5 of the 20 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 11 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 28 January 2025 to 29 June 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.
🎉 嘟噜云 App 正式发布上线啦！ 感谢大家一直以来的支持与等待，嘟噜云多端应用现已全面发布！为了让大家获得更稳定、更便捷的使用体验，我们准备了详细的各平台下载与登录指南。 请根据您的设备类型，查看下方的具体操作步骤： 🤖 安卓（Android）与 💻 电脑端下载指南 安卓手机以及 Windows/Mac 电脑用户，操作非常简单，请直接访问我们的专属链接获取最新版客户端安装包： 下载地址： 客户端.嘟噜云.com 温馨提示： 建议直接复制上方链接，粘贴至手机或电脑的默认浏览器（如 Chrome、Edge 等）中打开，以确保下载顺利进行。 🍎 苹果（iOS）端专属配置教程 由于苹果 App Store 的区域限制，iOS 用户需要通过第三方代理客户端来进行配置，只需简单三步即可完成： 1. 获取海外 Apple ID： 请先前往嘟噜云官网，获取我们为大家免费提供的海外苹果账号（请勿使用自己的国内账号搜索）。 2. 下载 N…
❤2
嘟噜云官方通知 pinned «📢 关于暂时停用「嘟噜云」官方客户端的通知 亲爱的用户： 您好！为了保障大家的网络连接体验与安全性，即日起我们将**暂时停用嘟噜云官方专属客户端**，具体恢复上线时间将另行通知。 在此过渡期间，为了不影响您的正常使用，我们强烈建议大家切换至更加成熟、稳定且功能强大的**第三方开源客户端**。 ### 📌 推荐使用的替代客户端： * **Clash Verge**电脑（https://github.com/clash-verge-rev/clash-verge-rev/releases/download/…»
📢 关于暂时停用「嘟噜云」官方客户端的通知 亲爱的用户： 您好！为了保障大家的网络连接体验与安全性，即日起我们将**暂时停用嘟噜云官方专属客户端**，具体恢复上线时间将另行通知。 在此过渡期间，为了不影响您的正常使用，我们强烈建议大家切换至更加成熟、稳定且功能强大的**第三方开源客户端**。 ### 📌 推荐使用的替代客户端： * **Clash Verge**电脑（https://github.com/clash-verge-rev/clash-verge-rev/releases/download/v2.5.1/Clash.Verge_2.5.1_x64-setup.exe） * **Clash Meta**安卓 （https://github.com/MetaCubeX/ClashMetaForAndroid/releases/tag/Prerelease-alpha） 客户端合集下载网站：https://wiki.…
🔄 【线路全面升级 & 套餐结构调整公告】 🔄 各位群友，大家好。 感谢大家一直以来的信任与陪伴。熟悉我们的老用户都知道，最近大环境的网络封锁和线路干扰越来越严重，传统的廉价线路在晚高峰几乎不可用。 为了彻底解决“拥堵、断流、关键时刻连不上”的痛点，我们做出了一个艰难但必要的决定：全面放弃低端内卷，将整站架构升级为高端精品路线。 经过几天的调试，我们已经重金购入并部署了全新的 顶级高防专线中转服务器。现在的节点，哪怕在晚高峰也能让你丝滑秒开 4K，体验真正的“ VIP 级不拥挤”。 但极高的质量也意味着极高的成本，为了长久且健康地运营下去，我们对原有的套餐体系进行了全面重构。 （详细请看官网） 🤝 【老用户平滑过渡方案】 我们绝不背刺老朋友！ 您当前持有的旧套餐在到期前依然有效，您可以继续正常使用。只有在您当前套餐耗尽或到期后，下次续费时才需要选择全新的套餐体系。
大家好，嘟噜云已经采取新的策略协议，并且升级成功，请大家更新软件的订阅，软件如果链接不上请删除重新下载，最新下载地址： 客户端.嘟噜云.com
1x全部恢复 需要补偿的提工单 补偿50%流量
全部升级完成 95折优惠码：95zhe
💩3❤1
国庆节优惠码:GuoQing
👍1
嘟噜云官方通知 pinned «七夕节七折优惠码：7xi»
七夕节七折优惠码：7xi
已换，等dns慢慢生效
电信IP被通报，换IP中
Showing the 12 most recent of 20 posts we hold for @DuluYun. 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“嘟噜云官方通知” (@DuluYun), 646 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/DuluYun.
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.