Telegram RegisterThe public register of Telegram
Telegram profile photo for 软软项目通知《注意看置顶》

Channel

软软项目通知《注意看置顶》

@cknbck

On this record: Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

7,556subscribers

-1,193 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-1002573516454
TypeChannel
Username@cknbck
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/cknbck

Growth

7,5568,8318,193.58 August 2026 — 8,749 subscribers8 August 2026 — 8,758 subscribers11 August 2026 — 8,773 subscribers14 August 2026 — 8,785 subscribers18 August 2026 — 8,797 subscribers21 August 2026 — 8,818 subscribers24 August 2026 — 8,830 subscribers28 August 2026 — 8,831 subscribers30 August 2026 — 8,726 subscribers2 September 2026 — 8,402 subscribers7 September 2026 — 7,556 subscribers8 August 20267 September 2026
11 measurements spanning 30 days, net -1,193. 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,365–9,022 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 06:567,556-846
2 Sept 2026, 10:598,402-324
30 Aug 2026, 20:438,726-105
28 Aug 2026, 03:048,831+1
24 Aug 2026, 22:288,830+12
21 Aug 2026, 07:478,818+21
18 Aug 2026, 08:158,797+12
14 Aug 2026, 22:138,785+12
11 Aug 2026, 17:188,773+15
8 Aug 2026, 23:128,758+9
8 Aug 2026, 03:468,749first reading

Engagement

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

ERR · 30 days
6.44%
avg views ÷ 7,556 subscribers
Avg views / post
487
24 posts measured
Reaction rate
0.762%
reactions ÷ views · ER floor
Posts in window
24
of 44 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 14 of 24 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 26 August 2026
Posts held44 (18 July 202626 August 2026)
Views total11,677
Reactions total40
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 16:12 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.

Reaction mix

60 reactions across 23 posts, in 6 distinct kinds. The most used accounts for 56.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3456.7%
1626.7%
🔥46.67%
😁35.00%
👏23.33%
🎉11.67%

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

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

26 Aug 2026, 04:48 UTC216 viewsread 28 August 2026

最新数据号卡网:https://shop.xianxinhn.xyz/shop/666 各位快来抢购吧!

25 Aug 2026, 11:34 UTC171 viewsread 28 August 2026
Photo

🎮和平精英高质量数据号已补货(绝对质量,纯手工验号) 🎮王者荣耀高质量数据号已补货(补的不多,各位快冲) 🥰 软软数据号官方店铺: 【https://shop.xianxinhn.xyz/shop/666 】 😀下载数据号上号器点我 📣官方QQ交流群点我进入 👀查看申请售后详情点我  咱们的数据号都是人工验号无异常上架卡网的 😃😃😃😃16小时在线客服 https://sh.iiprc.cn/ ✅一手货源✅三年老店✅售后质保 我们的优点:✅诚信✅低价✅质量✅便宜 ✅好用✅服务好✅售后好 🐼专为学生党打造放心购买🤓 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道

23 Aug 2026, 00:25 UTC260 views1 reactionsread 28 August 2026
Photo

🎮和平精英高质量数据号已补货(绝对质量,纯手工验号) 🎮王者荣耀高质量数据号已补货(补的不多,各位快冲) 🥰 软软数据号官方店铺: 【https://shop.xianxinhn.xyz/shop/666 】 😀下载数据号上号器点我 📣官方QQ交流群点我进入 👀查看申请售后详情点我  咱们的数据号都是人工验号无异常上架卡网的 😃😃😃😃16小时在线客服 https://sh.iiprc.cn/ ✅一手货源✅三年老店✅售后质保 我们的优点:✅诚信✅低价✅质量✅便宜 ✅好用✅服务好✅售后好 🐼专为学生党打造放心购买🤓 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道

👍1

22 Aug 2026, 11:49 UTC150 views2 reactionsread 28 August 2026

通知通知 软软数据号刚刚又大量补了一次号,账号特别特别特别质量,各位快去抢购吧

👍2

22 Aug 2026, 02:29 UTC310 views1 reactionsread 28 August 2026
Photo

