Channel
@NookReelUpdates
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
621subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003380868675 |
|---|---|
| Type | Channel |
| Username | @NookReelUpdates |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/NookReelUpdates |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 17:37 | 621 | +2 |
| 8 Aug 2026, 03:02 | 619 | no change |
| 7 Aug 2026, 21:03 | 619 | first reading |
20 posts held, back to 20 May 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 pageof Telegram’s post history, 20 posts per page.
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 1 of 3 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 July 2026 |
|---|---|
| Posts held | 20 (20 May 2026 – 28 July 2026) |
| Views total | 1,176 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 03:02 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.
10 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 60.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6 | 60.0% | |
| ❤ | 3 | 30.0% | |
| 👎 | 1 | 10.0% |
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 7 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 10reactions 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 20 May 2026 to 28 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.
📢 NookReel 用户 Bot 公测通知 为了提升大家的使用体验，NookReel 用户 Bot 现已开启公测。 🤖 Bot：@NookReelBot 目前已开放部分用户功能，后续将持续完善并增加更多便捷功能。 ⚠️ 公测期间说明 由于目前处于测试阶段，部分功能可能存在异常或不完善的情况。 如遇到： • 功能异常 • 操作问题 • 使用建议 • 新功能需求 欢迎回复本公告话题反馈，或联系管理：📩 @NookReelRelayBot 大家的反馈将帮助我们持续优化 Bot 功能。
📢 暂停注册公告 因平台近期需要进行用户管理及系统调整，NookReel 即日起暂停新用户注册及开号申请。 暂停期间： • 暂不受理新用户开号 • 已注册用户不受影响，可正常使用 • 现有账号管理、播放及求片等功能保持正常 恢复注册时间将根据实际情况另行通知，请以官方频道公告为准。
❤1
📢 NookReel × Forward 入库通知功能上线 为了方便大家及时获取资源更新动态，NookReel 已接入 Forward 入库通知服务。 绑定后，当您关注的影视资源完成入库并满足推送条件时，Forward 将及时发送通知提醒。 🔔 绑定方式 进入： 设置 → 追剧日历 → 入库通知 → 绑定口令 输入： NookReel 即可完成绑定。 也可以直接打开以下链接： forward://bindpush?code=NookReel 自动填入绑定信息。 ⚠️ 温馨提示 • 入库通知会根据资源匹配情况进行推送，并非所有入库资源都会重复通知。 • 系统会自动处理重复事件，避免频繁推送。 • 该功能仅用于资源更新提醒，不涉及账号、Cookie 等敏感信息。 后续我们也会继续完善更多通知功能，让大家更方便地获取 NookReel 最新动态。 📚 资源入库更新：@NookReelLibrary 💬 交流与反馈…
📢 NookReel 使用规范 为保障平台稳定运行及所有用户的正常使用，请遵守以下规则： ❌ 禁止将资源库作为数据中转、批量转存、离线搬运、采集等用途。 ❌ 禁止长期大量转存、不播放、异常访问、高频请求等非正常使用行为。 ❌ 禁止使用异常、失效或非 VIP 的 115 Cookie（CK）。 ⚠️ 平台设有完善的风控机制，将结合账号行为进行综合判断。对于存在异常使用、恶意占用资源、影响平台正常运行等行为的账号，将视情况限制使用或直接清理。 🚫 因违反使用规范或触发平台风控而被清理的账号，不予二次开号。 NookReel 为纯公益服务，希望大家合理使用资源，共同维护良好的使用环境。
👍3
📢 求片功能说明 为了方便大家快速获取所需资源，NookReel 已开放 求片功能。 📌 求片规则 ✅ 每位用户每日可提交 10 次求片。 提交路径： 用户中心 → 资源搜索 → 求片 ⚡️ 资源入库流程 提交求片后，系统将优先通过自动资源源进行匹配入库。 一般情况下，约 10 分钟内即可完成入库（具体时间以实际情况为准）。 若 10 分钟后仍未入库，则表示自动资源源暂未匹配成功，我们会通过 PT 资源站点进行人工检索、下载并补充入库。 📚 人工入库说明 • 若 PT 资源站点存在资源，一般将在当天内完成入库。 • 若提交后 3 天内仍未入库，通常表示目前暂无可获取资源或暂未找到符合要求的资源。 📢 所有入库资源均会同步发布至： @NookReelLibrary 欢迎关注频道，第一时间获取最新入库通知。
📢 Cookie 更新提醒 为保证资源合理利用及系统稳定运行，系统将于每周日 23:00（北京时间）定期清理 115 Cookie 已失效、异常或未绑定 的账号。 以下账号请及时更新 115 Cookie，否则将在本周清理时移除账号： Bes****** Jas*** Jason*** son*** fan*** luo*** rzx*** Gou*** boo*** 735*** kb cup*** mil*** xuj*** vru*** Ekk zzz*** sun*** lsb*** voo ⚠️ 如已完成更新，请忽略本次提醒。 💡 后续计划 目前 Cookie 状态需要用户自行关注。 后续 NookReel Bot 开发完成后，将支持账号状态检测，并在 Cookie 即将失效、已失效或未绑定 时，主动推送 Telegram 通知，提醒用户及时更新，避免因未及时处理而影响正常使用或被系统定期清理。 📩 如…
📢 【维护完成通知】 NookReel 已完成本次系统维护，所有服务现已恢复正常运行。 本次维护主要进行了系统优化、功能升级及稳定性调整，目前： ✅ 网站已恢复访问 ✅ 播放功能已恢复正常 ✅ 115 绑定功能已恢复 ✅ 求片及相关功能已恢复 如果您在使用过程中仍遇到异常情况（如播放异常、页面报错等），欢迎及时反馈，我们会第一时间协助处理。| 💬 交流与反馈：@NookReelLounge 📩 联系管理：@NookReelRelayBot 感谢大家在维护期间的耐心等待与理解，祝大家观影愉快！🍿
📢 【停服维护通知】 为优化系统稳定性、升级部分功能并进行例行维护，NookReel 将于今晚进行停服维护。 🕛 维护时间 2026 年 7 月 10 日 23:59（北京时间） ⏳ 预计维护时长 约 2 小时（将根据实际情况提前或顺延） 🔧 维护期间影响 • 网站将暂时无法访问 • 播放、绑定、求片等相关功能将暂停服务 请大家提前做好安排，避免在维护期间进行相关操作。 维护完成后，我们将第一时间发布恢复公告。 由此给大家带来的不便，敬请谅解。 感谢大家一直以来对 NookReel 的支持与理解！
❤1
115 Cookie（CK）绑定，你更希望采用哪种方式？
The shares total 110%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
📢 功能调研｜115 Cookie（CK）绑定方式征集 为了进一步提升使用体验，我们正在规划 NookReel Telegram Bot，后续将逐步对接网站常用功能，例如： ✅ 开号申请 ✅ 账号信息查询 ✅ 求片提交与查询 ✅ 系统通知推送 ✅ 更多便捷功能... 目前有一个功能，希望听听大家的意见： 115 Cookie（CK）绑定，是否需要集成到 Bot？ 目前考虑以下几种方案： ① Bot 生成二维码授权绑定 由 Bot 生成二维码，用户扫码完成绑定。 优点： • 无需手动复制、发送 Cookie • 操作更加直观、安全 • 更符合多数用户的使用习惯 ② Bot 直接接收 Cookie（CK）绑定 用户将 Cookie 发送给 Bot，由 Bot 自动完成绑定。 优点： • 操作简单 需要注意： Cookie（CK）属于账号的重要授权凭证。 虽然 Bot 可以做到自动处理，但 Cookie 需…
🗑️ 账号清理说明 为保证资源合理利用及系统稳定运行，系统将于每周日定期清理以下账户： • 未绑定 115 Cookie（CK）的账号 • 115 Cookie（CK）已失效或异常的账号 如因误判或其他原因被清理，可联系管理重新申请开号。
📢 温馨提示｜关于 302 服务使用建议 近期我们注意到，社区内不少用户同时使用或绑定多个 302 服务，因此在此统一提醒。 302 服务在 Cookie（CK）验证、日常校验、资源播放等过程中，均需要由后台服务器与 115 官方进行通信，因此服务器 IP 会被 115 记录。 ⚠️ 建议尽量不要将同一个 115 账号频繁绑定、切换多个 302 服务。 根据近期社区反馈，115 的风控策略可能正在持续调整，账号异常案例也较以往有所增加。虽然官方并未公开具体风控规则，但频繁在不同平台、不同服务器 IP 之间切换，可能会增加账号异常风险，具体以 115 官方实际策略为准。 如果已经选择了适合自己的 302 服务，建议长期、稳定使用，而不是频繁在多个平台之间切换或 " 集邮 " 多个平台。 NookReel 尊重每位用户的自由选择，也不会限制大家使用其他平台。本公告仅从账号安全角度提供使用建议，希望帮助大家降低潜在风险。不…
Showing the 12 most recent of 20 posts we hold for @NookReelUpdates. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
115 Cookie（CK）绑定，你更希望采用哪种方式？
The shares total 110%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 20 May 2026 to 28 July 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 1,173,887 of 1,340,412entries 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“NookReel Updates｜星幕公告” (@NookReelUpdates), 621 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/NookReelUpdates.
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.