Telegram RegisterThe public register of Telegram
Telegram profile photo for 百川主频道

Channel

百川主频道

@BCHOOK6

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

7,893subscribers

+472 since we began measuring on 18 August 2026

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

Register entry

Telegram ID-1002187187319
TypeChannel
Username@BCHOOK6
DescriptionDear Telegram team, this channel has never violated any Telegram terms, regulations, or EU criminal law treaties. Please verify carefully with Telegram
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 August 2026
Last confirmed live22 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/BCHOOK6

Growth

7,4217,8937,65718 August 2026 — 7,421 subscribers18 August 2026 — 7,421 subscribers18 August 2026 — 7,461 subscribers22 August 2026 — 7,893 subscribers18 August 202622 August 2026
4 measurements spanning 3 days, net +472. 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 7,350–7,964 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 03:087,893+432
18 Aug 2026, 23:067,461+40
18 Aug 2026, 15:457,421no change
18 Aug 2026, 15:307,421first reading

Engagement

62 posts held, back to 16 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 4 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
9.11%
avg views ÷ 7,893 subscribers
Avg views / post
719
61 posts measured
Reaction rate
2.02%
reactions ÷ views · ER floor
Posts in window
62
of 62 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 22 August 2026
Posts held62 (16 August 202622 August 2026)
Views total43,851
Reactions total884
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken22 Aug 2026, 20:21 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
51
Videos
27
Links
5

Lifetime counters from Telegram’s own channel header, read 22 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
8m 33s
Average length
27s

Measured directly from 19 videos 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

884 reactions across 61 posts, in 12 distinct kinds. The most used accounts for 93.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍82293.0%
242.71%
🕊91.02%
🤬60.679%
🤯60.679%
🤓50.566%
🍌30.339%
🔥30.339%
🤔20.226%
🥰20.226%
😁10.113%
😱10.113%

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

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

22 Aug 2026, 17:59 UTC180 views9 reactionsread 22 August 2026

马上涨价了 火速购买了 现在只需5块 要涨价了 🔥速 https://918.oioix.cn/links/2E8767D1

👍9

Signed baichuan💤(百川集团)

22 Aug 2026, 17:58 UTC184 views6 reactionsread 22 August 2026
Photo

Photo, posted without a caption

👍6

Signed baichuan💤(百川集团)

22 Aug 2026, 17:55 UTC190 views12 reactionsread 22 August 2026
Photo

配置表 还有如果进游戏或者进哪里闪退了,删除配置 即可不闪退

👍111

Signed baichuan💤(百川集团)

22 Aug 2026, 16:54 UTC291 views14 reactionsread 22 August 2026

5米永久还那么多事 隔壁某xue配范围都卡伤永久30某些人还愿意🤔

👍14

Signed 时夕

22 Aug 2026, 16:53 UTC286 views25 reactionsread 22 August 2026
File

1.增加防卡伤 登录卡密后自动下发 2.增加渲染距离,绘制距离更远 3.优化部分人吊针锁针问题 4.更新预判追踪 更准 5.解决大部分人闪退问题 6.更新所有追踪逻辑 等等 只需5块钱就能提 https://918.oioix.cn/links/2E8767D1 每天只限售一部分 http://hualuo.site/public/unbind.php?app=352085dc754d4bf2f830f59358668744 卡密解绑地址 只有三次机会 追踪配置15 0 0 前提量 默认为0

👍22🥰21

Signed 百川💤

22 Aug 2026, 16:44 UTC292 views17 reactionsread 22 August 2026
Video

将世界静音 聆听爆头的声音

👍12🍌3🤬2

Signed 时夕

22 Aug 2026, 16:38 UTC308 views18 reactionsread 22 August 2026
Video

原来修复追踪函数后不配防卡伤也是能爆头的😋😃

👍13🤬4🤓1

22 Aug 2026, 16:30 UTC328 views19 reactionsread 22 August 2026
Photo

这就是过卡伤渲染刷新神力吗😋(与项目无关 仅个人修正 不会发布 不用找我)

👍18🤓1

22 Aug 2026, 15:18 UTC444 views21 reactionsread 22 August 2026
Video

Video, posted without a caption

👍15🤯31🕊1🤓1

22 Aug 2026, 15:06 UTC460 views19 reactionsread 22 August 2026
Photo

难道这就是定制版本🤔听说可以更快刷新敌人绘制且是视频同款防卡伤🤔

👍17🕊1🤯1

22 Aug 2026, 13:46 UTC598 views21 reactionsread 22 August 2026

12点之前截止作者个人版本 截止到今天够卡的 视频效果如上 预判追 无视卡

👍21

Showing the 12 most recent of 62 posts we hold for @BCHOOK6. 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 — 787,386 of 1,584,420entries 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.

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

“百川主频道” (@BCHOOK6), 7,893 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/BCHOOK6.

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.