Telegram RegisterThe public register of Telegram
Telegram profile photo for MoviePilot频道

Channel

MoviePilot频道

@moviepilot_channel

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

19,978subscribers

+568 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001982378421
TypeChannel
Username@moviepilot_channel
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 November 2026
Measurements held60
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/moviepilot_channel

Topic

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 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.

Growth

19,41019,97819,6947 August 2026 — 19,410 subscribers8 August 2026 — 19,418 subscribers9 August 2026 — 19,420 subscribers10 August 2026 — 19,423 subscribers11 August 2026 — 19,433 subscribers12 August 2026 — 19,445 subscribers13 August 2026 — 19,449 subscribers14 August 2026 — 19,454 subscribers16 August 2026 — 19,480 subscribers17 August 2026 — 19,488 subscribers18 August 2026 — 19,493 subscribers19 August 2026 — 19,502 subscribers20 August 2026 — 19,513 subscribers21 August 2026 — 19,511 subscribers22 August 2026 — 19,517 subscribers24 August 2026 — 19,531 subscribers25 August 2026 — 19,538 subscribers26 August 2026 — 19,543 subscribers27 August 2026 — 19,559 subscribers29 August 2026 — 19,560 subscribers30 August 2026 — 19,563 subscribers31 August 2026 — 19,559 subscribers1 September 2026 — 19,560 subscribers2 September 2026 — 19,563 subscribers3 September 2026 — 19,579 subscribers5 September 2026 — 19,602 subscribers8 September 2026 — 19,621 subscribers11 September 2026 — 19,636 subscribers13 September 2026 — 19,637 subscribers15 September 2026 — 19,653 subscribers17 September 2026 — 19,671 subscribers19 September 2026 — 19,690 subscribers26 September 2026 — 19,745 subscribers4 October 2026 — 19,784 subscribers9 October 2026 — 19,791 subscribers13 October 2026 — 19,831 subscribers14 October 2026 — 19,836 subscribers15 October 2026 — 19,847 subscribers16 October 2026 — 19,859 subscribers17 October 2026 — 19,868 subscribers18 October 2026 — 19,878 subscribers19 October 2026 — 19,881 subscribers20 October 2026 — 19,892 subscribers22 October 2026 — 19,900 subscribers23 October 2026 — 19,899 subscribers24 October 2026 — 19,898 subscribers25 October 2026 — 19,907 subscribers26 October 2026 — 19,918 subscribers27 October 2026 — 19,931 subscribers28 October 2026 — 19,940 subscribers29 October 2026 — 19,942 subscribers31 October 2026 — 19,943 subscribers1 November 2026 — 19,946 subscribers3 November 2026 — 19,950 subscribers3 November 2026 — 19,957 subscribers5 November 2026 — 19,959 subscribers6 November 2026 — 19,964 subscribers7 November 2026 — 19,971 subscribers8 November 2026 — 19,974 subscribers9 November 2026 — 19,978 subscribers7 August 20269 November 2026
60 measurements spanning 94 days, net +568. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 19,325–20,063 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 60
Measured (UTC)SubscribersChange
9 Nov 2026, 17:0919,978+4
8 Nov 2026, 09:4819,974+3
7 Nov 2026, 01:0719,971+7
6 Nov 2026, 02:0119,964+5
5 Nov 2026, 00:4919,959+2
3 Nov 2026, 22:0619,957+7
3 Nov 2026, 00:0719,950+4
1 Nov 2026, 22:1519,946+3
31 Oct 2026, 18:3919,943+1
29 Oct 2026, 14:3619,942+2
28 Oct 2026, 13:1119,940+9
27 Oct 2026, 09:4419,931+13
26 Oct 2026, 12:4519,918+11
25 Oct 2026, 09:2119,907+9
24 Oct 2026, 05:4719,898-1
23 Oct 2026, 02:1819,899-1
22 Oct 2026, 01:1919,900+8
20 Oct 2026, 16:5819,892+11
19 Oct 2026, 13:5119,881+3
18 Oct 2026, 15:4819,878first reading

