Telegram RegisterThe public register of Telegram
Telegram profile photo for COffeeCLoud | 通知面板

Channel

COffeeCLoud | 通知面板

@coffeenotice

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

483subscribers

+24 since we began measuring on 31 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003959457974
TypeChannel
Username@coffeenotice
Created15 April 2026measured — dated from the channel’s first post
First recorded31 August 2026
Last confirmed live18 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/coffeenotice

Topic

Technology — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 69% 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

45948347131 August 2026 — 459 subscribers1 September 2026 — 462 subscribers10 September 2026 — 471 subscribers18 September 2026 — 483 subscribers31 August 202618 September 2026
4 measurements spanning 19 days, net +24. 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 455–487 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 20:00483+12
10 Sept 2026, 12:40471+9
1 Sept 2026, 04:27462+3
31 Aug 2026, 06:45459first reading

Engagement

6 posts held, back to 15 April 2026the 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 6 posts for this entry, the most recent from 17 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

48 reactions across 4 posts, in 6 distinct kinds. The most used accounts for 37.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩1837.5%
😱1327.1%
1122.9%
👍36.25%
🤯24.17%
😘12.08%

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 4 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 48 reactions 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 15 April 2026 to 17 June 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

17 Jun 2026, 16:35 UTC≈2,510 views6 reactionsread 31 August 2026

🌐 官方域名:https://aicoffee.app 🔄 跳转域名:https://咖啡云.net 🛟 备用域名:https://kafei26.cloud ━━━━━━━━━━━━━━ 🚀 V-Ninja 定制协议更新公告 近期我们持续对 V-Ninja 客户端进行升级与优化,修复了多个已知问题,并新增多项实用功能(包括不限于): ✅ 支持链式代理(Proxy Chain) ✅ 支持 Mihomo 内核替换 ✅ 支持 Windows 7 系统 ✅ 优化连接稳定性与兼容性 ✅ 提升客户端性能与使用体验 📢 官方频道: https://t.me/ninja_ss2 建议所有用户升级至最新客户端,以获得最佳的稳定性、兼容性及功能支持。 V-Ninja 将持续迭代,为大家带来更强大、更稳定、更流畅的网络连接体验。

6

26 Apr 2026, 08:29 UTC≈4,370 views35 reactionsread 31 August 2026

目前我们服务挺稳的,尤其是官方客户端。 在这次动荡中,我们整体不错,所以决定涨价。。。 平均价格上调 2.5-5元

💩18😱13👍3😘1

17 Apr 2026, 10:16 UTC≈4,770 views5 reactionsread 31 August 2026

非常抱歉,近期给(部分ios/路由器)用户带来不好的体验,因为普通协议(ss/anytls)的不可抗力,机器被不断的拔线,我们无法提供稳定的服务。 多方面考虑下,本月普通协议我们暂时只能提供海外入口或直连过度,但是我们会尽量优化海外连接效果。 预计下个月我们会从新增加中转为普通协议客户提供更好的服务。 补充: 1. ninja 客户不受到影响,并且随着ninja的使用量,我们不断的增加带宽。

5

16 Apr 2026, 09:43 UTC≈4,050 views2 reactionsread 31 August 2026

机房故障,预计晚一些恢复。

🤯2

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

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

“COffeeCLoud | 通知面板” (@coffeenotice), 483 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/coffeenotice.

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.