Telegram RegisterThe public register of Telegram
Telegram profile photo for OuO Notification

Channel

OuO Notification

@OuONotification

On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

7,944subscribers

-36 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-1001817568446
TypeChannel
Username@OuONotification
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live4 September 2026
Measurements held11
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/OuONotification

Growth

7,9437,9807,961.57 August 2026 — 7,980 subscribers7 August 2026 — 7,979 subscribers10 August 2026 — 7,976 subscribers13 August 2026 — 7,971 subscribers16 August 2026 — 7,966 subscribers19 August 2026 — 7,963 subscribers22 August 2026 — 7,958 subscribers25 August 2026 — 7,954 subscribers28 August 2026 — 7,947 subscribers31 August 2026 — 7,943 subscribers4 September 2026 — 7,944 subscribers7,9447 August 20264 September 2026
11 measurements spanning 28 days, net -36. 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 7,937–7,986 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 05:367,944+1
31 Aug 2026, 10:257,943-4
28 Aug 2026, 09:337,947-7
25 Aug 2026, 10:387,954-4
22 Aug 2026, 14:437,958-5
19 Aug 2026, 15:467,963-3
16 Aug 2026, 18:337,966-5
13 Aug 2026, 12:597,971-5
10 Aug 2026, 18:087,976-3
7 Aug 2026, 14:387,979-1
7 Aug 2026, 11:167,980first reading

Engagement

23 posts held, back to 4 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 19 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
28.8%
avg views ÷ 7,944 subscribers
Avg views / post
2,290
3 posts measured
Reaction rate
0.262%
reactions ÷ views · ER floor
Posts in window
3
of 23 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 25 August 2026
Posts held23 (4 January 202625 August 2026)
Views total6,860
Reactions total18
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 19:45 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

537 reactions across 22 posts, in 13 distinct kinds. The most used accounts for 27.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩14927.7%
11120.7%
👍8916.6%
👏5610.4%
👎346.33%
😢295.40%
😱234.28%
🤯183.35%
🤡81.49%
👌71.30%
🥰61.12%
🔥50.931%
🤔20.372%

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

Measured over the 23 most recent posts we hold, published 4 January 2026 to 25 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

25 Aug 2026, 12:59 UTC≈1,340 views4 reactionsread 28 August 2026

#维护通知 OuO Network 我们预计于 UTC+0800 08/27/26 02:00 后对系统进行维护。 预期会出现的情况: • 官网短时不可访问 • 节点短时断连 为您带来的不便深表歉意

👎3👌1

24 Aug 2026, 09:36 UTC≈1,770 views4 reactionsread 28 August 2026

#维护通知 OuO Network 开始尝试修复HK地区的解锁,修复过程中,您的流量可能会多次短时中断,给您带来的不便深表歉意。

👍2👎2

16 Aug 2026, 22:21 UTC≈3,750 views10 reactionsread 28 August 2026

#维护通知 OuO Network 已尝试修复异常解锁

👍81👎1

4 Aug 2026, 16:42 UTC≈6,610 views19 reactionsread 28 August 2026

OuO Network 预祝您七夕快乐! 85折优惠码: 2026-Chinese_Valentine-15%OFF 活动时间: UTC+0800 08/05/2026 00:00 - 08/21/2026 23:59 ⚠️ 仅限月/季/半年付

14🥰5

31 Jul 2026, 14:10 UTC≈7,110 views1 reactionsread 28 August 2026

#域名更新 域名发生异常污染,域名更换至 start.ouonetwork.com

1

7 Jun 2026, 16:08 UTC≈15,900 views37 reactionsread 28 August 2026

OuO Network 祝您618快乐! 85折优惠码: 2026-618-15%OFF 活动时间: UTC+0800 06/08/2026 00:00 - 06/21/2026 23:59 ⚠️ 仅限月/季付

35👏2

30 May 2026, 16:13 UTC≈16,000 views20 reactionsread 28 August 2026

#OuO公告 关于 SS/SS2022 即将停止使用通知 尊敬的用户: 您好,当前部分地区疑似发生SS/SS2022 协议精准QoS。 如确定有强关联性,为保障服务的稳定与可用性,后续将逐步关闭 SS/SS2022 协议的下发和使用。 近期我们将填充 AnyTLS 类型节点,给您带来的不便,我们深表歉意。

👍16👎4

18 May 2026, 19:37 UTC≈13,900 views1 reactionsread 28 August 2026

#OuO公告 我们确认当前流程可正确更新,如您无法更新请尝试使用流量或确认是否存在共享行为。

1

18 May 2026, 17:21 UTC≈12,700 views10 reactionsread 28 August 2026

#OuO公告 我们当前已完成第一周期的过渡,务必更新您的订阅以正常使用。Clash请使用Meta订阅格式进行订阅。

🤡82

18 May 2026, 09:28 UTC≈14,000 views17 reactionsread 28 August 2026

#OuO公告 我们将于 UTC+0800 05/19/26 01:00 对节点进行过渡期结束的协议调整,SS节点将完全推送至SS2022,届时请您再次更新订阅以保障使用。 当前我们已确认到不可控的服务降级再次发生,速率近期会发生劣化,请您优先尝试Vless节点。感谢您的支持与理解。 我们正在积极的寻找方案以优化您的体验。

😱152

7 May 2026, 07:52 UTC≈13,600 viewsread 28 August 2026

#故障通知 Emby服务商的纽约和洛杉矶机房掉线中,已经给服务商发送工单,请耐心等待恢复。

29 Apr 2026, 16:03 UTC≈13,800 views45 reactionsread 28 August 2026

OuO Network 祝您51快乐! 8折优惠码: 2026-05-01-20%OFF 活动时间: UTC+0800 04/30/2026 00:00 - 05/05/2026 23:59 ⚠️ 仅限月/季付

👎24👍129

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

FlowerCloud - 233号杰尼龟
@flower_cloud · 34,312
Telegram ranks this channel #11 of 46 here — alongside 45 others — read 3 September 2026
Clash Verge Rev Channel
@clash_verge_re · 79,623
Telegram ranks this channel #12 of 64 here — alongside 63 others — read 19 August 2026
翻翻墙 | 机场评测
@ffqchannel · 60,932
Telegram ranks this channel #13 of 45 here — alongside 44 others — read 22 August 2026
前女友们用过的机场—始于机场,不止机场
@gebaopiCloud · 100,847
Telegram ranks this channel #17 of 56 here — alongside 55 others — read 15 August 2026
科学上网观察与机场测速
@jichangtj · 133,836
Telegram ranks this channel #18 of 54 here — alongside 53 others — read 15 August 2026
海豚机场测评|用户侧体验|测速频道
@haitun_channel · 36,540
Telegram ranks this channel #21 of 39 here — alongside 38 others — read 1 September 2026
Matsuridayo GitHub
@MatsuriDayo · 45,312
Telegram ranks this channel #21 of 58 here — alongside 57 others — read 30 August 2026
FlClash Channel
@FlClash · 45,083
Telegram ranks this channel #24 of 53 here — alongside 52 others — read 28 August 2026
Duyao|SpeedTest|科技生活|资讯转发
@DuyaoSS · 67,900
Telegram ranks this channel #24 of 45 here — alongside 44 others — read 20 August 2026

This channel appears in 9 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“OuO Notification” (@OuONotification), 7,944 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/OuONotification.

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.