Telegram RegisterThe public register of Telegram
Telegram profile photo for COCODUCK 公告栏

Channel

COCODUCK 公告栏

@cocoduck_pub

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

3,018subscribers

+86 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-1002140320562
TypeChannel
Username@cocoduck_pub
Created6 March 2024measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/cocoduck_pub

Growth

2,9323,0182,9757 August 2026 — 2,932 subscribers8 August 2026 — 2,936 subscribers11 August 2026 — 2,947 subscribers15 August 2026 — 2,954 subscribers17 August 2026 — 2,959 subscribers21 August 2026 — 2,975 subscribers24 August 2026 — 2,991 subscribers27 August 2026 — 3,004 subscribers30 August 2026 — 3,018 subscribers7 August 202630 August 2026
9 measurements spanning 23 days, net +86. 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,919–3,031 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 13:553,018+14
27 Aug 2026, 14:133,004+13
24 Aug 2026, 23:482,991+16
21 Aug 2026, 08:022,975+16
17 Aug 2026, 22:332,959+5
15 Aug 2026, 06:332,954+7
11 Aug 2026, 19:462,947+11
8 Aug 2026, 11:442,936+4
7 Aug 2026, 14:032,932first reading

Engagement

6 posts held, back to 6 March 2024the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 24 November 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

162 reactions across 5 posts, in 9 distinct kinds. The most used accounts for 37.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6037.0%
👍2515.4%
👏2414.8%
😢2113.0%
💔159.26%
🕊63.70%
😭42.47%
🤨42.47%
😨31.85%

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

Measured over the 6 most recent posts we hold, published 6 March 2024 to 24 November 2025, 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

24 Nov 2025, 10:12 UTC≈9,040 views57 reactionsread 7 August 2026

迫于GFW的防控升级,我们的入口域名招致了全国范围内的大面积DNS污染,造成部分客户端出现连通性故障。 该问题现已修复,需要您在客户端手动更新订阅方可继续使用。 如果不知道如何更新订阅,请参考我们的文档:常见客户端刷新订阅方法 给您造成的不便,我们很抱歉!

34👍7🕊6🤨4💔3😨3

18 Nov 2025, 13:52 UTC≈8,740 views37 reactionsread 7 August 2026

受到全球TOP1网络基础设施供应商Cloudflare宕机影响,目前COCODUCK官网暂时无法打开,大部分节点由于解析层深度绑定的原因也出现大面积不稳定的情况。 目前全球还有数十万个网站和我们共享此至暗时刻。此事之后,我们将带着基础设施与信任一起撤离Cloudflare,然而现在我们只能苦笑等待,感谢并麻烦您与COCODUCK共同见证历史: https://www.cloudflarestatus.com/ 更新: 根据Cloudflare官方公告,我们确信相关故障已经修复,我们的服务已经全面恢复,感谢理解与支持。

😢219💔6👍1

21 Oct 2025, 17:19 UTC≈7,790 views22 reactionsread 7 August 2026

北京时间10月21日17:39到18:20左右,我们主入口服务器所在的广州机房的广港传输线路发生故障,原因查为机房线路时割接合分波(Multiplexer/Demultiplexer)配置错误,同时因故障转移策略失效,大部分用户端并未及时自动切换到厦港备用线路,致使大部分节点不可用,影响时长41分钟。 以上为故障通报,目前服务已经全部恢复,正在和机房沟通后续处理意见,非常抱歉。

👍8💔64😭4

15 Aug 2025, 07:53 UTC≈7,830 views43 reactionsread 7 August 2026

尊贵的会员们,我们很高兴地宣布,COCODUCK自研的安卓手机APP和电视端APP已经上线,诸位现在可以在面板上找到对应的下载链接。 自2024年7月起,我们开启自研APP的项目企划,从最初的技术选型、界面设计、功能规划,到后续的开发调试、设备适配、稳定性优化,我们一路摸索、一路前行。时至今日,即使市面上已经出现了许多面向机场的客户端承包商(经常上网的同学会看到不少类似的),我们依然坚持走全自研道路,因为自研APP不仅承载了我们对用户体验的责任和追求,更要为今后全面的私有化网络建设铺平道路。 使用COCODUCK APP,您和您的家人不必成为网络高手,也能畅快地享受最顶尖的冲浪自由——无论是女友想上ins追星,父母想追的港台剧,还是您工作学习中要用的各种AI工具,扫码登录,一键连接,皆可轻松拥有。 我们希望,COCODUCK能像一个安静又可靠的朋友,默默守护您与世界的联结。不论您身处何地,只要点击“一键加速”,就能穿越复杂

👏2410👍9

29 Jan 2025, 00:43 UTC≈3,960 views3 reactionsread 7 August 2026
Photo

祥蛇纳新福,锐气满屠苏。 COCODUCK祝大家所念皆如愿,所行皆坦途!

3

Showing the 6 most recent of 6 posts we hold for @cocoduck_pub. 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.

Citation-graph rank

Citation-graph rank — 931,245 of 1,627,068entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“COCODUCK 公告栏” (@cocoduck_pub), 3,018 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/cocoduck_pub.

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.