服务维护通知 因服务器供应商进行系统维护,8 月 18 日 06:00~07:00 期间服务可能短暂不可用,不便之处敬请谅解。

Channel
网盘资源机器人使用指南
@YunPanHelp
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
8,429subscribers
-13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001581953159 |
|---|---|
| Type | Channel |
| Username | @YunPanHelp |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/YunPanHelp |
Topic
Other / unclassifiable — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 49% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 17:55 | 8,429 | -4 |
| 7 Sept 2026, 12:36 | 8,433 | +9 |
| 2 Sept 2026, 15:36 | 8,424 | -10 |
| 30 Aug 2026, 11:35 | 8,434 | -6 |
| 27 Aug 2026, 10:56 | 8,440 | +8 |
| 24 Aug 2026, 15:25 | 8,432 | -3 |
| 17 Aug 2026, 17:25 | 8,435 | +2 |
| 14 Aug 2026, 10:15 | 8,433 | -6 |
| 7 Aug 2026, 20:26 | 8,439 | -3 |
| 7 Aug 2026, 01:16 | 8,442 | first reading |
Engagement
21 posts held, back to 31 December 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 23 pages 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 21 posts for this entry, the most recent from 17 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
111 reactions across 14 posts, in 6 distinct kinds. The most used accounts for 55.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 62 | 55.9% | |
| ❤ | 37 | 33.3% | |
| 🔥 | 9 | 8.11% | |
| 👏 | 1 | 0.901% | |
| 😁 | 1 | 0.901% | |
| 😱 | 1 | 0.901% |
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 17 of the 21 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 111 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 31 December 2024 to 17 August 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.
Recent posts
Posted without readable text
📢 网页端更新 ✨ 直接从浏览器访问 👉 https://so.ataw.top · 不登录也能搜索资源 · 支持 Telegram 一键登录,同步 Telegram 机器人的数据,轻松管理不同平台的稿件 · 无需梯子即可访问 🖥 电脑端适配:宽屏侧边栏布局 + 深色主题,大屏浏览更舒适 📤 投稿更省心 · 粘贴链接自动识别内容 · 图片提交即传,无需等待 · 投稿过程中意外退出自动保留草稿 · 被拒稿可一键「修改后重投」 🔍 搜索更顺手 · 标签快捷搜索、跨平台搜索提示、自动记住常用平台 还有下拉刷新、详情页上下翻页、网页打开提速等细节优化,欢迎体验反馈 👏
❤2👍1
#更新 全新网页端上线,投稿、查找、发现资源更方便 在阿里云盘、夸克网盘或汇盘机器人的对话左下角点击“网页版”按钮即可体验!
👍6
#更新 🚀 一键投稿 “快速投稿”功能升级为“一键投稿”,资源标题由 AI 自动提取,简化投稿流程。 🕵️ 匿名投稿 可以在机器人设置中开启匿名投稿。 📊 近期热门资源 支持展示最近一天、最近一周和历史热门资源,快速了解大家都在看什么。给机器人发送“热门”或者 /popular 命令即可查看。 📚 其它改进 改进了资源搜索结果的相关性; 改进了机器人响应速度。
❤3
计划维护通知 机器人所使用的 VPS 服务商预计在北京时间 2026 年 5 月 14 日(周四)凌晨 04:00 至早上 08:00 进行网络维护,期间机器人的响应可能会短暂出现延迟,最坏情况下持续 1 小时。对您造成的不便敬请谅解。 已维护完成
#更新 使用更现代的框架和技术栈重写了机器人 @AliYunPanBot, @QuarkRobot 和 @sharepan_bot ,以便解决一些长期的技术债、跟进 Telegram 平台的新特性,以及后续引入新功能。 本次重构的首要目标是保持用户体验一致,因此使用方式保持不变。
👍2
#更新 1. 继续改进了搜索效果,支持更模糊的查询内容,更智能 2. 大幅提升了搜索性能,大多数情况下仅需几毫秒即可完成
👍8❤7
数据已经恢复完成。为了避免大量调用 API 导致被 Telegram 封号,本次没有恢复稿件的图片。
👍6❤5
故障说明 2025 年 5 月 15 日下午,bot 所在的服务器突发离线。在联系服务商重新启动服务器后,发现数据无故丢失,但服务商声称没有发现异常。因此,我们不得不使用旧的数据备份恢复服务,其中 @AliYunPanBot 回滚到 5 月 6 日左右的数据,@QuarkRobot 和 @sharepan_bot 回滚到 3 月左右的数据。 我们还将做以下措施: 1. 继续联系服务商寻求恢复数据的机会。 2. 尝试将频道中已发布的新资源导入到数据库中,作为方案 1 的后备选项。 3. 加强备份措施。 对于给您造成的影响,我们表示真挚的歉意。感谢您的理解和支持。后续进展会继续发布在本频道 (@YunPanHelp)。
👍17❤4😁1
服务器意外离线,正在联系服务商。
👏1😱1
#更新 改进了搜索性能。
Showing the 12 most recent of 21 posts we hold for @YunPanHelp. 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.
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 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“网盘资源机器人使用指南” (@YunPanHelp), 8,429 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/YunPanHelp.
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.