Telegram RegisterThe public register of Telegram
Telegram profile photo for ReelFlow 通知群

Channel

ReelFlow 通知群

@reelflowNotify

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

1,653subscribers

+0 since we began measuring on 18 November 2026

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

Register entry

Telegram ID-1004309295582
TypeChannel
Username@reelflowNotify
CreatedBetween 1 June 2026 and 31 October 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 November 2026
Last confirmed live18 November 2026
Measurements held2
On Telegramt.me/reelflowNotify

Growth

1,65318 Nov 2026, 18:47 — 1,653 subscribers18 Nov 2026, 19:22 — 1,653 subscribers18 Nov 2026, 18:4718 Nov 2026, 19:22
2 measurements taken within a single day. 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 1,651–1,655 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Nov 2026, 19:221,653no change
18 Nov 2026, 18:471,653first reading

Engagement

13 posts held, back to 11 November 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
60.5%
avg views ÷ 1,653 subscribers
Avg views / post
1,000
13 posts measured
Reaction rate
0.165%
reactions ÷ views · ER floor
Posts in window
13
of 13 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. It is computed over the 9 of 13 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 18 November 2026
Posts held13 (11 November 2026 – 18 November 2026)
Views total13,003
Reactions total14
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 19:22 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
12
Videos
2
Links
6

Lifetime counters from Telegram’s own channel header, read 18 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
1m 14s
Average length
1m 14s

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

14 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1285.7%
👍214.3%

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

Measured over the 13 most recent posts we hold, published 11 November 2026 to 18 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: 1 of 13 posts held from the last 30 days (7.69%) 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).

18 Nov 2026, 15:26 UTC357 views1 reactionsread 18 November 2026
File

# ReelFlow 5.2.0 · 构建 261118 本次更新基于构建 261113,涵盖 iPhone、iPad、Apple TV 和 Mac。 ## 详情与播放 - TMDB 剧集和已匹配 TMDB 的资源站详情可按季浏览分集封面、简介和播出日期。选择一集后,ReelFlow 按季号和集号在当前订阅中查找播放资源,找不到时会提示具体季集。 - 详情页重新布局播放、预告片和资源入口。可在「追剧进度」中按季勾选已看集数,保存时保留其他季的记录。 - 「弹幕外观」新增花式弹幕,可预览样式,调整总比例、图标开关和各样式的出现权重。 - 修复部分位图字幕随每句文字长度改变显示大小的问题,长短字幕的字号更一致。 ## Apple TV - 遥控器焦点轮廓更贴合海报和按钮。调整发现、搜索、设置、资料库和详情页的布局,让上下移动和返回后的焦点更可预测。 - 播放器可用方向键按 10 秒预览进度,按确认跳转、按返回取消。选集、切…

❤1

18 Nov 2026, 14:24 UTC64 views0 reactionsread 18 November 2026
File

安卓版 ReelFlow 正式发布!(1.0.0+261118) 首个版本肯定会有一些 bug,但是希望大家保持友好的语气反馈和交流! TG 交流群:https://t.me/ReelFlowYYDS (反馈和建议都在这里) 和 Sollin 账号互通,并且 Sollin 的顶级用户自动转换 SVIP,高级自动转换 VIP(赞助功能目前只有和云同步相关的)

18 Nov 2026, 14:18 UTC≈1,190 viewsread 18 November 2026
File

安卓版 ReelFlow 正式发布!(1.0.0+261118) 首个版本肯定会有一些 bug,但是希望大家保持友好的语气反馈和交流! TG 交流群:https://t.me/ReelFlowYYDS (反馈和建议都在这里) 和 Sollin 账号互通,并且 Sollin 的顶级用户自动转换 SVIP,高级自动转换 VIP(赞助功能目前只有和云同步相关的)

18 Nov 2026, 10:28 UTC748 viewsread 18 November 2026

https://t.me/ReelFlowYYDS 求求了 tg大哥哥别封我的家人群了,进群的都是家人。°(°¯᷄◠¯᷅°)°。 新聊天群 只招收真正使用ReelFlow的家人朋友们❤️ 现在这个群死人太多了 bot太多了,我不喜欢。 可以踊跃,后面可以按照活跃度发福利嘿嘿嘿嘿🔵🟠🔵🟠

18 Nov 2026, 08:43 UTC802 views1 reactionsread 18 November 2026
Photo

我草莓招了 群被封了 为啥啊??

❤1

14 Nov 2026, 04:51 UTC≈1,190 views3 reactionsread 18 November 2026
File

# ReelFlow 5.2.0 · 构建 261113 播放与字幕 - 音轨和字幕列表增加更清楚的编号、中文语言名称及格式信息,方便区分同一影片中的多个选项。 - 播放时优先选择可用的中文字幕,有中英双语字幕时优先使用;手动切换、关闭或导入字幕后,尊重你的选择,不再被自动选择覆盖。 浏览与导航 - 修复部分系统底部展开菜单点击不灵敏、展开后项目难以选中的问题,改善展开与收起动画。 - 调整底部导航的页面留白,减少列表最后一项被底栏遮挡的情况。 Apple TV - 修复可能导致旧版 tvOS 点击应用后无法显示界面的启动兼容问题,最低系统仍为 tvOS 18。 - 修复本机配置目录不可写导致的源文件保存及备份恢复问题,升级时保留并迁移已有本机配置。 - 发现页切换站源改为专用选择页,打开后自动定位当前站源;焦点更清晰,长列表上下切换更稳定。 - 遥控器返回键优先收起站源选择页,关闭后焦点回到切换按钮。 - 修复“…

👍2❤1

11 Nov 2026, 09:54 UTC≈1,220 views5 reactionsread 18 November 2026
File

ReelFlow 5.2.0 · 261111 支持了py源、html源、emby。 更多影视源 - 新增 Python Spider 源,可添加脚本地址或从文件导入;支持 JSON 订阅中的 Python 爬虫站点。 - 新增 HTML 网页源,在“发现”中浏览;兼容网页可调用 ReelFlow 播放器、搜索与网盘推送。支持网页全屏浏览,退出按钮可长按拖动位置。 - 新增 Emby 服务器,可独立浏览媒体库、搜索和播放,也可参与站源搜索。 - 媒体源支持拖动排序。 账号、备份与同步 - 新增 ReelFlow 账号入口。 - “设置 → 云备份与恢复”支持按类别创建完整备份。 - 新增“实时增量云备份”;支持多端播放进度自动同步。 - 新增 WebDAV 备份与恢复入口:“云备份与恢复 → WebDAV”。 播放、字幕与续播 - 新增 ASSRT 在线字幕搜索,默认无需填写 Token,也可配置个人 Token …

❤5

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

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

“ReelFlow 通知群” (@reelflowNotify), 1,653 subscribers as measured 18 November 2026. Telegram Register, tgregister.com/channel/reelflowNotify.

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.