Telegram RegisterThe public register of Telegram
Telegram profile photo for iBeta 尝鲜派|公告栏

Channel

iBeta 尝鲜派|公告栏

@ibeta_channel

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

13,415subscribers

-17 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001487287740
TypeChannel
Username@ibeta_channel
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/ibeta_channel

Growth

13,41513,43713,4266 August 2026 — 13,432 subscribers6 August 2026 — 13,432 subscribers7 August 2026 — 13,430 subscribers8 August 2026 — 13,437 subscribers9 August 2026 — 13,431 subscribers10 August 2026 — 13,430 subscribers12 August 2026 — 13,425 subscribers13 August 2026 — 13,420 subscribers15 August 2026 — 13,417 subscribers16 August 2026 — 13,415 subscribers6 August 202616 August 2026
10 measurements spanning 10 days, net -17. 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 13,412–13,440 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 20:5513,415-2
15 Aug 2026, 14:5613,417-3
13 Aug 2026, 23:4713,420-5
12 Aug 2026, 16:3413,425-5
10 Aug 2026, 12:2513,430-1
9 Aug 2026, 11:3113,431-6
8 Aug 2026, 13:1413,437+7
7 Aug 2026, 15:1413,430-2
6 Aug 2026, 18:4613,432no change
6 Aug 2026, 09:3413,432first reading

Engagement

15 posts held, back to 7 July 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
27.5%
avg views ÷ 13,415 subscribers
Avg views / post
3,700
11 posts measured
Reaction rate
0.613%
reactions ÷ views · ER floor
Posts in window
11
of 15 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 11 August 2026
Posts held15 (7 July 202611 August 2026)
Views total40,650
Reactions total249
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 11:29 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.

Reaction mix

369 reactions across 15 posts, in 13 distinct kinds. The most used accounts for 39.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤮14539.3%
👎8122.0%
7720.9%
👍154.07%
🤡133.52%
custom 6323236945514202760102.71%
🫡82.17%
💩61.63%
🤣51.36%
🌚30.813%
🥰30.813%
😱20.542%
👌10.271%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it isTelegram’s.

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

Measured over the 15 most recent posts we hold, published 7 July 2026 to 11 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

11 Aug 2026, 03:35 UTC≈2,850 views33 reactionsread 15 August 2026
Photo

#iPadOS27 在iPadOS 27 Beta 5中,电池图标也被改成了iOS的样式,数字字体随iOS更改。 本条消息来自尝鲜派志愿者 @Zinc1um 加入尝鲜派群组:@ibetame

🤮19👍12👎2

11 Aug 2026, 00:39 UTC≈2,970 views20 reactionsread 15 August 2026
Photo

各位早! iOS 27 Beta 5 推送了。 —— 《iOS 27 Beta 5 体验报告》也已出炉。 过了 21 天终于来了。 但感觉就是憋了坨大的... 四个自带 App 图标做了小小变化。 然后万众期待的国行 AI 还没上线。 请接着往下看吧~ 公众号:https://mp.weixin.qq.com/s/G9m_GrCaoBTH2ANEmD5ZSQ 官网查看:https://betahub.cn/post/3861

🤮154👎1

Signed iBETA_Bot

11 Aug 2026, 00:36 UTC≈2,800 views9 reactionsread 15 August 2026
Photo

各位早! iOS 26.6.1 RC 推送了。 —— 《iOS 26.6.1 RC 体验报告》也已出炉。 通常这类小版本都是直接上线的。 但此次更新的 26.6.1 为 RC 版。 需要设置 Developer Beta 才可更新。 不过基本上也没什么变化。 正式版用户建议等后续更新就好了~ 请接着往下看吧。 公众号:https://mp.weixin.qq.com/s/OqdPggLloW453BmbudwbXg 官网查看:https://betahub.cn/post/3862

🤮81

Signed iBETA_Bot

10 Aug 2026, 18:06 UTC≈2,970 views33 reactionsread 15 August 2026

检测到苹果服务器已经推送了以下内容: Xcode 27 beta 5 (27A5237l) iOS 27.0 beta 5 (24A5408d) iPadOS 27.0 beta 5 (24A5408d) macOS 27.0 beta 5 (26A5406e) tvOS 27.0 beta 5 (24J5346a) visionOS 27.0 beta 5 (24M5348b) watchOS 27.0 beta 5 (24R5347a) iOS 26.6.1 (23G82) iPadOS 26.6.1 (23G82) macOS 26.6.2 (25G82) iOS 18.7.10 (22H373) iPadOS 18.7.10 (22H373) 来自:iBeta 尝鲜派 -> https://www.ibeta.me

👎20🤮7💩51

Signed iBETA_Bot

28 Jul 2026, 01:27 UTC≈5,390 views20 reactionsread 15 August 2026
Photo

各位早! iOS 26.6 正式版推送了。 —— 《iOS 26.6 正式版体验报告》也已出炉。 随着 iOS 27 的推出。 iOS 26.6 已经几乎没什么可见变化了。 但依旧推荐大家更新至这个版本。 提早完成 iOS 27 漫长的索引流程。 另外,iOS 26.6 正式版和 RC 构建号相同,如果上周已更新就收不到推送啦。 公众号:https://mp.weixin.qq.com/s/TV-tlcJfPPnomJNeSpoMYQ 官网查看:https://betahub.cn/post/3848