🎮和平精英高质量数据号已补货(绝对质量,纯手工验号) 🎮王者荣耀高质量数据号已补货(补的不多,各位快冲) 🥰 软软数据号官方店铺: 【https://shop.xianxinhn.xyz/shop/666 】 😀下载数据号上号器点我 📣官方QQ交流群点我进入 👀查看申请售后详情点我  咱们的数据号都是人工验号无异常上架卡网的 😃😃😃😃16小时在线客服 https://sh.iiprc.cn/ ✅一手货源✅三年老店✅售后质保 我们的优点:✅诚信✅低价✅质量✅便宜 ✅好用✅服务好✅售后好 🐼专为学生党打造放心购买🤓 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道

👍1

21 Aug 2026, 12:20 UTC442 views7 reactionsread 28 August 2026

公布一下这个傻逼的联系方式,自己的问题上来就投诉,而且还辱骂客服 手机号:19839869698 归属地:中国 河南省 三门峡市 运营商:移动 各位可以去关照关照他

👍7

21 Aug 2026, 02:21 UTC572 viewsread 28 August 2026
Photo

🎮和平精英高质量数据号已补货(绝对质量,纯手工验号) 🎮王者荣耀高质量数据号已补货(补的不多,各位快冲) 🥰 软软数据号官方店铺: 【https://shop.hnxianxin.cn/shop/666 】 😀下载数据号上号器点我 📣官方QQ交流群点我进入 👀查看申请售后详情点我  咱们的数据号都是人工验号无异常上架卡网的 😃😃😃😃16小时在线客服 https://sh.iiprc.cn/ ✅一手货源✅三年老店✅售后质保 我们的优点:✅诚信✅低价✅质量✅便宜 ✅好用✅服务好✅售后好 🐼专为学生党打造放心购买🤓 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道

20 Aug 2026, 14:15 UTC21 views1 reactionsread 20 August 2026
Forwarded from @KYNB666000

筷雨拦截2.0 已更新 本次更新 更新了版本号 解决了用户提出来的问题 解决了提出问题的用户 更新了最新的思路 《点我下载2.0拦截》 官方频道 @KYNB666000 表情支持😋 还有端口已更新思路 更新规则集即可 验证不上就清除数据 重新来

👍1

20 Aug 2026, 12:53 UTC32 views2 reactionsread 20 August 2026
Forwarded from @yssyjsPhoto

有没有使用伍六七云寄售的商户,他现在已经不干了 以后只进行易支付和服务器行业的业务 大家可以来幺三四云寄售,里面有很多货源,专门对接的用户也可以来 幺三四云寄售无视投诉,平台直接判商家获胜,投诉接口也能死扛🥰 欢迎各位大牛们前来入驻,入驻地址: 134c.cn ✅ 诚信经营不跑路 ✅ 支付手续费率超低 ✅ 自家接口不掉单 ✅稳定安全高速运营 ✅ 企业物理服务器 ✅攻击防御坚如磐石 ✅ 投诉当日处理完 ✅ 凌晨12点自动结算 ❗️限时免邀请码注册❗️

👍2

20 Aug 2026, 02:39 UTC503 views4 reactionsread 28 August 2026
Photo

🎮和平精英高质量数据号已补货(绝对质量,纯手工验号) 🥰 软软数据号官方店铺: 【https://shop.hnxianxin.cn/shop/666 】 😀下载数据号上号器点我 📣官方QQ交流群点我进入 👀查看申请售后详情点我  咱们的数据号都是人工验号无异常上架卡网的 😃😃😃😃16小时在线客服 https://sh.iiprc.cn/ ✅一手货源✅三年老店✅售后质保 我们的优点:✅诚信✅低价✅质量✅便宜 ✅好用✅服务好✅售后好 🐼专为学生党打造放心购买🤓 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道 点我加入官方频道

👍4

19 Aug 2026, 15:48 UTC332 views5 reactionsread 28 August 2026

宝宝们实在不好意思,我才注意到卡网更换链接了,现在的链接已经无法访问 还请大家到最新卡网购买:https://shop.hnxianxin.cn/shop/666 🤓

👍5

19 Aug 2026, 15:42 UTC327 views3 reactionsread 28 August 2026
Photo

完蛋了,怎么天天都让你们得吃了😁

👍3

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

Posts edited after publishing

@cknbck edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
25 August 2026
Most recent edit
25 August 2026

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.

Mentions

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.

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.

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

“软软项目通知《注意看置顶》” (@cknbck), 7,556 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/cknbck.

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.