Telegram RegisterThe public register of Telegram
Telegram profile photo for 币子频道

Channel

币子频道

@bizinb8

On this record: Previous handles · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

6,099subscribers

-18 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1002461764740
TypeChannel
Username@bizinb8
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/bizinb8

Previous handles

@bizinb8 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@xyxnb6
held 8 August 20268 August 2026

Growth

6,0586,1176,087.58 August 2026 — 6,117 subscribers8 August 2026 — 6,117 subscribers11 August 2026 — 6,107 subscribers18 August 2026 — 6,071 subscribers18 August 2026 — 6,073 subscribers21 August 2026 — 6,060 subscribers24 August 2026 — 6,058 subscribers28 August 2026 — 6,070 subscribers31 August 2026 — 6,114 subscribers3 September 2026 — 6,116 subscribers9 September 2026 — 6,099 subscribers6,0998 August 20269 September 2026
11 measurements spanning 31 days, net -18. 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 6,049–6,126 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 04:176,099-17
3 Sept 2026, 10:296,116+2
31 Aug 2026, 11:476,114+44
28 Aug 2026, 03:586,070+12
24 Aug 2026, 19:166,058-2
21 Aug 2026, 09:156,060-13
18 Aug 2026, 15:146,073+2
18 Aug 2026, 10:316,071-36
11 Aug 2026, 14:426,107-10
8 Aug 2026, 18:306,117no change
8 Aug 2026, 18:176,117first reading

Engagement

43 posts held, back to 12 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 6 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
2.90%
avg views ÷ 6,099 subscribers
Avg views / post
177
15 posts measured
Reaction rate
0.365%
reactions ÷ views · ER floor
Posts in window
18
of 43 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 7 of 15 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 18 August 2026
Posts held43 (12 July 202618 August 2026)
Views total2,650
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 10: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

Video runtime
15s
Average length
15s

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

21 reactions across 17 posts, in 3 distinct kinds. The most used accounts for 57.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1257.1%
838.1%
😭14.76%

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

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

18 Aug 2026, 09:34 UTC1 viewsread 18 August 2026
Forwarded from @LDL123Photo

💰 转账给你 23.89 U 请在24小时内领取

18 Aug 2026, 09:30 UTC1 views1 reactionsread 18 August 2026
Forwarded from @GeminiESPFile

未来Pro版正式版 此次修复的bug为 自瞄更改为内核级无模块陀螺仪自瞄 自瞄算法与VS一样 增加保存配置功能 修复被瞄预警失效的问题 修复手雷预警失效的问题 修复部分安卓16设备不可以使用的问题 增加观透功能(观透功能默认开启过滤队伍要手动与某娃相同) 修复开启载具绘制满地的载具血条 修复闪框解密失效的问题 优化追踪预判 优化CPU占用(应该不会卡死机) 弓弩追踪概率增加 修复录屏闪退的问题 修复物资无法正常使用的问题 适配安卓17 对防高风险增加检测到即将高风险自动闪退保号功能(闪退保号成功概率为75%) 增加巡查与观战预警 未来主频道: https://t.me/GeminiESP 未来衍生频道: https://t.me/NX7878

👍1

18 Aug 2026, 08:19 UTC2 views1 reactionsread 18 August 2026
Forwarded from @GeminiESPFile

未来Pro版正式版 此次修复的bug为 自瞄更改为内核级无模块陀螺仪自瞄 自瞄算法与VS一样 增加保存配置功能 修复被瞄预警失效的问题 修复手雷预警失效的问题 修复部分安卓16设备不可以使用的问题 增加观透功能(观透功能默认开启过滤队伍要手动与某娃相同) 修复开启载具绘制满地的载具血条 修复闪框解密失效的问题 优化追踪预判 优化CPU占用(应该不会卡死机) 弓弩追踪概率增加 修复录屏闪退的问题 修复物资无法正常使用的问题 适配安卓17 对防高风险增加检测到即将高风险自动闪退保号功能(闪退保号成功概率为75%) 增加巡查与观战预警 未来主频道: https://t.me/GeminiESP 未来衍生频道: https://t.me/NX7878

