The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

Channel
CA全防频道《禁广告》
@QIUNBNB
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
329subscribers
-44 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002127561530 |
|---|---|
| Type | Channel |
| Username | @QIUNBNB |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/QIUNBNB |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 |
|---|---|---|
| 6 Oct 2026, 14:02 | 329 | -5 |
| 26 Sept 2026, 12:19 | 334 | -10 |
| 12 Sept 2026, 02:41 | 344 | -2 |
| 4 Sept 2026, 13:41 | 346 | -5 |
| 29 Aug 2026, 00:13 | 351 | -7 |
| 22 Aug 2026, 21:39 | 358 | -6 |
| 15 Aug 2026, 00:52 | 364 | -8 |
| 8 Aug 2026, 06:19 | 372 | no change |
| 7 Aug 2026, 23:08 | 372 | -1 |
| 7 Aug 2026, 11:54 | 373 | first reading |
Engagement
17 posts held, back to 28 November 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
13 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 46.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 46.2% | |
| 🎉 | 3 | 23.1% | |
| 👍 | 3 | 23.1% | |
| 😁 | 1 | 7.69% |
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 7 of the 17 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 28 November 2024 to 28 July 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
【Telegram资源神器】万物搜索引擎全新上线!一键搜索Telegram全网频道/群组,覆盖学习、娱乐、行业交流等海量资源。实时更新精准结果,无需翻页即可找到目标群组,支持关键词智能匹配,让你轻松获取优质社群链接。安全无广告,完全免费使用,即刻加入开启高效资源探索之旅! Telegram群组链接 https://t.me/qysuo
👍1
Signed 不良人·期源⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭
超多搜索引擎 @qysuo
Signed 不良人·期源⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭
出a8卡周卡50月卡120你没看错就是最近市面上超🔥的a8和平项目同步破解最新版购卡联系 @qyyewu
❤1
Signed 期源⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭
祝我生日快乐
🎉3
Signed 期源⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭
✅KUAS-1.2版本✅ 采用全国高端绘制 天线 骨骼 预警 血量 信息 载具 方框🌐 ⭐️采用独家内置旁路⭐️ 支持PUBG64位,全火连打🔥 内存功能:广角 据点 防抖 秒切枪 高帧⚠️ ⚠️采用独家UI,拒绝泛滥⚠️ ✔️下载链接: https://www.123865.com/s/73p8Vv-Vs5Kd ―――――――――――――――― 官方频道:https://t.me/KUASANB 官方频道:https://t.me/KUASANB ―――――――――――――――― 👑反馈: @jiejun888
❤3👍1
Signed 戒君 -【引擎皇帝】
做地推进 https://t.me/+QYWNHaY1_JAxNzFl 100-200💰一单
Signed 期源⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭
地推安装,app,app我们可以生成任何app, 有保底工资,一单100-200不等, 谁做,联系我,工资结账及时,一单一回, 下午六点到晚上12点,上班时间自由都可,无限制地区人员 地推礼品报销,业绩最佳有大额奖励,无限制收人
😁1
Signed 期源⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭𑲭
和平精英公益加速 现在开始公益一个赛季 £功能效果如下 £ ✺【绿体】 【红体】【彩体】 ✺ 【枪械无后】 【人物据点】 ✺ 【辐射开灯】 【人物加速】 ✺ 【人物范围】 【人物变大】 ✺ 【自瞄十字】 【枪械美画】 ✺ 【卡开黑门】 【超高画质】 ✺ 【6000条独家防值】 ✺ 【卡游戏等级】 【卡出生点】 安卓手机都可以使用 主播同款 可稳定传奇 点文字进入 和平精英地铁逃生模式 公益特色 不会出现人脸识别 ;可以组队 不会设备脸 今天新赛季 已经可以正常使用了
❤2
Signed 就叫 月初吧
和平精英公益加速 现在开始公益一个赛季 £功能效果如下 £ ✺【绿体】 【红体】【彩体】 ✺ 【枪械无后】 【人物据点】 ✺ 【辐射开灯】 【人物加速】 ✺ 【人物范围】 【人物变大】 ✺ 【自瞄十字】 【枪械美画】 ✺ 【卡开黑门】 【超高画质】 ✺ 【6000条独家防值】 ✺ 【卡游戏等级】 【卡出生点】 安卓手机都可以使用 主播同款 可稳定传奇 点文字进入 和平精英地铁逃生模式 公益特色 不会出现人脸识别 ;可以组队 不会设备脸 今天新赛季 已经可以正常使用了
Signed 就叫 月初吧
和平精英公益加速 现在开始公益一个赛季 £功能效果如下 £ ✺【绿体】 【红体】【彩体】 ✺ 【枪械无后】 【人物据点】 ✺ 【辐射开灯】 【人物加速】 ✺ 【人物范围】 【人物变大】 ✺ 【自瞄十字】 【枪械美画】 ✺ 【卡开黑门】 【超高画质】 ✺ 【6000条独家防值】 ✺ 【卡游戏等级】 【卡出生点】 安卓手机都可以使用 主播同款 可稳定传奇 点文字进入 和平精英地铁逃生模式 公益特色 不会出现人脸识别 ;可以组队 不会设备脸 今天新赛季 已经可以正常使用了
Signed 就叫 月初吧
戒君开始送免费8级号了 点击加入频道领取8级号 点击加入频道领取8级号 点击加入频道领取8级号 点击加入频道领取8级号 点击加入频道领取8级号 点击加入频道领取8级号 点击加入频道领取8级号
Signed 戒君 -【黑风暴团队】
Showing the 12 most recent of 17 posts we hold for @QIUNBNB. 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.
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
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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“CA全防频道《禁广告》” (@QIUNBNB), 329 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/QIUNBNB.
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.