Channel
残念通知频道
@CANNIANNB6
On this record: Topic · Growth · Engagement · Citations · Cite this entry
27,408subscribers
+13,267 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002866950631 |
|---|---|
| Type | Channel |
| Username | @CANNIANNB6 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 18 August 2026 |
| Last confirmed live | 14 October 2026 |
| Measurements held | 40 |
| Confirmed unchanged | 1 time, most recently 14 October 2026 |
| On Telegram | t.me/CANNIANNB6 |
Topic
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Oct 2026, 19:36 | 27,408 | -302 |
| 13 Oct 2026, 12:21 | 27,710 | -1,248 |
| 9 Oct 2026, 11:58 | 28,958 | -494 |
| 5 Oct 2026, 05:22 | 29,452 | -318 |
| 28 Sept 2026, 19:17 | 29,770 | +1,493 |
| 17 Sept 2026, 17:58 | 28,277 | -79 |
| 15 Sept 2026, 12:55 | 28,356 | -134 |
| 13 Sept 2026, 23:58 | 28,490 | -2,094 |
| 12 Sept 2026, 06:17 | 30,584 | -2 |
| 9 Sept 2026, 21:41 | 30,586 | -378 |
| 6 Sept 2026, 15:18 | 30,964 | +122 |
| 4 Sept 2026, 04:19 | 30,842 | -66 |
| 2 Sept 2026, 16:48 | 30,908 | -10 |
| 1 Sept 2026, 13:33 | 30,918 | -47 |
| 31 Aug 2026, 10:34 | 30,965 | -48 |
| 30 Aug 2026, 12:28 | 31,013 | -2 |
| 29 Aug 2026, 14:26 | 31,015 | -11 |
| 28 Aug 2026, 16:32 | 31,026 | +37 |
| 27 Aug 2026, 19:42 | 30,989 | +10,051 |
| 26 Aug 2026, 16:55 | 20,938 | first reading |
Engagement
No public post preview. We read this entry on 18 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@xbnb6661 · 8,39635 postsTH-风花雪月
@GLGYJNB · 1,40616 posts冷淡魔术快斗官方
@LDGWJ · 10,17614 posts清筑改文件主频道［冲10k］
@qingzhu54188 · 5,97710 posts森的心声
@SSDJTNB · 4,4598 posts残念泛滥文件
@Longshen666 · 4,9307 posts七夜改文件官方副频道🇨🇳
@QYFL86 · 5,3186 posts公益资源分享频道🇨🇳
@SNGF666888 · 13,7156 posts小白数据号【唯一正版频道】
@XBSJHJLQ · 1,2644 postsEO三角洲官方频道
@vlp_Doro · 4,8704 posts公益游戏外挂内核直装文件分享频道
@LYGWJ666 · 2,9883 postsMoseDust端口【官方频道】
@SHENYUANNB888 · 18,2823 posts北冥改文件主频道
@bmgwjnb · 9,5213 posts残念和平&PUBG改文件/破解直装/内核项目分享
@CNWJNB · 2,8462 postsAS Game 官方频道 🇨🇳
@DSCHEAT8 · 14,1492 posts小月改文件官方主频道🇨🇳
@apple666o · 12,7402 posts毒蛇代理频道
@cjzhuren2 · 2,4482 postsTG引流｜高速代理｜账号｜各平台业务
@gaosudailinn · 1,9062 postsBing（有问题先看0714置顶）
@nullnb62 · 20,5872 posts
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 22 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. The 19 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@xbnb6661 · 8,39641 postsTH-风花雪月
@GLGYJNB · 1,40630 posts森的心声
@SSDJTNB · 4,45914 posts清筑改文件主频道［冲10k］
@qingzhu54188 · 5,97713 posts冷淡魔术快斗官方
@LDGWJ · 10,17612 posts残念泛滥文件
@Longshen666 · 4,9308 postsEO三角洲官方频道
@vlp_Doro · 4,8708 posts残念和平&PUBG改文件/破解直装/内核项目分享
@CNWJNB · 2,8466 posts七夜改文件官方副频道🇨🇳
@QYFL86 · 5,3186 posts小白数据号【唯一正版频道】
@XBSJHJLQ · 1,2646 posts北冥改文件主频道
@bmgwjnb · 9,5215 postsMoseDust端口【官方频道】
@SHENYUANNB888 · 18,2824 posts公益资源分享频道🇨🇳
@SNGF666888 · 13,7154 posts小月改文件官方主频道🇨🇳
@apple666o · 12,7403 posts公益游戏外挂内核直装文件分享频道
@LYGWJ666 · 2,9883 posts毒蛇代理频道
@cjzhuren2 · 2,4482 postsAS Game 官方频道 🇨🇳
@DSCHEAT8 · 14,1492 postsTG引流｜高速代理｜账号｜各平台业务
@gaosudailinn · 1,9062 postsBing（有问题先看0714置顶）
@nullnb62 · 20,5872 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 14 October 2026 — this entry's latest reading, not the date you are reading this.
“残念通知频道” (@CANNIANNB6), 27,408 subscribers as measured 14 October 2026. Telegram Register, tgregister.com/channel/CANNIANNB6.
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.