🤮154👍1

Signed iBETA_Bot

27 Jul 2026, 18:40 UTC≈4,360 views27 reactionsread 15 August 2026
Photo

检测到苹果服务器已经推送了以下内容: iOS 26.6 (23G71) iPadOS 26.6 (23G71) macOS 26.6 (25G72) tvOS 26.6 (23L773) visionOS 26.6 (23O770) watchOS 26.6 (23U67) 来自:iBeta 尝鲜派 -> https://www.ibeta.me

👎15🤮64😱2

Signed iBETA_Bot

22 Jul 2026, 03:16 UTC≈4,840 views47 reactionsread 15 August 2026
Photo

各位的 Todoo 更新了! 新的 1.1.9 版本带来了如下更新: 1、开放注册。 2、Markdown 支持。 3、后台处理。 4、全新设计的输入框。 5、新的日程和回忆小组件。 6、适配横屏和响应式设计。 7、适配 iOS 17。 8、优化实时活动设计。 以及上上下下大大小小几十项改进。 久等了,来看看你的用户 ID 是几位数! PS:Todoo 是尝鲜派的兄弟产品,一款 AI 屏幕事项处理软件,Apple 2026 官方孵化器项目,功能介绍:https://mp.weixin.qq.com/s/MiHWEmYY6SZ4UPlKQOirRg

👎22🤮117🤣5👍2

21 Jul 2026, 01:15 UTC≈3,840 views12 reactionsread 15 August 2026
Photo

各位早! iOS 26.6 RC 推送了。 —— 《iOS 26.6 RC 体验报告》也已出炉。 该版本提前开始了聚焦索引「为 Siri AI 准备好」。 请接着往下看吧。 公众号:https://mp.weixin.qq.com/s/J11QExiGgcM7f3CrV5fXZg 官网查看:https://betahub.cn/post/3836

🤮84

Signed iBETA_Bot

21 Jul 2026, 01:10 UTC≈3,810 views13 reactionsread 15 August 2026
Photo

各位早! iOS 27 Beta 4 推送了。 —— 《iOS 27 Beta 4 体验报告》也已出炉。 Beta 4 修复了上个版本的很多问题。 比如汉化、「设置」卡死、快捷粘贴等。 同时也觉得比之前流畅了一点。 总结: 还是值得更新的。 请接着往下看吧~ 公众号:https://mp.weixin.qq.com/s/ia7XfsRWN1ZeYI2HN8v3fA 官网查看:https://betahub.cn/post/3835

🤮76

Signed iBETA_Bot

20 Jul 2026, 20:22 UTC≈3,330 views10 reactionsread 15 August 2026
Photo

检测到苹果服务器已经推送了以下内容: Xcode 27 beta 4 (27A5228h) visionOS 27.0 beta 4 (24M5326g) watchOS 27.0 beta 4 (24R5325h) 来自:iBeta 尝鲜派 -> https://www.ibeta.me

🤮73

Signed iBETA_Bot

20 Jul 2026, 17:34 UTC≈3,490 views25 reactionsread 15 August 2026
Photo

检测到苹果服务器已经推送了以下内容: iOS 27.0 beta 4 (24A5390f) iPadOS 27.0 beta 4 (24A5390f) macOS 27.0 beta 4 (26A5388g) tvOS 27.0 beta 4 (24J5325d) iOS 26.6 RC (23G71) iPadOS 26.6 RC (23G71) macOS 26.6 RC (25G70) tvOS 26.6 RC (23L772) visionOS 26.6 RC (23O770) watchOS 26.6 RC (23U67) 来自:iBeta 尝鲜派 -> https://www.ibeta.me

11🤡11🤮2👎1

Signed iBETA_Bot

15 Jul 2026, 15:32 UTC≈4,190 views57 reactionsread 10 August 2026
Photo

慢讯丨Apple 智能通过网信办备案,千问模型助力苹果 AI 落地中国 根据网信办公众号「网信中国」公布的消息,包括「Apple 智能」在内的 7 款手机端侧生成式人工智能服务,已经完成备案。 以上备案是根据《生成式人工智能服务管理暂行办法》实施的,《办法》规定面向中国境内公众提供生成文本、图片、音频、视频等内容的生成式人工智能服务,需要履行相应的安全与合规义务。 此次完成备案,意味着「Apple 智能」已经跨过进入中国内地市场前的一项重要合规门槛。 不过,完成备案并不等于「Apple 智能」和 Siri AI 会立即上线。苹果后续可能仍需完成具体应用或功能登记,并落实合作主体、模型调用、数据处理和本地化部署等环节。 根据彭博社的 Mark Gurman 报道,苹果可能会单独在服务器端为国行用户开启「Apple 智能」而无需额外系统更新,就像早些时候发生过的一次意外一样。 另外,据阿里巴巴方面透露,千问大模型将作为

26👎18🤮10🤡2👌1

Signed iBETA_Bot

Showing the 12 most recent of 15 posts we hold for @ibeta_channel. 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 — 279,560 of 1,481,243entries 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 2 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 16 August 2026 — this entry's latest reading, not the date you are reading this.

“iBeta 尝鲜派|公告栏” (@ibeta_channel), 13,415 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/ibeta_channel.

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.