👍1

18 Aug 2026, 04:22 UTC6 views1 reactionsread 18 August 2026
Forwarded from @GeminiESPFile

未来Pro版正式版 此次修复的bug为 自瞄更改为内核级无模块陀螺仪自瞄 自瞄算法与VS一样 增加保存配置功能 修复被瞄预警失效的问题 修复手雷预警失效的问题 修复部分安卓16设备不可以使用的问题 增加观透功能(观透功能默认开启过滤队伍要手动与某娃相同) 修复开启载具绘制满地的载具血条 修复闪框解密失效的问题 优化追踪预判 优化CPU占用(应该不会卡死机) 弓弩追踪概率增加 修复录屏闪退的问题 修复物资无法正常使用的问题 适配安卓17 对防高风险增加检测到即将高风险自动闪退保号功能(闪退保号成功概率为75%) 增加巡查与观战预警 未来主频道: https://t.me/GeminiESP 未来衍生频道: https://t.me/NX7878

👍1

18 Aug 2026, 01:21 UTC12 viewsread 18 August 2026
Forwarded from @GeminiESPFile

未来Pro版正式版 此次修复的bug为 自瞄更改为内核级无模块陀螺仪自瞄 自瞄算法与VS一样 增加保存配置功能 修复被瞄预警失效的问题 修复手雷预警失效的问题 修复部分安卓16设备不可以使用的问题 增加观透功能(观透功能默认开启过滤队伍要手动与某娃相同) 修复开启载具绘制满地的载具血条 修复闪框解密失效的问题 优化追踪预判 优化CPU占用(应该不会卡死机) 弓弩追踪概率增加 修复录屏闪退的问题 修复物资无法正常使用的问题 适配安卓17 对防高风险增加检测到即将高风险自动闪退保号功能(闪退保号成功概率为75%) 增加巡查与观战预警 未来主频道: https://t.me/GeminiESP 未来衍生频道: https://t.me/NX7878

14 Aug 2026, 17:53 UTC≈1,010 views1 reactionsread 18 August 2026
Photo

币子失控进化打矿功能矿工房例子 中间放箱子记录家坐标 周围都是双扇门

👍1

14 Aug 2026, 12:01 UTC69 viewsread 18 August 2026
File

❤️失控进化公益1.2❤️ 无模块陀螺仪/内核陀螺仪/自动打矿 😍卡密随便输入😍 Rthook twt 天堂 TH Rtdev 纯c读写 ❤️失控进化已经更新触摸检测 使用无模块陀螺仪和内核陀螺仪即可 点我查看UI 点我交流 下载sh 更新内容: 1.修复打矿 物资绘制 2.更新自动回家 自动放矿 绘制物资(领地柜 矿石 卡等) 自动打矿/区分矿物/自动回家放矿 后续更新更多功能 好玩记得分享给朋友哦 更新频道 @bizinb 交流频道https://t.me/TwTnb6

14 Aug 2026, 11:55 UTC≈1,160 views1 reactionsread 18 August 2026
File

❤️失控进化公益1.2❤️ 无模块陀螺仪/内核陀螺仪/自动打矿 😍卡密随便输入😍 Rthook twt 天堂 TH Rtdev 纯c读写 ❤️失控进化已经更新触摸检测 使用无模块陀螺仪和内核陀螺仪即可 点我查看UI 点我交流 下载sh 更新内容: 1.修复打矿 物资绘制 2.更新自动回家 自动放矿 绘制物资(领地柜 矿石 卡等) 自动打矿/区分矿物/自动回家放矿 后续更新更多功能 好玩记得分享给朋友哦 更新频道 @bizinb 交流频道https://t.me/TwTnb6

1

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

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

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

“币子频道” (@bizinb8), 6,099 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/bizinb8.

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.