Telegram RegisterThe public register of Telegram

Channel

CapyPlayer - 通知

@capyplayer_msg

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

6,931subscribers

+68 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1003699537053
TypeChannel
Username@capyplayer_msg
CreatedBetween 1 January 2026 and 12 February 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/capyplayer_msg

Growth

6,8636,9316,8978 August 2026 — 6,863 subscribers9 August 2026 — 6,875 subscribers12 August 2026 — 6,931 subscribers8 August 202612 August 2026
3 measurements spanning 4 days, net +68. 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 6,853–6,941 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 08:236,931+56
9 Aug 2026, 00:546,875+12
8 Aug 2026, 02:186,863first reading

Engagement

20 posts held, back to 12 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
62.6%
avg views ÷ 6,931 subscribers
Avg views / post
4,340
1 post measured
Reaction rate
0.3%
reactions ÷ views · ER floor
Posts in window
1
of 20 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 20 July 2026
Posts held20 (12 February 202620 July 2026)
Views total4,340
Reactions total13
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 02:41 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.

Reaction mix

183 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 48.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍8848.1%
8345.4%
💩84.37%
🎉21.09%
🔥10.546%
🤓10.546%

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 20 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 183reactions 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 12 February 2026 to 20 July 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

20 Jul 2026, 08:49 UTC≈4,340 views13 reactionsread 12 August 2026
File

#CapyPlayer #移动端 安卓版本1.1.3(113122)更新。 1. MPV支持播放Profile 7 FEL(双层杜比视界) 2. 媒体库卡片无图片优化展示 3. 弹幕匹配优化 4. 播放内核支持系统代理 5. 支持MP订阅 6. 详情页面增加分类 7. 详情页面增加剧照 8. EXO SUBRIP字幕多行重叠问题修复 9. EXO ASS字幕相关优化 10. 播放设置增加播放时间数字滚动、长按倍速横滑调节控制选项 11. APP图标大小优化 12. 媒体库没有海报图片问题优化 13. Plex外挂字幕问题优化 14. 搜索页支持搜索历史 15. 搜索配置持久化 16. 背景模糊性能优化 17. TMDB数据订阅问题修复 18. 详情页面集选中边框颜色优化 19. 详情页面性能优化 20. 首页性能优化 21. 预加载增加触发时机配置 22. PRO订阅标记 23. 预加载优化 24. MDK支持磁盘缓存 25

👍76

7 Jul 2026, 12:34 UTC≈5,360 views5 reactionsread 12 August 2026
File

#CapyPlayer #移动端 安卓版本1.1.2(11208)更新。 1. 详情 - 继续播放偶发跳转不准确问题优化 2. 详情 - 选集面板增加自动避让边缘 3. 设置 - 增加图标更换功能 4. 播放 - 退出播放的后台刷新服务优化 5. 聚合 - 切换资源卡片Best问题修复 6. 聚合 - 改为按照码率排序显示 7. 播放 - 剧集数据丢失问题优化 8. 播放 - 在线字幕导致跳转下一集问题修复 9. 播放 - 片头数据无法清除问题修复 10. 合集 - 数据展示优化 11. 多个列表页面性能优化 12. 卡片性能优化 13. 追更 - 增加日历功能 14. 追更 - UI优化 15. 资源 - 增加媒体库统计Sheet 16. 播放 - 点击按钮弹出面板掉帧问题优化 17. 播放 - 更换视频版本后字幕轨道信息没有刷新问题修复 18. 收藏 - 数据加载优化 19. 一些Bug修复 有问题请评论反馈,我们会及

5

30 Jun 2026, 15:09 UTC≈6,110 views26 reactionsread 12 August 2026
File

#CapyPlayer #移动端 安卓版本1.1.1更新。 1. 搜索 - 增加TMDB搜索功能 2. 搜索 - 增加组件搜索功能 3. 搜索页 -搜索栏UI优化 4. 播放页 - 点击面板导致弹幕掉帧优化 5. 播放页 - 进度条优化 6. 播放页 - 弹幕热力图条优化 7. 播放页 - Exo ass字幕问题优化 8. 播放页 - ISO文件没有结束时间问题优化 9. 播放页 - MPV特殊网络无法播放视频问题优化 10. 播放页 - 视频选择展示UI优化 11. 收藏页- 支持滑动加载更多数据 12. 组件编辑页 - 媒体库列表Widget支持拖拽自定义库顺序 13. 列表页 - 排序优化 14. 详情页 - TMDB数据进度上报失败问题修复 15. 详情页 - 切换线路不生效问题修复 16. 备份恢复 - 优化恢复后资源的Token刷新逻辑 17. 备份恢复 - 弹幕大小跟随设备大小优化 18. 资源页 - 添加资源

👍16💩64

27 Jun 2026, 03:11 UTC≈7,900 views13 reactionsread 12 August 2026
File

#CapyPlayer #桌面端 1. 原生实现Win端播放页面 2. 修复多个问题与优化稳定性 有问题请评论反馈,我们会及时跟进处理。

👍103

15 Jun 2026, 14:30 UTC≈7,950 views3 reactionsread 12 August 2026
File

#CapyPlayer #移动端 安卓版本1.1.0更新。 1. 若干问题优化 2. 若干bug修复 有问题请评论反馈,我们会及时跟进处理。

