最新 😀 @epan 主机器人刚才炸掉了,已经更换了新的主机器人。所有跳转链接和功能都不受影响。 😀 唯一受影响的是进群验证功能,需要重新拉 @epan_filesbot 机器人进群。(使用进群验证的需要注意更换机器人) 😀 @epan 用户名已经指向 @epan_filesbot ,但是电脑客户端可能存在缓存,所以有的依旧跳转到老机器人。手机客户端不存在此问题,过一两天电脑客户端缓存应该就改正过来了。 @epan 点击跳转老机器人的,清理客户端缓存,重启客户端基本可以恢复正常。

Channel
易盘网盘文件助手
@files
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
680subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002943064651 |
|---|---|
| Type | Channel |
| Username | @files |
| Created | Between 1 August 2025 and 24 August 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/files |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 16:39 | 680 | no change |
| 6 Aug 2026, 13:53 | 680 | first reading |
Engagement
7 posts held, back to 24 August 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 pageof 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 7 posts for this entry, the most recent from 10 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 2
Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
最新 😀 @epan 主机器人刚才炸掉了,已经更换了新的主机器人。所有跳转链接和功能都不受影响。 😀 唯一受影响的是进群验证功能,需要重新拉 @epanXfile_bot 机器人进群。(使用进群验证的需要注意更换机器人) 😀 @epan 用户名已经指向 @epanXfile_bot ,但是电脑客户端可能存在缓存,所以有的依旧跳转到老机器人。手机客户端不存在此问题,过一两天电脑客户端缓存应该就改正过来了。 @epan 点击跳转老机器人的,清理客户端缓存,重启客户端基本可以恢复正常。
易盘网盘文件助手 pinned a photo
@epan 网盘机器人已上线
🥰 大家好,新的网盘机器人开发进度会在这里同步,可以看频道用户名购买价格,资金充足,足以保障服务稳定运行。 我们为网盘机器人 @QQyunbot 作者提供了服务器费用,暂时继续提供给大家使用。 大概一个月后,我们开发一个新的机器人取代这个机器人。新的机器人开发进展会在 @files 进行通知 需要备份数据的也抓紧备份,新机器人不会继承数据。
Messages in this channel will no longer be automatically deleted
Messages in this channel will be automatically deleted after 1 week
Showing the 7 most recent of 7 posts we hold for @files. 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.
Citation-graph rank
Citation-graph rank — 591,505 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Mentions
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@files named 2 handles 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“易盘网盘文件助手” (@files), 680 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/files.
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.