Telegram RegisterThe public register of Telegram

Channel

采白通知频道

@cbdknb

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

2,402subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002142144166
TypeChannel
Username@cbdknb
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/cbdknb

Growth

2,3992,4022,400.57 August 2026 — 2,401 subscribers7 August 2026 — 2,401 subscribers8 August 2026 — 2,402 subscribers10 August 2026 — 2,399 subscribers13 August 2026 — 2,402 subscribers7 August 202613 August 2026
5 measurements spanning 6 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 2,399–2,402 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 04:342,402+3
10 Aug 2026, 15:132,399-3
8 Aug 2026, 00:412,402+1
7 Aug 2026, 13:482,401no change
7 Aug 2026, 12:582,401first reading

Engagement

16 posts held, back to 1 June 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
12.2%
avg views ÷ 2,402 subscribers
Avg views / post
292
11 posts measured
Reaction rate
0.226%
reactions ÷ views · ER floor
Posts in window
11
of 16 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 4 of 11 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 2 August 2026
Posts held16 (1 June 20262 August 2026)
Views total3,213
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 13:48 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
3m 13s
Average length
3m 13s

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

7 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 85.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
685.7%
👍114.3%

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

Measured over the 16 most recent posts we hold, published 1 June 2026 to 2 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

2 Aug 2026, 15:20 UTC157 viewsread 7 August 2026
Forwarded from @KSCNYYDS666Photo

ZygiskNext 1.4.4 正式版 适配 Meta Quest 的 stub zygote 修复检测问题 修复光速虚拟机 arm32 转译支持 适配 KernelSU 的模拟软重启 提升安全性 获取链接:点击我跳转

2 Aug 2026, 15:20 UTC168 viewsread 7 August 2026
Forwarded from @KSCNYYDS666Photo

更新日志: 更换 hook 方案,大幅提升性能,要求框架实现允许在系统服务中加载原生库 升级到 libxposed API 101 最低支持版本提升至 Android 11 提升应用列表加载速度 新增可按应用单独设置的激进意图过滤选项 优化配置与列表刷新流程 移除 Firebase 获取链接:点击我跳转

1 Aug 2026, 10:54 UTC93 viewsread 7 August 2026
Forwarded from @KSCNNB66Photo

⭐️🌈售后无忧,我们承诺提供全网最优质的售后服务,有任何问题,第一时间联系客服,我们全力为您解决 🙏环境刷机提卡链接:点击我跳转 ⭐️🌈采用独家解密绝不是市面上那种泛滥拉扎 不会三方或者协议 采用的是独家驱动 并且是配了模型漏打 后续会添加追踪 已上架三角洲独家解密:点击我跳转

31 Jul 2026, 10:06 UTC105 viewsread 7 August 2026
Forwarded from @KSCNNB66Photo

⭐️🌈售后无忧,我们承诺提供全网最优质的售后服务,有任何问题,第一时间联系客服,我们全力为您解决 🙏环境刷机提卡链接:点击我跳转 ⭐️🌈采用独家解密绝不是市面上那种泛滥拉扎 不会三方或者协议 采用的是独家驱动 并且是配了模型漏打 后续会添加追踪 已上架三角洲独家解密:点击我跳转

30 Jul 2026, 06:03 UTC201 viewsread 7 August 2026
Forwarded from @KSCNNB66File

可以修改品牌厂商/型号/设备市场名/指纹/芯片等 获取链接:点击我跳转

28 Jul 2026, 09:52 UTC260 viewsread 7 August 2026
Forwarded from @KSCNNB66File

下载单个刷入 HAM依赖zygisk不是lsp zygisk打开选择仅挂载 下边三个选项打开上边两个最后一个不用打开 获取无广频道:点击我跳转

28 Jul 2026, 09:45 UTC252 views1 reactionsread 7 August 2026
Forwarded from @KSCNNB66File

最新密钥 ✅✅✅ 获取频道:点击跳转 此频道为无广

1

23 Jul 2026, 09:05 UTC369 views1 reactionsread 7 August 2026
Forwarded from @KSCNNB66File

发布频道:点我跳转

1

17 Jul 2026, 08:12 UTC601 views1 reactionsread 7 August 2026
Forwarded from @KSCNNB66File

隐藏模块 别人花六七十做的,给你们公益 早就说要发了主要是没有精力在弄别的东西 获取链接:点击跳转

1

15 Jul 2026, 15:04 UTC551 views1 reactionsread 7 August 2026
Forwarded from @KSCNYYDS666

😎😎🎮三角洲和暗区专属环境😆😆 更新❗️日志:7月13❗️ 用此环境可以达到不偏不漏,前提必须没分过账号的设备,你们可以去线刷,或者是恢复出厂设置 ❗️❗️❗️模块获取❗️❗️❗️ 上号必须执行:清理下发文件和改权限 封号1/3可以执行:清理 第一步:TA模块 第二步:TEES 第三步:改机型 第四步:伪装cpu+GPU+防设备标记+清理 阻止应用检测SELinux修改:模块 密钥:吊销就跟新 网盘链接已更新最新:跳转 最重要的一步:思路可以不用 思路:有用 效果图:没必要完美环境 取消一键,等我做云端 单个模块刷入教程教程:教程 线刷教程:小白教程 ❤️❤️❤️支持一下❤️❤️❤️ 🎯🎯🎯游戏数据🎯🎯🎯 瓦手游[1.23.0]:数据

1

16 Jun 2026, 10:55 UTC≈6,470 views3 reactionsread 7 August 2026
Photo

三角洲国际服iOS 全系统子追 无视举报和检测 需要搭配端口需要可以进群

2👍1

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

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

“采白通知频道” (@cbdknb), 2,402 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/cbdknb.

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.