File, posted without a caption
👍47🤬16❤5🥰1

Channel
@scene2023
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
57,651subscribers
+4,687 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001650513563 |
|---|---|
| Type | Channel |
| Username | @scene2023 |
| Description | The official update channel of SCENE |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/scene2023 |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 17 August 2026 and assigned it the closest of 31 fixed categories, at 37% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 02:59 | 57,651 | +82 |
| 10 Nov 2026, 19:11 | 57,569 | +58 |
| 9 Nov 2026, 08:10 | 57,511 | +77 |
| 7 Nov 2026, 23:07 | 57,434 | +69 |
| 6 Nov 2026, 19:19 | 57,365 | +86 |
| 5 Nov 2026, 19:21 | 57,279 | +45 |
| 4 Nov 2026, 22:07 | 57,234 | +36 |
| 3 Nov 2026, 21:17 | 57,198 | +26 |
| 2 Nov 2026, 20:08 | 57,172 | +46 |
| 1 Nov 2026, 18:19 | 57,126 | +69 |
| 31 Oct 2026, 19:58 | 57,057 | +62 |
| 30 Oct 2026, 20:27 | 56,995 | +41 |
| 29 Oct 2026, 22:05 | 56,954 | +58 |
| 28 Oct 2026, 19:19 | 56,896 | +32 |
| 27 Oct 2026, 19:09 | 56,864 | +19 |
| 26 Oct 2026, 15:36 | 56,845 | +46 |
| 25 Oct 2026, 13:19 | 56,799 | +52 |
| 24 Oct 2026, 12:37 | 56,747 | +34 |
| 23 Oct 2026, 11:41 | 56,713 | +34 |
| 22 Oct 2026, 08:31 | 56,679 | first reading |
35 posts held, back to 22 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 199 pages of 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.
| Window | Rolling 30 days · latest post in window 8 November 2026 |
|---|---|
| Posts held | 35 (22 May 2026 – 8 November 2026) |
| Views total | 83,300 |
| Reactions total | 455 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 11:17 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.
Lifetime counters from Telegram’s own channel header, read 13 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.
3,772 reactions across 35 posts, in 31 distinct kinds. The most used accounts for 39.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 1,494 | 39.6% | |
| ❤ | 995 | 26.4% | |
| 💩 | 207 | 5.49% | |
| 🥰 | 167 | 4.43% | |
| 🔥 | 160 | 4.24% | |
| 😱 | 122 | 3.23% | |
| 🤔 | 110 | 2.92% | |
| 🤬 | 75 | 1.99% | |
| 👀 | 60 | 1.59% | |
| 🤓 | 54 | 1.43% | |
| 😁 | 50 | 1.33% | |
| 👎 | 43 | 1.14% | |
| 👏 | 29 | 0.769% | |
| 🤡 | 25 | 0.663% | |
| 😍 | 22 | 0.583% | |
| 🤯 | 22 | 0.583% | |
| 🗿 | 19 | 0.504% | |
| 🍌 | 18 | 0.477% | |
| 🤮 | 18 | 0.477% | |
| 👾 | 16 | 0.424% | |
| 11 further kinds | 66 | 1.75% |
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 35 of the 35 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 3,772 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 35 most recent posts we hold, published 22 May 2026 to 8 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.
Telegram’s own ‘edited’ marker: 1 of 6 posts held from the last 30 days (16.7%) 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).
File, posted without a caption
👍47🤬16❤5🥰1
File, posted without a caption
👍81🤬12🆒5❤3🥰1
** 更新后请重启手机! # N1 26.10 Beta14 -调整 环境配置-Install Boost 调整为默认开启 -优化 环境配置-Install Boost 延迟编译优化时跳过不常用应用 -修复 FAS全局设置的帧率偏移未在当个游戏配置时体现 -修复 部分文件使用编辑器插件打开时因权限校验问题报错 -优化 游戏快传升级到v2.3 支持一次性传多个应用/游戏 优化清单生成/处理阶段内存占用 -优化 改进文件浏览部分使用体验细节 -优化 屏幕检测增加刷新率测试甲壳虫 -其它 RemotePlay插件更新 支持通过shizuku激活主机服务 优化Windows端连接键盘中文输入体验,增加复制、剪切、粘贴键盘指令 -新增 性能调节框架内置一些8e/8ee6的适配参数 # N1 26.10 Beta13 -优化 刷新率管理-兼容模式 参数写入耗时大幅降低到3ms -优化 刷新…
👍40❤9🥰3
File, posted without a caption
👍44🤡17❤12🥰4
File, posted without a caption
👍81❤11🥰9
** 更新后请重启手机! # N1 26.10 Beta11 -优化 SceneFAS针对vivo机型禁用缓冲区检查,避免因缓冲区暂存帧数过多忽略卡顿 -调整 SceneFAS精简设置项 -优化 导航键模式下界面显示兼容 # N1 26.10 Beta10 -新增 刷新率管理增加屏幕超频特调,支持设置原厂刷新率上限和逐档升降低 * 注意 Scene本身不提供屏幕超频功能,超频需要自行想办法 -优化 常驻通知快捷控制面板弹出体验 # N1 26.10 Beta9 -优化 常驻通知弹出逻辑,避免广播导致点击无响应 -优化 重构常驻通知控制面板,提供更多快捷选项 -优化 监视器悬浮窗显示位置和部分系统(插帧、超分)功能冲突 # N1 26.10 Beta8 -优化 LP CoreCtl控制提高延迟,避免过于积极的启停核心 -修复 刷新管理管理闲置状态切换时机错误 -优化 下拉通知快捷面板 刷新率档位改为滑块组件,支…
👍32❤18🥰4
File, posted without a caption
👍85❤31💩15😱13🖕10🤬9👾6😁5
File, posted without a caption
👍175❤30🐳15🥰12👾5🤬4💩1
** 更新后请重启手机! # N1 26.09 Alpha7 -修复 daemon窗口监测默认设置下未正常工作 -调整 同时开启daemon层窗口检测和无障碍服务时,不自动禁用,只弹出提示 -修复 未设置屏幕旋转也创建了旋转控制悬浮窗 # N1 26.09 Alpha6 -优化 轻装上阵更畅快,迄今为止体积最小的版本 -重构 性能调节框架-CPU频率控制进一步完善 增加Fast Share功能传输过程CPU Boost 增加文件浏览功能ZIP压缩解压、复制文件等操作的CPU Boost 增加增强LMKE主动压缩、回写过程CPU Boost、KSwapd0 Boost 再次重构GestureBoost激活和退出逻辑 修复辅助调速器设定的频率应用错误 修复Scene FAS中核频率偏移失效 -调整 配置文件统一为小写 -修复 Scene FAS中核频率偏移功能失效 -优化 降低daemon调用系统服务获取…
👍53❤46🥰5🤬2
File, posted without a caption
❤32👍22😁4😱4👎3
File, posted without a caption
👍135❤33🤓12👎10🥰6👾5🤔5😁4
** 更新后请重启手机! # 9.4.16/9.4.17Alpha (26.08.21) -修复 通过GUI设置的中核频率偏移值错误 -优化 FAS目标档位隐藏超过屏幕刷新率的档位 -优化 部分界面资源文字翻译 -新增 文件浏览 - 支持安装apks文件 -修复 8E/8E5等处理器关闭Cluster后启动Scene闪退 -修复 充电统计历史记录里,充电越充越少也显示为正数 -修复 附加模块文件浏览,点击软链时未正确跳转 -修复 附加模块中一个示例错误 # 9.4.15Alpha (26.08.16) -修复 帧率记录在前两版更新后数值后出现的问题 -优化 增加天玑9400,9500 Pad版识别 -调整 文件浏览不再计算0/1/2级目录空间占用 -修复 文件浏览文件名排序错误 -新增 ADB模式 帧率记录显示CPU温度 -新增 使用壁纸主题时,可以自行选择前景/背景模糊 # 9.4.14 Alpha(26.08.15) …
❤51👍40👎4🥰3😁3
Showing the 12 most recent of 35 posts we hold for @scene2023. 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.
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.
Named by 3 registered channels — 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.
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.
Read from Telegram’s recommendation API, most recently 12 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.
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.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“SCENE Downloads” (@scene2023), 57,651 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/scene2023.
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.