Engagement

46 posts held, back to 23 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 71 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
35.0%
avg views ÷ 19,978 subscribers
Avg views / post
7,000
15 posts measured
Reaction rate
0.258%
reactions ÷ views · ER floor
Posts in window
15
of 46 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 November 2026
Posts held46 (23 June 2026 – 6 November 2026)
Views total104,950
Reactions total271
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Nov 2026, 15:37 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
26
Videos
4
Links
61

Lifetime counters from Telegram’s own channel header, read 10 November 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.

Video runtime
46s
Average length
46s

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.

Reaction mix

1,057 reactions across 46 posts, in 10 distinct kinds. The most used accounts for 51.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍54251.3%
❤37435.4%
🎉868.14%
🫡181.70%
😨171.61%
👏70.662%
💅50.473%
🥰40.378%
🗿30.284%
🏆10.095%

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 46 of the 46 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,057 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 46 most recent posts we hold, published 23 June 2026 to 6 November 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

Telegram’s own ‘edited’ marker: 3 of 15 posts held from the last 30 days (20.0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

6 Nov 2026, 22:38 UTC≈3,610 views14 reactionsread 10 November 2026

🚀v3.2.5 更新内容 • 下载与订阅:修复合集缺集被误记为已下载、订阅提前完成的问题;Transmission 支持临时通信故障自动重连重试。 • 整理与网盘:完善远程存储覆盖整理的文件命名,修复 115 等存储的重命名兼容问题。 • 媒体库:限制 Emby/Jellyfin 异常剧集范围展开,避免同步时内存暴涨。 • 站点兼容:适配 HDChina 新站 RSS,修复 CSPT 流量统计,以及 HTTP 跳转 HTTPS 时丢失登录 Cookie 的问题。 • AI 助手:补齐模型请求超时限制,修复历史会话选择记录的时间和兼容加载。 • 运行稳定性:主动回收闲置浏览器会话,完善持久事件独立投递与重试,减少重复执行。 • 插件管理:修复启动时插件恢复异常;更新插件时保留文件夹、筛选、排序和滚动位置。 • 界面提示:修复浅色玻璃主题下提示文字不清晰的问题;AppPush 改用 MoviePilot 图标。 • App 兼容与…

👍9❤5

5 Nov 2026, 04:58 UTC≈4,750 views50 reactionsread 10 November 2026

🚀 MoviePilot iOS 官方客户端 ❤️ 感谢热心网友帮忙上架了 TestFlight,v1.1.3 及后续版本将支持App原生消息推送(需在 设定-通知 渠道添加 AppPush)。 邀请链接:https://testflight.apple.com/join/S2F8nY8N

👍41❤9

3 Nov 2026, 23:59 UTC≈5,120 views15 reactionsread 10 November 2026

🚀 v3.2.4 更新内容 • 新增搜索诊断,展示资源匹配、过滤原因及规则未适用提示,订阅卡片显示更明确的搜索状态。 • 优化订阅搜索与下载,避免异常站点拖住整体任务,修复累计集数区间匹配,按配置的目录优先级选择下载位置。 • 修复整理后的订阅与日历入库状态同步,正确区分“已入库”和“洗版完成”,跳过整理的文件不再误记为入库成功。 • 新增通过 API/MCP 登记外部已完成整理的历史记录,支持复制、硬链接和移动结果核验及登记审计。 • 修复 Emby、Jellyfin 媒体库分页同步,避免大型媒体库同步不完整。 • 修复部分站点首次下载确认跳转;改用 AniList 官方 API 并缓存中文标题,完善动漫标题识别。 • 提升插件安装与更新稳定性:切换页面不再中断安装,强制更新重新读取市场索引,避免装回旧版,并完善插件生命周期并发管理。 • 新增版本化插件前端 SDK,方便插件复用宿主组件、交互及原生能力。 • 修复智能助手会…

👍10❤5

31 Oct 2026, 07:31 UTC≈6,720 views15 reactionsread 10 November 2026

🚀 v3.2.3 更新内容 • 修复自定义剧集组的缺集计算,恢复订阅严格媒体身份匹配,减少同名内容误匹配。 • 搜索与下载共享站点流控,完善频控提示,减少无效重试。 • 修复缺少元数据时整理任务的异常与结算问题,以及 Agent 定时任务的执行账号归属。 • 加强 API、文件管理及云盘操作的权限与目标校验。 • 完善 App 业务通知投递、海报和完整正文展示,修复重启、重新登录后的通知误解绑。 • 优化升级弹窗按钮文案与加载状态显示。 • 新增匿名 iOS App 安装版本统计,遵循“分享使用统计”开关。 • iOS App 支持保存和切换多个服务,分别保留登录状态,并可选择使用本机钥匙串记忆账号密码。 • iOS App 优化服务列表与圆形左滑删除按钮,修复搜索返回时导航中断、系统明暗切换后顶部渐变异常。 • iOS App 改善启动恢复,增加等待提示、“立即重试”和“更改地址”,完善启动请求超时与重试。 • 修复数据库操…

❤10👍5

29 Oct 2026, 10:46 UTC≈6,910 views9 reactionsread 10 November 2026

🚀 v3.2.2 更新内容 • 插件市场支持安装前查看使用说明,完善文档入口和作者头像展示。 • 字幕筛选支持“中字”和“特效”,兼容已有筛选设置。 • 新增 Obscurify.ai 大模型服务商。 • 优化 Agent 在兼容 Responses 接口下的缓存复用,修复 Telegram 等渠道的命令回执投递。 • 修复历史整理任务恢复、结果结算及缺少元数据导致的异常,避免重复创建待处理任务。 • 插件 Release 安装支持 GitHub 镜像下载,完善超时、异常回退和安装方式偏好处理。 • 修复站点重定向异常中断 CookieCloud 同步等批量操作的问题。 • 改善浅色主题下媒体卡片的文字对比度。

❤7👍2

26 Oct 2026, 23:05 UTC≈8,380 views22 reactionsread 10 November 2026

📱 MoviePilot iOS 官方客户端 MoviePilot-App 将熟悉的 MoviePilot 功能带到 iPhone,结合系统原生导航、搜索与快捷面板,支持侧滑返回、卡片长按操作和原生弹窗,iOS 26+ 更可体验 Liquid Glass。 沿用现有业务页面和插件界面,并提供多实例连接、桌面及锁屏小组件,让日常管理更顺手。 请先将 MoviePilot 更新至 v3.2.0 或更新的兼容版本,需要自己完成IPA签名,安装后输入实例地址,使用原有账号登录。 📦 下载安装包 📖 安装与自动续签说明 🔗 连接与使用说明 ✨ 项目介绍 · 界面预览

❤19👍3

26 Oct 2026, 23:05 UTC≈6,930 views4 reactionsread 10 November 2026

🚀 v3.2.1 更新内容 • 优化媒体卡片状态查询和配置读取,减少重复请求及后台轮询。 • 优化日历、站点和资源列表加载,完善失败重试。 • 新增玻璃特效开关,改善主题、多语言、插件搜索和弹窗布局,修复下载器拖拽崩溃。 • 完善 iOS 容器的原生菜单、资源筛选排序、长按搜索订阅和通行密钥验证。 • 修复存储清理确认、115 子项变更漏检、云盘目录导航及 CUE 专辑缓存问题。 • 改善订阅并发、设置保存与重置、评论分页和异步请求稳定性。 • 加强账号切换数据隔离、订阅接口认证和敏感凭据保护。 • 修复 TTG 临时下载链接失效重试,提升插件发布一致性。

👍4

26 Oct 2026, 10:20 UTC≈6,410 views17 reactionsread 10 November 2026

🚀 v3.2.0 更新内容 • 完成 iOS 原生容器协作,支持原生导航、操作菜单、资源筛选排序、长按搜索订阅、通知中心和 Passkey 验证。 • 统一浅色、深色及跟随系统的玻璃主题,优化壁纸、导航阴影和弹层显示。 • 优化插件市场、文件列表、插件历史、订阅批量操作及资源操作交互。 • 提升搜索订阅稳定性,优化站点限流、请求配额、队列恢复和媒体类型冲突处理。 • 增强下载、转移、整理、媒体库缓存及插件安装恢复能力。 • 新增 Runcrate 大模型提供商,强化 Agent 会话隔离、请求恢复、定向消息和流式记录。 • 增强 qBittorrent、HDDolby、GitHub 资源下载等外部服务兼容性,并隐藏敏感凭据。 • 修复调度器协程预算、动漫识别、SQLite 连接失效等问题,升级 Rust 加速组件与依赖审计链路。

❤14👍3

22 Oct 2026, 09:38 UTC≈8,490 views7 reactionsread 10 November 2026

🚀 v3.1.9 更新内容 • 新增 reflink 整理及复制自动回退,在支持的文件系统上减少复制耗时和空间占用。 • 订阅新增首次下载与洗版来源记录,优化全集洗版、整季资源选择和重复资源退避。 • 新增季图片写入剧集根目录、图片兼容别名和 Fanart 4K 背景图开关,优化图片下载复用。 • 完善 115 云盘覆盖、同名文件处理和整理回执恢复,补齐源文件清理人工复核及 AI 接管。 • 修复音乐多碟专辑、发行规格识别和重复提交问题,改善 Emby 媒体年份读取。 • 优化 Agent 交互任务隔离、流式反馈、Telegram 最终消息更新及飞书资源卡片。 • 支持从 secrets 文件读取敏感配置;新增 Cheaper Inference,改进 ChatGPT OAuth 刷新和默认模型配置。 • 修复站点连通性检测、分类透传、等级及分享率显示,完善插件版本历史更新操作和豆瓣评论布局。 • 修复 DoH 的 CNAME…

👍6❤1

19 Oct 2026, 06:31 UTC≈9,210 views13 reactionsread 10 November 2026

🚀 v3.1.8 更新内容 • 优化 Emby、Jellyfin、Plex、Navidrome 按需查询,减少无用的数据获取和解析。 • 修复自动整理音乐时未同步本地封面的问题。 • 修复歌词文件权限,遵循 UMASK 设置,避免媒体服务器无法读取。 • 修复热门订阅年份返回异常。 • 修复 Transmission 空文件列表导致错误选集的问题,未匹配目标集数时保持暂停。 • 改进 Agent 资源管理,完善取消、缓存替换及会话关闭时的资源回收。

👍9❤4

18 Oct 2026, 08:12 UTC≈8,830 views11 reactionsread 10 November 2026

🚀 v3.1.7 更新内容 • 新增豆瓣短评与影评展示,区分作者与正文并补齐“加载更多”翻译;修复豆瓣推荐列表读取异常及评论分页契约告警。 • 优化洗版订阅:新集使用普通订阅规则,已有集数升级使用洗版规则;修复洗版订阅状态筛选不准确的问题。 • 改进搜索稳定性:避免站点持续长时间冷却阻塞整轮搜索,减少英文关键词的片段误匹配。 • 加强文件整理安全:覆盖前先暂存新文件并备份旧文件,完善中断恢复、路径校验与事件重放中的媒体信息保留;修复音乐种子下载分类兜底。 • 优化整理通知聚合:目录监控连续到达的文件按静默窗口合并通知,减少刷屏;改进持久通知恢复,降低异常任务相互影响。 • 修复 Telegram 网络异常后的消息接收恢复和 Agent 流式发送限流,以及微信 access_token 过期或失效后的刷新。 • 改善媒体服务器兼容性:修复媒体库同步误清空本地缓存、Emby 图片缓存刷新、Jellyfin 零时长播放进度及 Ple…

👍10❤1

15 Oct 2026, 23:11 UTC≈7,990 views34 reactionsread 10 November 2026
Video

🏅 MoviePilot 社区荣耀勋章系统上线! MoviePilot 的成长,离不开每一位参与者。写代码、做插件、完善文档、参与测试、解答疑问……这些付出,值得被看见、被铭记。 我们以电影幕后的不同角色为灵感,推出首批 七枚社区勋章,致敬共同建设 MoviePilot 的你: ✍️ 编剧:献给贡献代码与文档的共建者。官方仓库中被采纳的贡献累计达到 1 / 10 / 50 / 200 次,分别获得「初光 / 共建 / 卓越 / 核心」四档荣誉。 🎨 布景:献给丰富 MoviePilot 体验的插件作者。发布首个插件即可获得「初光」,名下插件累计安装达到 1 万 / 10 万 / 100 万次,依次晋升「共建 / 卓越 / 核心」。 🎬 主创:献给持续维护项目的维护者与核心团队。 🏮 掌灯:献给长期在社群中答疑解惑、帮助他人的热心伙伴。 🌙 守夜:献给负责任地报告安全问题,并协助修复的安全贡献者。 🎞 试映:献给参…

❤31👍3

Showing the 12 most recent of 46 posts we hold for @moviepilot_channel. 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

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.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

PT风向旗
@Ptfxq · 17,501
#1
PTPP Actions
@PTPPAction · 3,001
#2
未响 | FutureEcho | 公告
@FutureEcho_Notice · 7,324
#3
MoviePilot Wiki
@MoviePilot_Wiki · 4,988
#4
在花🎗️科技圈
@zaihuapd · 289,745
#5
NodeSeek官方频道
@nodeseekc · 40,449
#6
aimovierobot
@aimovierobot · 4
#7
Themby
@themby_official · 2,672
#8
Odyssey+
@odysseyplus · 24,733
#9
风向旗参考快讯
@xhqcankao · 168,108
#10
PT-Plugin-Plus (Unofficial)
@ptpluginplus · 4,396
#11
折腾啥
@zhetengsha · 53,830
#12
CottonMusic(棉花音乐播放器)
@ppuremusic · 1,490
#13
XP Digital Lab
@rocCHL · 37,274
#14
NAStool Wiki
@NAStool_wiki · 5,656
#15
zrj766的频道
@zrj96 · 17,813
#16
Turnip Project助手
@TurnipProject · 1,542
#17
CloudNAS
@cloud_nas · 11,714
#18
Filebar News
@FileboxOfficial · 8,656
#19
VERTEX
@lswl_vertex · 872
#20
iPlay News
@iPlayNews · 2,767
#21
技术小木屋 channel
@v2rayAgentChannel · 9,697
#22
Yummy 😋
@GodlyNews1 · 71,117
#23
AKILE NOTICE
@akile_notice · 19,019
#24
VPS✨主机补货监控
@vps_track_share · 4,356
#25
Surge TestFlight Feed
@SurgeTestFlightFeed · 13,052
#26
Surge & Loon & QX 脚本收集
@NobyDa · 64,479
#27
xiaoya文档
@xiaoya_doc · 6,267
#28
竹新社
@tnews365 · 167,118
#29
NodeSeek新帖推送
@hostloc2tg · 4,522
#30
生瓜太保工具分享
@guashare · 383
#31
VPS信号旗播报
@vps_xhq · 50,783
#32
二次元emby 开学快乐
@nijigen_emby · 11,011
#33
ᴅɪɢɪᴛᴀʟᴠɪʀᴛ ☁️ 情报站
@DigitalVirtStation · 3,938
#34
特价VPS分享
@Tjjcfx · 17,879
#35
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud · 101,582
#36
Faker | iKun聚集地
@scriptalking · 27,954
#37
蓝点网订阅频道
@landiansub · 47,084
#38
每日消费电子观察
@CE_Observe · 77,552
#39
Yamby Release
@yamby_release · 37,383
#40

Read from Telegram’s recommendation API, most recently 30 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Yamby Release
@yamby_release · 37,383
Telegram ranks this channel #28 of 29 here — alongside 28 others — read 1 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 9 November 2026 — this entry's latest reading, not the date you are reading this.

“MoviePilot频道” (@moviepilot_channel), 19,978 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/moviepilot_channel.

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.