3

29 May 2026, 16:08 UTC≈9,530 views2 reactionsread 12 August 2026
File

#CapyPlayer #安卓端 安卓版本1.0.99更新。 1. 安卓播放功能使用原生实现 2. 若干bug修复 有问题请评论反馈,我们会及时跟进处理。

2

2 May 2026, 16:11 UTC≈11,900 views6 reactionsread 12 August 2026
File

#CapyPlayer 版本 1.0.78更新。 1. 媒体库排序支持单独设置 2. 详情 - Trakt追剧显示优化 3. 首页 - 媒体卡片性能优化 4. 首页 - 数据加载优化 5. 弹幕 - 御版的弹幕 6. 播放 - exo请求问题修复 7. 播放 - 外挂字幕优化 8. 播放 - 跳过片尾一次跳过多集问题修复 9. 播放 - MDK版本升级适配 10. 订阅 - 优化同步逻辑 11. 在看 - 支持按服务器分组 12. 组件 - 引擎数据加载优化 13. 一些小Bug修复与功能优化 14. 修复图片加载问题 官网:https://capyplayer.feifeiduck.com 、https://capyplayer.feifeiduck.cn 有问题请在更新通知下评论反馈~ 再次感谢各位的支持与反馈,我将持续优化,为大家带来更好的体验

6

29 Apr 2026, 10:32 UTC≈9,310 views5 reactionsread 12 August 2026
File

#CapyPlayer 桌面端更新 1. 新增窗口最大化/还原功能 2. 新增窗口支持单击/双击/拖拽 3. 优化播放窗口问题 4. 优化播放亮度问题 5. 优化播放键盘适配 6. 优化首页上下滑动问题 7. 优化一些设备名称为中文导致的网络请求问题 8. 优化窗口背景透明问题 9. 优化桌面端自动代理问题 10. 桌面端支持隐藏/展示资源 11. 横向列表添加左右快速切换图标按钮 12. 优化桌面端卡片大小 13. Windows 播放设置扩展(新增 D3D11VA、DXVA2 视频渲染选项) ,Win推荐解码器设置为D3D11VA 移动端也会在这几天内更新~ 有问题请在更新通知下反馈,欢迎理性交流与建议,我们会及时跟进处理。 感谢大家的支持,我会持续优化产品体验。

5

28 Apr 2026, 12:32 UTC≈6,850 views33 reactionsread 12 August 2026
File

#CapyPlayer CapyPlayer桌面端来了! Windows测试版本更新。macOS TF审核中~ 有问题请在更新通知下评论反馈~ 再次感谢各位的支持与反馈,我将持续优化,为大家带来更好的体验

👍285

22 Apr 2026, 11:18 UTC≈7,350 views4 reactionsread 12 August 2026
File

#CapyPlayer 版本 1.0.6更新。 1. 资源 - 资源卡片增加呼吸状态标识 2. 资源 - 状态检测失败资源跳过后续请求 3. 详情 - 一些媒体服的继续播放不能正确跳转剧集问题修复 4. 详情 - 资源聚合 - 对服务器返回的数据进行验证 5. 详情 - 组件聚合 - 合并单个组件的搜索结果 6. 详情 - 切换线路后缓存数据未被清除问题修复 7. 组件 - 组件列表支持滑动删除 8. 首页 - 支持每次进入/后台返回 - 自动刷新数据 9. 在看 - 支持每次进入/后台返回 - 自动刷新数据 10. 首页 - 卡片评分展示位置优化 11. 播放 - EXO - 优化视频解码逻辑 12. 播放 - MPV - 缓冲问题修复 13. 播放 - 未开始播放显示自动跳过问题修复 14. 播放 - 自动跳过片头 - Plex适配 15. 在看 - 收藏支持分页获取 16. 首页 - 去除自定义页面上限 17. 媒体列

4

15 Apr 2026, 09:34 UTC≈6,250 views4 reactionsread 12 August 2026
File

#CapyPlayer 版本 1.0.5安卓测试版更新。 1. 官网渠道启用应用内更新 2. 纯色背景UI效果优化 3. 播放 - Emby服务器跳过片头功能优化 4. 播放 - 弹幕优化 5. 播放 - Exo自动开启软解播放 6. 播放 - MPV最大缓冲时间扩大到1200s 7. 播放 - 字幕调整修改后立即生效 8. 播放 - 支持STRM直链 9. 详情 - 支持季图标 10. 列表页面 - 支持横向卡片展示 11. 首页 - 资源页面支持自定义 12. 首页 - 性能优化 13. 登录 - IPad验证码输入问题修复 14. 设置 - 增加Impeller渲染引擎选项 15. 设置 - 备份优化 16. 设置 - 组件优化 17. 设置 - 删除提示优化 18. 其他 - 启动页面自动适配颜色模式 19. 一些BUG修复 官网:https://capyplayer.feifeiduck.com 、https:/

4

Showing the 12 most recent of 20 posts we hold for @capyplayer_msg. 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 — 581,003 of 1,160,990entries 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.

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 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.

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

“CapyPlayer - 通知” (@capyplayer_msg), 6,931 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/capyplayer_msg.

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.