Telegram RegisterThe public register of Telegram
Telegram profile photo for 果酱云通知频道

Channel

果酱云通知频道

@gjy_notice

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

750subscribers

-18 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-1001700514276
TypeChannel
Username@gjy_notice
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live10 October 2026
Measurements held8
Confirmed unchanged2 times, most recently 10 October 2026
On Telegramt.me/gjy_notice

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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

7507687597 August 2026 — 768 subscribers8 August 2026 — 768 subscribers16 August 2026 — 766 subscribers23 August 2026 — 762 subscribers30 August 2026 — 760 subscribers7 September 2026 — 758 subscribers15 September 2026 — 755 subscribers30 September 2026 — 750 subscribers7 August 202630 September 2026
8 measurements spanning 54 days, net -18. 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 747–771 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Sept 2026, 20:39750-5
15 Sept 2026, 22:18755-3
7 Sept 2026, 18:59758-2
30 Aug 2026, 14:04760-2
23 Aug 2026, 18:30762-4
16 Aug 2026, 01:58766-2
8 Aug 2026, 01:49768no change
7 Aug 2026, 12:32768first reading

Engagement

20 posts held, back to 30 April 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 20 posts for this entry, the most recent from 20 December 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

12 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍866.7%
❤433.3%

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 12 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 12 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 30 April 2024 to 20 December 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

20 Dec 2025, 13:03 UTC≈1,450 views2 reactionsread 8 August 2026

请所有12月6日0点(UTC +8)以后消费过的用户找我补单 请所有12月6日0点(UTC +8)以后消费过的用户找我补单 请所有12月6日0点(UTC +8)以后消费过的用户找我补单 (不太确定原数据库到底有没有数据 大概率是没有的 所以先补单)

❤2

20 Dec 2025, 09:17 UTC≈1,220 viewsread 8 August 2026

OVH自动生成账单失败后导致了五六台网站机器被删掉 目前已经移到新服务器部署完成 正在恢复API 预计3小时内恢复 Update: 12月6日0点之后的数据库没有备份 12月6日0点之后的网站为2024年的 我不知道为什么会这样 初步怀疑是宝塔更新导致 目前将临时使用12月5日的数据库 大概三天后把原机器数据库拿到. Update: 我在12月6日0点1分与0点6分更新了宝塔面板...

20 Jul 2025, 06:45 UTC≈2,410 viewsread 8 August 2026

在我最忙的时候遇到了假警察 实在抱歉 时间爆满导致了我无暇顾及其真假. 明天将回复最近两个月的所有工单 先睡一觉了

12 Jul 2025, 17:29 UTC≈2,270 views0 reactionsread 8 August 2026

已更新订阅链接并禁用了之前的订阅链接 请尝试从官网重新导入订阅 (或手动将订阅链接的 .xyz 后缀改为 .auto)

19 May 2025, 16:05 UTC≈2,670 viewsread 8 August 2026

已更新订阅链接并禁用了之前的订阅链接 请尝试从官网重新导入订阅 (或手动将之前的订阅链接后缀从.online 改为.xyz)

18 May 2025, 00:25 UTC≈2,430 views1 reactionsread 8 August 2026
Poll

是否还需要海外的WebSocket(WS)协议节点?(WS会大幅加快节点被墙的速度)🗑

  1. 刚需海外WS节点56%
  2. 并不刚需海外WS节点(TCP WS都能用)44%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

👍1

1 May 2025, 05:32 UTC≈2,100 views3 reactionsread 8 August 2026

五一劳动节快乐 -18%优惠码: 2025workersday 服务器生效时间(UTC-5): 2025/05/01 00:00 ~ 2025/05/05 16:00 上海时间: 2025/05/01 12:00 ~ 2025/05/06 04:00 (对于最近的订阅泄露 仍然在处理当中; 已暂时开启在订阅中展示剩余流量信息 请设置自动更新订阅 每天查看剩余流量 确保能及时发现异常; 之前的补偿即将定下 由于补偿对象比较特别 需要一些额外的时间来处理)

👍3

17 Mar 2025, 05:57 UTC≈1,930 viewsread 8 August 2026

问题已解决 如果今年未更新订阅链接的 请更新订阅链接 (推荐官网一键导入) 如果订阅链接已经为最新的 请更新订阅

28 Jan 2025, 09:00 UTC≈2,220 views0 reactionsread 8 August 2026

新春快乐 25%off优惠码: 2025springfestival 服务器生效时间(UTC-5): 2025/01/28 15:00 ~ 2025/02/02 15:00 上海时间: 2025/01/29 04:00 ~ 2025/02/03 04:00

24 Jan 2025, 01:11 UTC≈1,880 viewsread 8 August 2026

官网正在迁移 预计耗时10分钟 已完成 耗时8分钟

2 Dec 2024, 06:04 UTC≈2,380 viewsread 8 August 2026
Photo

请稍等 机器似乎关机了 不过完全不用担心 已重新部署 耗时3小时

23 Nov 2024, 06:36 UTC≈1,920 viewsread 8 August 2026

官网正在迁移 预计耗时10分钟 已完成 耗时45分钟

Showing the 12 most recent of 20 posts we hold for @gjy_notice. 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.

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

18 May 2025, 00:25 UTCAnonymous Poll101 voters

是否还需要海外的WebSocket(WS)协议节点?(WS会大幅加快节点被墙的速度)🗑

  1. 刚需海外WS节点56%
  2. 并不刚需海外WS节点(TCP WS都能用)44%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 30 April 2024 to 20 December 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“果酱云通知频道” (@gjy_notice), 750 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/gjy_notice.

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.