Telegram RegisterThe public register of Telegram
Telegram profile photo for 学习强国公告

Channel

学习强国公告

@UOVZNEWS

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

5,038subscribers

+21 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001376660572
TypeChannel
Username@UOVZNEWS
Created8 January 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held6
Confirmed unchanged1 time, most recently 15 August 2026
On Telegramt.me/UOVZNEWS

Growth

5,0175,0415,0296 August 2026 — 5,017 subscribers6 August 2026 — 5,017 subscribers6 August 2026 — 5,018 subscribers9 August 2026 — 5,028 subscribers12 August 2026 — 5,041 subscribers15 August 2026 — 5,038 subscribers5,0386 August 202615 August 2026
6 measurements spanning 9 days, net +21. 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 5,013–5,045 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 14:185,038-3
12 Aug 2026, 09:445,041+13
9 Aug 2026, 17:225,028+10
6 Aug 2026, 08:505,018+1
6 Aug 2026, 08:305,017no change
6 Aug 2026, 08:285,017first reading

Engagement

20 posts held, back to 3 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 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
51.5%
avg views ÷ 5,038 subscribers
Avg views / post
2,590
3 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
3
of 20 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 5 August 2026
Posts held20 (3 April 20265 August 2026)
Views total7,780
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 04:54 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.

Recent posts

5 Aug 2026, 11:02 UTC≈2,090 viewsread 12 August 2026

经查实,香港方向故障问题系上游运营商市政基础设施因持续高温导致设备过热故障。目前,相关部门已紧急完成设备更换与光缆抢修,受影响的网络线路已全面恢复正常。 建议您重新检查当前业务的连通性。如仍有异常,请随时在工单中反馈,我们将持续为您跟进。感谢您的理解与耐心配合!

Signed Kwan | 💓 | 私聊坏掉了

3 Aug 2026, 09:22 UTC≈2,170 viewsread 12 August 2026

香港方向已经全部恢复。

Signed Kwan | 💓 | 私聊坏掉了

24 Jul 2026, 16:00 UTC≈3,520 viewsread 12 August 2026
Photo

咕咕云沪日专线网络维护通知

Signed Kwan | 💓 | 私聊坏掉了

8 Jul 2026, 04:35 UTC≈4,840 viewsread 12 August 2026
Photo

广西仔加油💪

Signed Kwan | 💓 | 私聊坏掉了

8 Jul 2026, 02:13 UTC≈4,040 viewsread 12 August 2026

📢【咕咕云·泉州机房割接通告】 🔔 割接时间: 2026年7月10日 00:00 - 06:00 🌐 涉及范围: 泉州电信节点全网IP 💥 网络影响: 期间将对泉州核心交换机进行整机替换。由于新旧线路多次倒换,将会出现多次短暂的高延时、抖动及丢包。 ⚠️ 溫馨提示: 升级后网络体验将更佳。请各位用户务必提前做好数据备份及网络切换准备。 由此给您带来的不便,我们深表歉意。感谢您对咕咕云的信任与支持! 咕咕云 2026年7月8日

Signed (🔨🔨🔨打工版)奶油熊子炖菜 / 咕咕售前小助理 | GGY.NET

2 Jul 2026, 06:16 UTC≈4,660 viewsread 12 August 2026

沪日IX故障,正在处理中。 已恢复

Signed Kwan | 💓 | 私聊坏掉了

2 Jul 2026, 06:06 UTC≈4,450 viewsread 12 August 2026

上海区域更换落地IP中。

Signed Kwan | 💓 | 私聊坏掉了

1 Jun 2026, 13:34 UTC≈6,640 viewsread 12 August 2026

咕咕云河南移动节点因通报被拔线,预计整机搬迁至常州电信。

Signed Kwan | 💓 | 私聊坏掉了

31 May 2026, 07:45 UTC≈6,530 viewsread 12 August 2026

咕咕云部分产品已经解除海外限制。

Signed Kwan | 💓 | 私聊坏掉了

25 May 2026, 07:08 UTC≈7,360 viewsread 12 August 2026

咕咕云腾讯香港产品调价通知 感谢您一直以来对咕咕云产品的支持与信任。 由于近期腾讯云对香港地域部分云产品价格进行调整,且IP地址部分区域默认50元一个,导致我司运营成本显著增加。为持续为您提供稳定、优质的服务,我们不得不对受影响的香港产品进行价格优化。 调整详情 调整范围:腾讯云香港产品(原月付价低于 69 元) 新价格:统一调整至 69 元/月 生效时间:新价格将在您下一次续费时生效,当前已生效的订单不受影响。 1继续使用:所有用户将获赠 1 个月时长,续费价格自动调整为 69 元/月,年费为:699元/年 2申请退款:如无法接受本次价格调整,可联系客服为您操作退款,当前周期内全额退款。 为感谢您的理解与支持 ,此次调整实属无奈之举,我们深表歉意,也真诚感谢您的理解与包容。如有任何疑问,欢迎随时联系在线客服,我们将竭诚为您服务。

Signed Kwan | 💓 | 私聊坏掉了

22 Apr 2026, 08:45 UTC≈7,300 viewsread 12 August 2026

沪日ix维护改为明天

Signed Kwan | 💓 | 私聊坏掉了

22 Apr 2026, 07:52 UTC≈6,780 viewsread 12 August 2026

沪日IX临时维护,IP地址会被更换。

Signed Kwan | 💓 | 私聊坏掉了

Showing the 12 most recent of 20 posts we hold for @UOVZNEWS. 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 — 950,874 of 1,481,217entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“学习强国公告” (@UOVZNEWS), 5,038 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/UOVZNEWS.

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.