Telegram RegisterThe public register of Telegram
Telegram profile photo for HiNet 網站公告 HiNetNotify

Channel

HiNet 網站公告 HiNetNotify

@HiNetNotify

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

2,258subscribers

+4 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001068773197
TypeChannel
Username@HiNetNotify
CreatedBetween 1 May 2016 and 28 February 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live24 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/HiNetNotify

Growth

2,2532,2582,255.55 August 2026 — 2,254 subscribers6 August 2026 — 2,254 subscribers6 August 2026 — 2,255 subscribers9 August 2026 — 2,253 subscribers18 August 2026 — 2,257 subscribers21 August 2026 — 2,256 subscribers24 August 2026 — 2,258 subscribers5 August 202624 August 2026
7 measurements spanning 19 days, net +4. 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,252–2,259 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 21:532,258+2
21 Aug 2026, 12:382,256-1
18 Aug 2026, 21:172,257+4
9 Aug 2026, 17:412,253-2
6 Aug 2026, 23:342,255+1
6 Aug 2026, 06:022,254no change
5 Aug 2026, 23:312,254first reading

Engagement

20 posts held, back to 15 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
27.4%
avg views ÷ 2,258 subscribers
Avg views / post
619
5 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
5
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 31 July 2026
Posts held20 (15 June 202631 July 2026)
Views total3,094
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:44 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

31 Jul 2026, 03:40 UTC628 viewsread 7 August 2026

ℹ️ 台馬第三海纜 (TM3) 障礙修復說明 中華電信公司台馬第三海纜 (TM3),已於 7 月 31 日搶修完成並恢復正常運作 https://tg.pe/hnYf (2026/07/31)

29 Jul 2026, 12:00 UTC570 viewsread 7 August 2026

ℹ️ 中華電信 HiNet 屏東數據機房進行部分設備維護作業 HiNet 屏東機房將於 115 年 08 月 06 日 上午 04:00 ~ 08:00 進行設備維護作業,屆時將中斷屏東地區 HiNet 非固定制部分用戶上網服務約 30 分鐘 https://tg.pe/hnA2 (2026/07/29)

29 Jul 2026, 08:20 UTC584 viewsread 7 August 2026

ℹ️ 中華電信新竹營運處設備維護公告:115 年 08 月 18 日 02:00 ~ 06:00 進行設備維護作業 新竹營運處 將於 115 年 08 月 18 日 02:00 ~ 06:00 進行機房設備維護,屆時將中斷新竹地區部分寬頻用戶上網服務約 60 分鐘 https://tg.pe/hnb4 (2026/08/01)

28 Jul 2026, 08:40 UTC663 viewsread 7 August 2026

ℹ️ 橫太平洋快速海纜 (TPE) 計畫性維護說明 中華電信公司橫太平洋快速海纜 (TPE),預計於 115 年 7 月 31 日至 115 年 9 月 4 日進行計畫性維護作業。維護期間 https://tg.pe/hn7D (2026/07/28)

27 Jul 2026, 08:00 UTC649 viewsread 7 August 2026

ℹ️ 中華電信台中 HiNet 機房設備維護公告:115 年 8 月 6 日上午 04:00~08:00 進行設備維護作業 台中 HiNet 機房 將於 115 年 8 月 6 日 上午 04:00 ~ 08:00 進行機房設備維護,屆時將中斷台中地區 HiNet 非固定制部分用戶上網服務約 30 分鐘 https://tg.pe/hnab (2026/07/27)

26 Jul 2026, 09:50 UTC700 viewsread 7 August 2026

ℹ️ 台馬第二海纜 (TDM2) 障礙說明 中華電信公司台馬第二海纜 (TDM2) 於 7 月 26 日發生芯線障礙,訊務已於第一時間疏轉。 中華電信公司技術團隊已派員全力搶修中 https://tg.pe/hnsy (2026/07/26)

24 Jul 2026, 03:00 UTC787 viewsread 7 August 2026

ℹ️ 中華電信台北營運處設備維護公告: 115/7/30 03:00~07:00 進行天母機房寬頻設備維護作業 中華電信台北營運處訂 115 年 7 月 30 日凌晨 03:00~07:00,進行天母機房寬頻機房設備維護作業,屆時「台北市士林天母地區」部分客戶上網、MOD、VPN 寬頻及 MSAN 市話服務將中斷約 60 分鐘,深感抱歉,並感謝您的諒解與配合 https://tg.pe/hnk3 (2026/07/24)

23 Jul 2026, 08:40 UTC761 viewsread 7 August 2026

ℹ️ 中華電信桃園 HiNet 機房設備維護公告:115 年 07 月 30 日上午 02:00~05:00 進行設備維護作業 桃園 HiNet 機房將於 115 年 07 月 30 日上午 02:00 ~ 05:00 進行機房設備維護,屆時將中斷桃園地區 HiNet 固定制部分用戶上網服務約 30 分鐘 https://tg.pe/hnLf (2026/07/23)

23 Jul 2026, 08:30 UTC683 viewsread 7 August 2026

ℹ️ 中華電信台北 HiNet 機房設備維護公告:115 年 08 月 06 日上午 04:00~08:00 進行設備維護作業 台北北二 HiNet 機房將於 115 年 08 月 06 日上午 04:00 ~ 08:00 進行機房設備維護,屆時將中斷大台北地區 HiNet 非固定制部分用戶上網服務約 30 分鐘 https://tg.pe/hnpr (2026/07/24)

23 Jul 2026, 08:20 UTC651 viewsread 7 August 2026

ℹ️ 中華電信新北 HiNet 機房設備維護公告:115 年 08 月 06 日上午 04:00~08:00 進行設備維護作業 台北重新 HiNet 機房將於 115 年 08 月 06 日上午 04:00 ~ 08:00 進行機房設備維護,屆時將中斷新北地區 HiNet 非固定制部分用戶上網服務約 30 分鐘 https://tg.pe/hncs (2026/07/24)

23 Jul 2026, 08:10 UTC596 viewsread 7 August 2026

ℹ️ 中華電信中壢 HiNet 機房設備維護公告:115 年 08 月 13 日上午 04:00~08:00 進行設備維護作業 中壢 HiNet 機房將於 115 年 08 月 13 日上午 04:00 ~ 08:00 進行機房設備維護,屆時將中斷中壢地區 HiNet 非固定制部分用戶上網服務約 30 分鐘 https://tg.pe/hntS (2026/07/31)

21 Jul 2026, 04:50 UTC636 viewsread 7 August 2026

ℹ️ 115 年 8 月 6 日上午 04:00~08:00 高雄地區固網部分設備進行維護 將於 115 年 8 月 6 日上午 04:00~08:00 進行機房設備維護作業,屆時將影響高雄地區部分非固定制用戶上網服務約 30 分鐘 https://tg.pe/hnjp (2026/07/30)

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

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

“HiNet 網站公告 HiNetNotify” (@HiNetNotify), 2,258 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/HiNetNotify.

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.