Posted without readable text

Channel
综合公告与重要通知
@PanAnnouncement
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
7,070subscribers
-119 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001524799697 |
|---|---|
| Type | Channel |
| Username | @PanAnnouncement |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/PanAnnouncement |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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 |
|---|---|---|
| 16 Sept 2026, 21:41 | 7,070 | -8 |
| 13 Sept 2026, 07:59 | 7,078 | -7 |
| 9 Sept 2026, 19:21 | 7,085 | -13 |
| 4 Sept 2026, 18:20 | 7,098 | -12 |
| 1 Sept 2026, 04:37 | 7,110 | -9 |
| 29 Aug 2026, 13:47 | 7,119 | -4 |
| 26 Aug 2026, 05:43 | 7,123 | -15 |
| 22 Aug 2026, 21:15 | 7,138 | -9 |
| 19 Aug 2026, 12:23 | 7,147 | -12 |
| 16 Aug 2026, 17:06 | 7,159 | -12 |
| 13 Aug 2026, 06:18 | 7,171 | -10 |
| 10 Aug 2026, 08:38 | 7,181 | -8 |
| 7 Aug 2026, 05:57 | 7,189 | no change |
| 7 Aug 2026, 01:15 | 7,189 | first reading |
Engagement
20 posts held, back to 17 May 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 13 pages 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 20 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 8m 00s
- Average length
- 4m 00s
Measured directly from 2 videos 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
216 reactions across 19 posts, in 14 distinct kinds. The most used accounts for 36.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 78 | 36.1% | |
| ❤ | 60 | 27.8% | |
| 🫡 | 29 | 13.4% | |
| 👎 | 9 | 4.17% | |
| 🙏 | 8 | 3.70% | |
| 🎉 | 7 | 3.24% | |
| 💩 | 7 | 3.24% | |
| 🥴 | 7 | 3.24% | |
| 👏 | 5 | 2.31% | |
| ❤🔥 | 2 | 0.926% | |
| 🏆 | 1 | 0.463% | |
| 😁 | 1 | 0.463% | |
| 🤡 | 1 | 0.463% | |
| 🤮 | 1 | 0.463% |
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 19 of the 20 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 216 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 17 May 2024 to 1 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
丙午新岁,万象更新。愿你在马年里,心中有梦,脚下有风;策马春风,奔赴锦绣前程。祝大年初一吉祥,万事胜意,平安喜乐。 As the Year of the Horse begins, may all things be renewed. May you chase your dreams with the wind beneath your feet and gallop toward a bright future. Wishing you a blessed first day of the New Year and may all go well with you.
❤1
To my friends near and far: 避开喧嚣,预支一份好心情。 2026年,愿我们:有底气、有自由、有底牌。 祝大家新年快乐,万事胜意! Stepping away from the bustle to pre-order a year of joy. In 2026, may we have the confidence, the freedom, and the inner strength to thrive. Happy New Year to you all! 🎆✨
👍3❤1
关于近期采集频道资源的现象说明 最近又看到不少采集整合频道资源的内容。从使用者的角度来看,确实带来了便利,但对我们这些原创频道的建设者而言,这种行为无疑是毁灭性的。一旦资源被采集、整合并广泛传播,就极容易被版权方盯上,引发版权炮击,进而导致频道被封乃至彻底消失。 在此不点名。关于我频道的内容,请勿擅自转载、整合或宣传传播。感谢理解与配合。我也一直秉持“低调运营、不互推合作”的原则,只为频道能稳定长久地存在下去。 影视资源分享本就处于极度敏感的夹缝中——一边是国内版权方严控清理,一边是海外版权组织精准打击。身处其中,步步惊心,唯有谨慎行事,才能延续一丝喘息之机。
❤30
致各位频道主与群组管理员朋友们: 近期,Telegram 平台对涉及版权争议内容的整治行动明显升级:从最初的提醒与警告,迅速过渡到账号冻结、频道删除,清理手段愈发严厉。与此同时,平台内部的不良行为也日益增多:恶意举报同行、假冒管理员诈财、滥用平台漏洞勒索敲诈等事件频发,不仅破坏了生态,也极大消耗了运营者的精力与信任。 面对这一系列不确定与不安全,我们深刻认识到——在这个时代,单打独斗将寸步难行,合作与联防才是唯一出路。 因此,我们倡议发起「ARU-All Telegram Resource Unified Alliance」的建立。此群旨在汇聚真正的频道主与管理者,以身份验证为基础,构建一个信任互通、防御协作、资源共建的平台,携手应对外部压力与内部风险。 【入群方式与审核要求】 为保障平台纯净与沟通真实,入群前请完成以下身份验证流程: 提供您所管理的频道或群组截图; 提供 Telegram 显示您为管理员权限界面的截图。 …
🫡29👍5❤4❤🔥2👏1😁1
祝大家在乙巳蛇年里 顺风顺水顺财神,得财得利得天时,身体健康,万事如意,福绿寿喜,事业发达,家庭和睦,健康长寿
🎉5
感谢一路同行!本频道携全体管理成员在此祝愿2025乙巳蛇年: 家人安康顺遂,福运缠身! 木火相生乙巳年, 灵蛇衔财入家园; 春风化雨人心暖, 盛世欢歌庆团圆。
👍6🎉2🏆1
愿各位在2025年事业有成,生活富足。
👍14👏4❤2
新世界,新分享,用心传递每一份资源! 为更好地应对版权公司的审查并提升管理效率,我们对频道架构进行了全新优化,将原有组织划分为三级体系,便于快速响应和高效管理。 组织架构 第一级:综合管理层 由三个三级频道的审核管理群组成,负责整体监督和协调工作。 第二级:分享公告层 用于发布重要信息和资源更新通知。 包含以下频道: 综合公告板 @PanAnnouncement 综合更新与分享通知频道(Top 10 热门资源) @New_Sharing 第三级:分频道 按网盘类型划分,具体如下: 1. 阿里云盘分区 资源发布频道 @NewAliyunPan 资源交流群 @alyd_g 投稿机器人(支持搜索功能) @AliYunPanBot 讨论区(禁止加入) @AliyunPan_Share_Group 2. 夸克网盘分区 资源发布频道 @NewQuark 资源交流群 @Quark_Share_Group 投稿机器人(支持搜索功能)…
👍10❤4
搞了一个暂时用的频道 https://t.me/NewQuark
👍2
夸克网盘资源分享频道 @Quark_Share_Channel 因版权投诉被封,目前我们正在积极尝试与telegram 和Appletv进行沟通,但无回复
🙏8🥴7
https://115.com/u/TnRb41/1# “115生活”原价500元的年费VIP限时特惠115元!转发推广还能赚钱! 现在考虑用115吧,没赶上3年vip车的兄弟们 用户多的话可以考虑搞群组资源分享
👍3
Showing the 12 most recent of 20 posts we hold for @PanAnnouncement. 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
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.
@NewQuark · 1,2982 posts阿里巴巴影业集团™ 粉丝群
@alyd_g · 10,1981 post好剧分享、热门搜索、更新通知/magic🔮魔法频道
@New_Sharing · 110,0641 postNewAliyunPan
@NewAliyunPan · 1211 post黄黄交流会
@NSFW_PAN · 4,1781 post如何巧妙利用 夸克浏览器™
@Quark_Share_Group · 10,9331 postSharePanBaidu
@SharePanBaidu · 3361 post网盘资源机器人使用指南
@YunPanHelp · 8,4291 post
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@PanAnnouncement named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 8 August 2026 – 13 August 2026
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“综合公告与重要通知” (@PanAnnouncement), 7,070 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/PanAnnouncement.
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.