Telegram RegisterThe public register of Telegram
Telegram profile photo for 柒柒的鱼骨头

Channel

柒柒的鱼骨头

@Sandrone0721

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

1,082subscribers

+1 since we began measuring on 17 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001998010275
TypeChannel
Username@Sandrone0721
CreatedBetween 1 November 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 August 2026
Last confirmed live21 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/Sandrone0721

Growth

1,0801,0821,08117 August 2026 — 1,081 subscribers18 August 2026 — 1,080 subscribers21 August 2026 — 1,082 subscribers17 August 202621 August 2026
3 measurements spanning 4 days, net +1. 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 1,080–1,082 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 13:591,082+2
18 Aug 2026, 06:421,080-1
17 Aug 2026, 14:451,081first reading

Engagement

20 posts held, back to 10 August 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
62.9%
avg views ÷ 1,082 subscribers
Avg views / post
680
20 posts measured
Reaction rate
3.36%
reactions ÷ views · ER floor
Posts in window
20
of 20 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. It is computed over the 18 of 20 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 17 August 2026
Posts held20 (10 August 202617 August 2026)
Views total13,602
Reactions total415
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Aug 2026, 14:45 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

Video runtime
4s
Average length
4s

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

415 reactions across 18 posts, in 12 distinct kinds. The most used accounts for 41.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣17241.4%
😭5613.5%
🥰409.64%
💊327.71%
🤔327.71%
💩276.51%
🤪235.54%
143.37%
😴133.13%
😇30.723%
🤩20.482%
👏10.241%

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 18 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 415reactions 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 10 August 2026 to 17 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

17 Aug 2026, 11:45 UTC270 views15 reactionsread 17 August 2026

两天下来已修复大部分问题 热点开不起来刷 melt,官方的内核驱动太老了,同理 gpu 驱动太老会出现渲染异常 剩下的问题在尝试使用不修改安装包的方式解决 以及因为 Android 17 开始一大堆 hidl 的兼容都删了,导致现在 5.10 的设备要么写 aidl 桥接要么整回旧的 累计已修复: - 设置部分页面异常(打不开) - 人脸无法录入 - 蓝牙无声(aac/lhdc),米系耳机页面打不开问题 - 相机闪退 - 锁屏样式无法保存 - ac4 编码疯狂报错 - 震动/红外 有一说一,开包简单,修东西要花点时间 不过有天才程序员在,那都不是问题.png

🥰15

15 Aug 2026, 00:39 UTC532 views7 reactionsread 17 August 2026

marble 尝鲜: https://github.com/Kyuofox/Action_Build_ROM/releases/tag/OS4.0.0.9.XPCCNXM 先让我解决一些小问题再重新发布 bug: - aod - 小爱语音唤醒 使用玻璃材质会有亿丢丢卡顿,建议使用 os3 的材质 使用过程中如果出现软重启是正常情况 日用不建议 Warning / 警告: - 首次使用请安装清除 gpu 缓存的模块 - Do not downgrade packages that have old security patches installed, as this will render your device unbootable / 不要降级安装比此版本旧安全补丁的 ROM,否则后果自负 For Chinese user only: - 不要发到酷安等国内 (CN) 网站,其他随意 Thanks: YuKongA

7

14 Aug 2026, 16:54 UTC556 views33 reactionsread 17 August 2026
Photo

miclaw 最终还是化为了付费用户专享.png

💩27🤣6

14 Aug 2026, 13:29 UTC603 views7 reactionsread 17 August 2026
Photo

已严肃赤石,忽略下版本名 开了 mi17 4.0.0.9

7

14 Aug 2026, 08:39 UTC561 views11 reactionsread 17 August 2026

只是 UI 大业里面的冰山一角,还有更多敷衍的地方呢 哦对了 互联网一部基本都是敷衍的 #HyperOS4

🤣9😭2

13 Aug 2026, 12:09 UTC674 views28 reactionsread 17 August 2026

以小米 18 12+256 5x99 的价格为参考 友商同规格产品接近 6 开头 4 开头拿上一代产品换皮,或者拿上一代的次旗舰换皮 Apple 价格已明析,7/8-1 开头,pro max 顶配可能会超过一万五,标准版到明年发布的话可能比预期的 6 开头更贵,e 或者新 air 来承接 4000-5000 档位 华子象征性涨一点,无非少赚,毕竟利润大头不在手机上 其它产品少发/换皮/倒退已成定局,等 28 年吧

💊26🤔2

13 Aug 2026, 04:32 UTC373 views23 reactionsread 17 August 2026
Forwarded from @installerx_revivedPhoto

修正,小米的逻辑是去系统应用里匹配能处理https的应用,但是installerx被挂载为系统应用,且高优先级地声明自己能处理https,所以被误选中了(他这样的写法也有问题就是了) 刚才急火攻心了,对着小米一顿喷,打脸来的太快

🤔16🤣7

13 Aug 2026, 03:20 UTC575 viewsread 17 August 2026

昨天点过链接的可能会有这个情况,反正也是寄了

Showing the 12 most recent of 20 posts we hold for @Sandrone0721. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

Appears in Telegram’s recommendations for other channels

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.

LSPosed
@LSPosed · 189,402
Telegram ranks this channel #34 of 57 here — alongside 56 others — read 17 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“柒柒的鱼骨头” (@Sandrone0721), 1,082 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/Sandrone0721.

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.