選委會選舉|陸啟康主持危機管理委員會會議 又到票站視察 【Now新聞台】選舉委員會選舉於接下來的星期日舉行,選舉管理委員會主席陸啟康主持危機管理委員會會議。 政制及內地事務局局長謝小華亦有出席。選管會在會議上聽取各部門簡報選舉籌備及協調工作,例如網絡安全、保安風險評估等。 陸啟康又到投票站視察工作人員排練。選委會選舉設有五個一般票站,使用電子選民登記冊系統為投票人發出選票,工作人員透過排練熟習以系統派票以及後備模式的發票程序。
💩2

Channel
@nowtv_news
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
42,356subscribers
-448 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001262173775 |
|---|---|
| Type | Channel |
| Username | @nowtv_news |
| Description | 【非官方營運】由程式自動獲取並推送 Now TV 港聞、兩岸國際新聞 |
| Created | 5 August 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 66 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/nowtv_news |
National news — a classification, not a measurement. 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @nowtv_news/171961 · this entry7 Aug 2026, 06:55 UTC | @HKNewsDigest/1638727 Aug 2026, 06:55 UTC | 1.00 | under a minute |
| @nowtv_news/171993 · this entry8 Aug 2026, 07:40 UTC | @HKNewsDigest/1640268 Aug 2026, 07:40 UTC | 1.00 | under a minute |
| @nowtv_news/171994 · this entry8 Aug 2026, 08:50 UTC | @HKNewsDigest/1640298 Aug 2026, 08:50 UTC | 1.00 | under a minute |
| @nowtv_news/171997 · this entry8 Aug 2026, 09:30 UTC | @HKNewsDigest/1640358 Aug 2026, 09:30 UTC | 1.00 | under a minute |
| @nowtv_news/172003 · this entry8 Aug 2026, 13:45 UTC | @HKNewsDigest/1640538 Aug 2026, 13:45 UTC | 1.00 | under a minute |
| @nowtv_news/172005 · this entry8 Aug 2026, 14:45 UTC | @HKNewsDigest/1640578 Aug 2026, 14:45 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @HKNewsDigest | 9 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (9–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 957 comparable posts for this entry, running 5 August 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Recorded under the key clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 18:11 | 42,356 | -14 |
| 12 Nov 2026, 06:39 | 42,370 | +14 |
| 10 Nov 2026, 08:07 | 42,356 | +10 |
| 8 Nov 2026, 16:54 | 42,346 | -31 |
| 7 Nov 2026, 09:38 | 42,377 | +11 |
| 6 Nov 2026, 06:44 | 42,366 | -20 |
| 5 Nov 2026, 02:46 | 42,386 | +8 |
| 4 Nov 2026, 00:47 | 42,378 | -7 |
| 2 Nov 2026, 23:55 | 42,385 | -13 |
| 1 Nov 2026, 21:30 | 42,398 | +3 |
| 31 Oct 2026, 18:39 | 42,395 | -13 |
| 30 Oct 2026, 20:26 | 42,408 | +20 |
| 29 Oct 2026, 22:36 | 42,388 | -27 |
| 28 Oct 2026, 21:35 | 42,415 | +2 |
| 27 Oct 2026, 23:36 | 42,413 | -16 |
| 27 Oct 2026, 00:00 | 42,429 | -16 |
| 25 Oct 2026, 22:27 | 42,445 | -18 |
| 25 Oct 2026, 00:17 | 42,463 | +2 |
| 24 Oct 2026, 03:36 | 42,461 | -5 |
| 23 Oct 2026, 05:47 | 42,466 | first reading |
3,247 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 200 pages of Telegram’s post history, 20 posts per page.
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. It is computed over the 947 of 1,031 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 17 November 2026 |
|---|---|
| Posts held | 3,247 (5 August 2026 – 17 November 2026) |
| Views total | 546,011 |
| Reactions total | 2,965 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 20:56 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.
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
2,878 reactions across 910 posts, in 52 distinct kinds. The most used accounts for 33.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💩 | 967 | 33.6% | |
| 🤡 | 665 | 23.1% | |
| 👍 | 259 | 9.00% | |
| 🤣 | 124 | 4.31% | |
| 🔥 | 106 | 3.68% | |
| 👎 | 64 | 2.22% | |
| 🖕 | 62 | 2.15% | |
| 🤮 | 53 | 1.84% | |
| ❤ | 50 | 1.74% | |
| 😁 | 50 | 1.74% | |
| 😢 | 46 | 1.60% | |
| 🤬 | 43 | 1.49% | |
| 🎃 | 37 | 1.29% | |
| 💊 | 37 | 1.29% | |
| 🙏 | 30 | 1.04% | |
| 🎉 | 27 | 0.938% | |
| 🥱 | 26 | 0.903% | |
| 🐳 | 24 | 0.834% | |
| ☃ | 22 | 0.764% | |
| 👏 | 22 | 0.764% | |
| 32 further kinds | 164 | 5.70% |
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 916 of the 1,000 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 2,878 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 19 October 2026 to 17 November 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.
Telegram’s own ‘edited’ marker: 0 of 1,031 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
選委會選舉|陸啟康主持危機管理委員會會議 又到票站視察 【Now新聞台】選舉委員會選舉於接下來的星期日舉行,選舉管理委員會主席陸啟康主持危機管理委員會會議。 政制及內地事務局局長謝小華亦有出席。選管會在會議上聽取各部門簡報選舉籌備及協調工作,例如網絡安全、保安風險評估等。 陸啟康又到投票站視察工作人員排練。選委會選舉設有五個一般票站,使用電子選民登記冊系統為投票人發出選票,工作人員透過排練熟習以系統派票以及後備模式的發票程序。
💩2
深圳APEC|中俄美元首三方會晤舉行在即 特朗普:若有機會願與普京雙邊會談
💩2
深圳APEC|習近平會見出席APEC會議的領袖
💩2
葵福路食水管爆裂封路 兩的士一度陷入地面受困 【Now新聞台】葵涌葵福路有食水管爆裂,導致路陷,兩架的士一度受困。 兩架的士陷入地面,約晚上8時由拖車協助離開。食水一直從地下滲出,警員到場協助處理。 水務署晚上接報,葵福路有水管爆裂,經了解後確認水管直徑150毫米,不影響食水供應,關上水掣後已停止湧水。葵福路介乎盛福街至永基路全線封閉,直至完成緊急維修工程。 水務署會為水管安排測漏,又利用透地雷達檢測路面下狀況。
🐳2
選委會選舉周日舉行 陸啟康到票站視察 【Now新聞台】選舉委員會選舉於接下來的星期日舉行,選舉管理委員會主席陸啟康視察投票站排練。 陸啟康到投票站向工作人員了解排練情況。選委會選舉設有五個一般票站,使用電子選民登記冊系統為投票人發出選票,工作人員透過排練,熟習以系統派票以及後備模式的發票程序。 陸啟康感謝工作人員的努力和付出,確保各項程序符合法例和指引,並在公開、誠實及公平的情況下舉行選舉。
💩4❤1🖕1
特朗普抵達菲律賓馬尼拉 出席四方安全對話
❤2
中大醫院切錯病人卵巢 指醫生出現短暫認知盲點
💊3
澳洲賽駒安樂死後遭棄垃圾箱 醫院致歉認程序有不足
👎1
深圳APEC|習近平晤巴新總理馬拉佩 馬拉佩稱關閉台北駐巴新代表處決定不易
💩6
消防指石鼓洲焚化廠三級火疑涉燒焊或吸煙 環保署已責成承建商加強措施
💩4
特朗普抵達菲律賓馬尼拉展開亞洲訪問 【Now新聞台】美國總統特朗普抵達菲律賓首都馬尼拉,展開亞洲訪問第一站行程,將出席四方安全會談。 特朗普在東盟峰會尾聲乘坐空軍一號抵達馬尼拉,當地為他舉行歡迎儀式。他之後會與印度總理莫迪、澳洲總理阿爾巴尼斯和日本首相高市早苗,舉行他第二個總統任期以來首次四方安全會談。特朗普又會出席東盟與美國的特別峰會以及東盟晚宴。 特朗普明天會轉赴深圳,出席亞太經合組織會議。他預告此行最受關注的美中俄領導人峰會會聚焦討論核裁軍和俄烏戰事。
👍3👎1
深圳APEC|李家超工商領導人峰會致辭 鼓勵外地企業到大灣區尋覓合作伙伴(李馨萍報道)
💩6
Showing the 12 most recent of 3,247 posts we hold for @nowtv_news. 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.
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.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 29 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 12 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“NOW 新聞” (@nowtv_news), 42,356 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/nowtv_news.
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.