更新了什么?自己去看提交记录 免root用户请务必更新,LSPosed 也不准不更新)
👍32❤3

Channel
@bbx_show
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
6,320subscribers
+1,173 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002109458887 |
|---|---|
| Type | Channel |
| Username | @bbx_show |
| Description | BBZQ @NPatch https://t.me/+fh1y5zaL_iQ4Njll |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 30 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/bbx_show |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 |
|---|---|---|
| 5 Nov 2026, 16:20 | 6,320 | +27 |
| 2 Nov 2026, 18:30 | 6,293 | +40 |
| 30 Oct 2026, 12:56 | 6,253 | +51 |
| 27 Oct 2026, 14:06 | 6,202 | +55 |
| 24 Oct 2026, 07:06 | 6,147 | +29 |
| 21 Oct 2026, 09:17 | 6,118 | +21 |
| 18 Oct 2026, 11:49 | 6,097 | +24 |
| 15 Oct 2026, 03:07 | 6,073 | +37 |
| 11 Oct 2026, 16:17 | 6,036 | +63 |
| 5 Oct 2026, 02:36 | 5,973 | +89 |
| 26 Sept 2026, 06:58 | 5,884 | +99 |
| 17 Sept 2026, 08:01 | 5,785 | +57 |
| 12 Sept 2026, 23:39 | 5,728 | +76 |
| 9 Sept 2026, 10:58 | 5,652 | +51 |
| 4 Sept 2026, 03:18 | 5,601 | +29 |
| 1 Sept 2026, 01:04 | 5,572 | +35 |
| 30 Aug 2026, 22:11 | 5,537 | no change |
| 28 Aug 2026, 23:56 | 5,537 | +34 |
| 26 Aug 2026, 05:14 | 5,503 | +58 |
| 23 Aug 2026, 07:02 | 5,445 | first reading |
17 posts held, back to 23 August 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 5 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 30 October 2026 |
|---|---|
| Posts held | 17 (23 August 2026 – 30 October 2026) |
| Views total | 16,390 |
| Reactions total | 160 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 13:43 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 6 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.
589 reactions across 16 posts, in 11 distinct kinds. The most used accounts for 58.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 346 | 58.7% | |
| ❤ | 75 | 12.7% | |
| 🥰 | 74 | 12.6% | |
| 🎉 | 31 | 5.26% | |
| 🤣 | 24 | 4.07% | |
| 🤯 | 20 | 3.40% | |
| 🔥 | 9 | 1.53% | |
| 😁 | 6 | 1.02% | |
| 🤔 | 2 | 0.34% | |
| 👏 | 1 | 0.17% | |
| 💯 | 1 | 0.17% |
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 16 of the 17 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 589 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 23 August 2026 to 30 October 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 4 posts held from the last 30 days (25.0%) 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).
更新了什么?自己去看提交记录 免root用户请务必更新,LSPosed 也不准不更新)
👍32❤3
新介面基本完成,同時不再支援從 BBZQ 應用內查看模組設置
👍59❤4🔥3🤔2
https://github.com/HSSkyBoy/BBZQ/releases/tag/v1.5.1 新的 Release 版本已发布,快快更新吧 下一个版本将涉及对当前模组设置页面的重新编写,我想没人不清楚当前的设页面有多么混乱
❤20👍1
本版本更换了签名密钥,无法直接覆盖安装 v1.4.1 及更早版本。 之后的版本将继续使用新签名,可正常覆盖更新。 本版本全面适配哔哩哔哩 9.15.0:大量页面已迁移到 Compose、Kotlin Moss 与 kotlinx 序列化,模块随之重写了对应的定位与过滤逻辑;同时新增多项播放、直播、评论与搜索相关功能。
🎉31❤3🥰2
😈😈😈
👍27❤3🔥2👏1
竖屏播放器突然更新成这样了,你们怎么样?
❤8
https://t.me/onpatch/257 (不要開啟注入加載器) 已在該版本測試可用,打包速度約 5s 完成了史詩級的速度提升
🤯20❤2💯1
- 我追踪的、棘手的、复杂的、有挑战性的、我头疼的 bug,我修复好了!
👍64🥰4
新功能
🥰43👍9🔥4❤1
File, posted without a caption
👍27
很抱歉,我还在排查具体问题。目前看来,卡开屏的问题确实存在,同时还伴随着高性能损耗及其他诸多问题。未能及时排查程式码是我的疏忽,非常抱歉。我正在研究开屏页的情况,看看是否需要重构,因为之前的热重启和冷启动都伴随着不明原因的巨额性能损耗
👍46😁3❤1
Channel name was changed to «哔哩哔哩增强»
Showing the 12 most recent of 17 posts we hold for @bbx_show. 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.
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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“哔哩哔哩增强” (@bbx_show), 6,320 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/bbx_show.
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.