Telegram RegisterThe public register of Telegram

Channel

赶场频道

@ScreenHop

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

17subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003926024269
TypeChannel
Username@ScreenHop
Created29 June 2026measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/ScreenHop

Growth

176 August 2026 — 17 subscribers11 August 2026 — 17 subscribers6 August 202611 August 2026
2 measurements spanning 5 days. 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 16–18 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 19:3117no change
6 Aug 2026, 12:3117first reading

Engagement

8 posts held, back to 29 June 2026the 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 · 30 days
175.0%
avg views ÷ 17 subscribers
Avg views / post
29.8
4 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
4
of 8 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 4 August 2026
Posts held8 (29 June 20264 August 2026)
Views total119
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken11 Aug 2026, 19:31 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
2
Videos
1
Links
1

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

Video runtime
11s
Average length
11s

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

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.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 1 of the 8 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 1reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 29 June 2026 to 4 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

4 Aug 2026, 13:31 UTC15 viewsread 11 August 2026

https://testflight.apple.com/join/4CKbD49Q 主体转移,需要重新添加一下 TF

29 Jul 2026, 15:24 UTC26 viewsread 11 August 2026
Photo

## 1.2.0 (build 5) 新增 - 「我的」页改版:顶部是观影统计概况,点进去有月/年统计详情页,设置移到了二级页。 - 统计详情页支持左右滑动切换月/年,点趋势图也能翻页。 - 把票加进钱包后,走到影院附近锁屏会自动建议这张票。 - 新建自定义日程时可以搜索片库关联影片。 修复 - 添加到钱包的通知问题 - 识别命中片库后,编辑表单里不显示封面 - 点日历卡片旁边的空白想新建日程时,不再误触打开卡片详情。 - 票夹待出票列表跨年时的排序错误。

15 Jul 2026, 15:04 UTC46 viewsread 11 August 2026

## 1.0 (build 17) 新增 - 新建日程时,会顺带列出你选的这段时间里的场次,点一下就能直接加进来 - 日历里两场之间的通勤时间可以点了,一点就拉起两家影院之间的地图路线 - 删日程、删票这类操作现在能撤销,误删也不怕 优化 - 场次详情换场更顺手:直接列出同一部片的其他场次,一点就换 - 遇到时间冲突改选别的场次一步到位,改错了也能撤销 - 提示条改版,更清爽不挡手 - 发现页海报加载更省电、更省内存,滑动更跟手 修复 - 三日视图拖动场次时,原来那天不再留下一个不动的重影

11 Jul 2026, 06:29 UTC83 viewsread 11 August 2026

## 1.0 (build 13) 赶场 · 内测 新增 - AI 电影票识别:拍摄或从相册选择票据后,自动提取信息;无网络或 AI 识别失败时自动回退本地识别。 - 新增拟物出票动画:识别完成后,实体票按淘票票、猫眼、万达、寰映等品牌版式生成票面,从页面顶部“出票”后可分享。 优化 - 扫票流程整合为单页体验:拍摄、识别、匹配场次与加入票夹衔接更顺滑;相机取景框会在检测到票面后给出对准反馈。 - 日程页的视图切换、隐藏座位与新建按钮迁入系统导航栏;再次点击“日程” tab 时,会回到今天或最近的观影安排。

9 Jul 2026, 03:55 UTC74 views1 reactionsread 11 August 2026

build(12) 新增 - 自定义日程:日程页支持新建不关联官方场次的个人安排(标题 / 位置 / 影厅 / 票价 / 座位 / 开始结束时间 / 备注,交互对齐系统日历新建日程);日历视图可直接点击空白时段拖出日程(默认半小时,两端可拖拽调整起止时间)。 - 自定义日程支持长按整体拖动调整时间(含跨日)、拖拽手柄单独调时长、长按呼出快捷菜单一键删除。 优化 - 扫票录入页改为在票夹页内推入打开(不再全屏弹出),支持从屏幕左缘右滑返回,导航体验与系统一致。 - 票卡版式精简:移除「电子票 / 实体票」徽标,展映单元标签单独成行。 - 日历单日视图下,同一时间段的多条日程改为并排显示,不再互相遮挡。 修复 - 新装 App 首次启动若网络请求失败(如联网权限弹窗期间),发现页此前会误显示「排片即将公布」;现在如实提示「排片加载失败」并提供重新加载入口,回到前台也会立即自动重试。

1

Showing the 8 most recent of 8 posts we hold for @ScreenHop. 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 — 1,037,299 of 1,169,250entries 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.

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

“赶场频道” (@ScreenHop), 17 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/ScreenHop.

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.