Telegram RegisterThe public register of Telegram

Channel

SCENE Downloads

@scene2023

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

53,240subscribers

+276 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001650513563
TypeChannel
Username@scene2023
DescriptionThe official update channel of SCENE
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/scene2023

Growth

52,96453,24053,1026 August 2026 — 52,964 subscribers6 August 2026 — 52,979 subscribers7 August 2026 — 53,023 subscribers8 August 2026 — 53,068 subscribers9 August 2026 — 53,088 subscribers10 August 2026 — 53,133 subscribers11 August 2026 — 53,172 subscribers12 August 2026 — 53,205 subscribers13 August 2026 — 53,240 subscribers6 August 202613 August 2026
9 measurements spanning 7 days, net +276. 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 52,923–53,281 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 16:3853,240+35
12 Aug 2026, 18:3353,205+33
11 Aug 2026, 16:3153,172+39
10 Aug 2026, 16:3153,133+45
9 Aug 2026, 19:5253,088+20
8 Aug 2026, 20:3353,068+45
7 Aug 2026, 19:1053,023+44
6 Aug 2026, 18:1552,979+15
6 Aug 2026, 09:1852,964first reading

Engagement

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

ERR · 30 days
41.7%
avg views ÷ 53,240 subscribers
Avg views / post
22,200
12 posts measured
Reaction rate
0.377%
reactions ÷ views · ER floor
Posts in window
12
of 23 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 9 August 2026
Posts held23 (22 May 20269 August 2026)
Views total266,580
Reactions total1,005
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 11:36 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

Links
2

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

Reaction mix

2,234 reactions across 23 posts, in 27 distinct kinds. The most used accounts for 27.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
61927.7%
👍61027.3%
💩1898.46%
🔥1607.16%
🥰1135.06%
🤔1054.70%
😱1044.66%
👀602.69%
🤓421.88%
👏291.30%
😁261.16%
😍220.985%
🤯220.985%
🤬200.895%
👎190.85%
🗿190.85%
🤮180.806%
🍌170.761%
💋100.448%
🌚60.269%
7 further kinds241.07%

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

Measured over the 23 most recent posts we hold, published 22 May 2026 to 9 August 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

9 Aug 2026, 16:55 UTC≈9,800 views39 reactionsread 14 August 2026
File

File, posted without a caption

23🤬8👍5😁3

9 Aug 2026, 16:55 UTC≈9,900 views104 reactionsread 14 August 2026
File

File, posted without a caption

👍7811🥰9🤬3😁3

9 Aug 2026, 16:55 UTC≈9,380 views48 reactionsread 14 August 2026

** 更新后请重启手机! # 9.4.11 (26.08.09) -新增 调节 - 我的游戏 - Remote Play入口 -修复 自定义目标帧率档位后,FAS档位匹配错误 -其它 清理了一些废弃的功能代码

37👍4🥰4😁2🤬1

3 Aug 2026, 12:39 UTC≈19,000 views56 reactionsread 14 August 2026
File

File, posted without a caption

👍29😱119🤡4🏆2😁1

3 Aug 2026, 12:39 UTC≈18,800 views203 reactionsread 14 August 2026
File

File, posted without a caption

👍145😱2316💩11🔥4🥰2😁2

3 Aug 2026, 12:39 UTC≈17,900 views71 reactionsread 14 August 2026

** 更新后请重启手机! # 9.4.9 (26.08.03) -增加 文件浏览、有限人传人界面英文翻译 -其它 细微修复 # 9.4.8 Alpha (26.08.01) -优化 调节 - 我的游戏 - 有限人传人 * 提升大量小文件的应用传输速度 * 提升Direct模式发现和连接热点的速度 * 修复有时状态显示停止更新 -修复 文件浏览访问包含上万个小文件的目录时速度很慢且崩溃 -新增 SceneFAS支持为单个应用设置匹配的目标帧率档位 -其它 无关紧要的优化项 # 9.4.7 Alpha (26.07.27) -优化 应用管理备份APK时,自动将有分包的应用压缩成apks -修复 文件浏览按大小排序时,前进后退路径可能不显示文件 -新增 调节 - 我的游戏 - 有限人传人 * 支持LAN和Direct双模传输,默认Direct模式。 1. LAN模式,同一局域网下的设备间传输数据,靠近路由

46🤯10😁6🍾3👍3🤔1🤬1🥰1

19 Jul 2026, 08:40 UTC≈30,100 views66 reactionsread 14 August 2026
File

File, posted without a caption

👍44😍85💩4💋3😁2

19 Jul 2026, 08:40 UTC≈29,900 views148 reactionsread 14 August 2026
File

File, posted without a caption

111👍15😍10🤮6🥰4😁2

19 Jul 2026, 08:40 UTC≈28,900 views54 reactionsread 14 August 2026

** 更新后请重启手机! # 9.3.12 -新增 帧率记录图标,增加横向滑动悬停显示Tooltip -新增 进程统计悬浮窗,长按进程打开线程监视器 -调整 调整Scene FAS因卡顿退出后的频率限制 -新增 在天玑9500上测试CpuQoS标注CT线程改变L3使用优先级

🔥357👍4😍4🥰3😁1

16 Jul 2026, 14:38 UTC≈32,500 views42 reactionsread 14 August 2026
File

File, posted without a caption

👍2511💋5😁1

16 Jul 2026, 14:38 UTC≈30,400 views116 reactionsread 14 August 2026
File

File, posted without a caption

👍1027🌚6😁1

16 Jul 2026, 14:38 UTC≈30,000 views58 reactionsread 14 August 2026

** 更新后请重启手机! # 9.3.11 -优化 优化帧率记录选择对比目标的操作体验 -修复 Scene FAS 天玑9400,9500中核频率偏移下限不生效 -修复 Scene FAS在出现帧率大幅波动主动退出后,设定的频率上限过低导致持续卡顿 -优化 备份性能调节配置,确保在服务器宕机期间也能正常切换HP、LP、EP -微调 Scene FAS 8GEN5小核频率上限提高100MHz -调整 Scene FAS 频率趋势统计区间延长 # 9.3.10 -调整 SceneFAS参数微调,稍微提高升频积极性 -调整 自动帧率微调改为默认关闭 # 9.3.9 -新增 Scene FAS帧率微调增加Auto档 -调整 Scene FAS策略调整,效果未知 -修复 开启数据共享后,帧率记录超过1小时无法停止 -新增 确保已经获得永久授权的设备,在服务器离线时依然可以正常使用 # 9.3.8 -修复 开启数据共享后,帧率记录超

49👍5🤩3😁1

Showing the 12 most recent of 23 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.

Citation-graph rank

Citation-graph rank — 483,372 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.

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

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

“SCENE Downloads” (@scene2023), 53,240 subscribers as measured 13 August 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.