🚨19:00 #沙田 大埔公路沙田段 往上水方向,近體藝中學有交通意外,龍尾:文化博物館。 #路面情況

Channel
天眼.交通頻道
@ncetransport
On this record: Previous handles · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
47,690subscribers
-111 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001378786668 |
|---|---|
| Type | Channel |
| Username | @ncetransport |
| Created | 12 August 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/ncetransport |
Previous handles
Recorded in 2019 as “抗爭行動交通頻道” — the title held for this same channel (matched by Telegram id, not by handle) in the Pushshift Telegram Dataset, a third-party archive captured in 2019-2020, years before this register made its own first observation. CC BY 4.0, Baumgartner, Zannettou, Squire & Blackburn (2020), Zenodo. A third party’s dated snapshot, not a measurement this register made itself.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 18:18 | 47,690 | -6 |
| 13 Aug 2026, 11:48 | 47,696 | -18 |
| 12 Aug 2026, 14:33 | 47,714 | -5 |
| 11 Aug 2026, 14:08 | 47,719 | -18 |
| 10 Aug 2026, 10:53 | 47,737 | -24 |
| 9 Aug 2026, 08:31 | 47,761 | -17 |
| 8 Aug 2026, 08:43 | 47,778 | -12 |
| 7 Aug 2026, 05:25 | 47,790 | -11 |
| 6 Aug 2026, 01:46 | 47,801 | no change |
| 5 Aug 2026, 22:00 | 47,801 | first reading |
Engagement
142 posts held, back to 4 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 20 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.30%
- avg views ÷ 47,690 subscribers
- Avg views / post
- 622
- 142 posts measured
- Reaction rate
- 0.665%
- reactions ÷ views · ER floor
- Posts in window
- 142
- of 142 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. It is computed over the 115 of 142 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 August 2026 |
|---|---|
| Posts held | 142 (4 August 2026 – 14 August 2026) |
| Views total | 88,261 |
| Reactions total | 509 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 12:05 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
464 reactions across 98 posts, in 9 distinct kinds. The most used accounts for 65.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 302 | 65.1% | |
| 🖕 | 109 | 23.5% | |
| 💩 | 18 | 3.88% | |
| 🍌 | 12 | 2.59% | |
| 🤬 | 9 | 1.94% | |
| ❤ | 8 | 1.72% | |
| 👍 | 2 | 0.431% | |
| 😡 | 2 | 0.431% | |
| 🤮 | 2 | 0.431% |
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 115 of the 142 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 509reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 142 most recent posts we hold, published 4 August 2026 to 14 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
⚠️⚠️#深水埗 地鐵站 18:30 AB, CD出口閘內外 至少20黃衫查出入閘 17:20 AB, CD出口閘內外 至少10黃衫查出入閘
✅18:50更新 較早前 #觀塘 將軍澳道 往將軍澳方向,近翠屏南邨的交通意外已經清理。 #路面情況
⚠️⚠️18:30 #將軍澳 地鐵站 B出口閘內 3黃衫查入閘
🔥1
✅18:50更新 較早前 #觀塘 將軍澳道 往將軍澳方向,近翠屏南邨的交通意外已經清理。 #路面情況
⚠️⚠️17:56 #炮台山 地鐵站 閘內 https://t.me/safetystationinfo/31723
🔥1
⚠️⚠️#深水埗 地鐵站 18:30 AB, CD出口閘內外 至少20黃衫查出入閘 17:20 AB, CD出口閘內外 至少10黃衫查出入閘
🔥1
18:05 #石硤尾 地鐵站 閘內 3藍衫警戒備
🖕2
⚠️⚠️17:32 #中環 地鐵站 🔠出口閘內 2黃衫查入閘
🔥1
14:21 #紅磡 火車站 大堂 4藍衫警戒備
🖕4🔥1
⚠️⚠️08:12 #柯士甸 西鐵站 所有出口閘內外 https://t.me/safetystationinfo/31692
🔥5
⚠️⚠️08:34 #太和 火車站 AB出口閘內 3黃衫查入閘
🔥5
Showing the 12 most recent of 142 posts we hold for @ncetransport. 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.
Posts edited after publishing
@ncetransport edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 8 August 2026
- Most recent edit
- 8 August 2026
Citation-graph rank
Citation-graph rank — 116,134 of 1,340,412entries 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.
@tungchungpoeyes · 1,53312 posts太古細哨
@taikooronaldinho · 1,5807 posts機場channel
@hkairport_news_channel · 2115 posts聯合資訊 - 柴小杏
@chaisiuhanginfo · 7,8464 posts沙田FC資訊頻道
@STunionn · 11,2703 posts【厚德邨Channel】
@hautakfunminus100 · 1932 posts奇蹟Channel
@helpthefightguys · 3481 post📡 民防事務管理局
@HongKongStateCDMA · 711 post理大反送中 PolyU AntiElab
@polyudongotoschool · 1,1961 post張可森 Sam Cheung Ho Sum
@samcheunghs · 1841 post荃民街坊資訊頻道
@twinfochannel · 1,8471 post元朗牛哨兵
@yuenlongox · 9,0551 post
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Mentions
Named by 1 registered channel — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“天眼.交通頻道” (@ncetransport), 47,690 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/ncetransport.
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.