青嶼幹線往九龍方向,近五鼓嶺再有另一宗交通意外,快線受阻;加上較前位置,青馬大橋近青衣行政大樓的意外仍在處理,往九龍方向交通擠塞,龍尾:青嶼幹線轉車站。青嶼幹線往九龍方向的下層行車道仍然開放。 2026-08-07 HKT 18:34

Channel
荃葵青交通 Transport for TW & KT Channel
@TW_KC_TY_Transport_channel
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
1,670subscribers
+16 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 | -1001516588668 |
|---|---|
| Type | Channel |
| Username | @TW_KC_TY_Transport_channel |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/TW_KC_TY_Transport_channel |
Topic
Local community — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 17 September 2026 and assigned it the closest of 31 fixed categories, at 79% confidence. 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 03:18 | 1,670 | -2 |
| 12 Sept 2026, 15:41 | 1,672 | +2 |
| 8 Sept 2026, 09:38 | 1,670 | +2 |
| 2 Sept 2026, 19:58 | 1,668 | +1 |
| 31 Aug 2026, 04:56 | 1,667 | +3 |
| 27 Aug 2026, 19:53 | 1,664 | +1 |
| 25 Aug 2026, 05:43 | 1,663 | +3 |
| 22 Aug 2026, 15:38 | 1,660 | +4 |
| 18 Aug 2026, 20:34 | 1,656 | +2 |
| 15 Aug 2026, 17:16 | 1,654 | +2 |
| 12 Aug 2026, 00:22 | 1,652 | -1 |
| 8 Aug 2026, 18:03 | 1,653 | -2 |
| 6 Aug 2026, 07:18 | 1,655 | no change |
| 6 Aug 2026, 02:10 | 1,655 | +1 |
| 5 Aug 2026, 22:00 | 1,654 | first reading |
Engagement
18 posts held, back to 3 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 2 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 16s
- Average length
- 16s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
6 reactions across 2 posts, in 4 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 33.3% | |
| 💩 | 2 | 33.3% | |
| 🖕 | 1 | 16.7% | |
| 🤬 | 1 | 16.7% |
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 3 of the 18 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 3 August 2026 to 7 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
馬亞木旗下小巴路線調整服務時間 Amendment to Service Hours for Ma Ah Muk Minibuses 🗓️ 17/8/2026 🚐 301M 經有線電視 via Cable TV ⛔ 取消路線 Service CEASED 🚐 302 豪景花園往 Hong Kong Garden → 葵涌廣場 Kwai Chung Plaza 尾班車 Last Departure 00:25→23:00 ⚠️運輸署歸類此路線為循環線,不設葵芳開車時間 In official record, this is a circular line. No official times for departure from Kwai Fong 此客運營業證其他路線 Under same Passenger Service License 🚐 301 荃灣地鐵站 Tsuen Wan MTR ↔ 荃灣廣場 Tsuen W…
(原文)運輸署回覆: 為應付新皇崗口岸開通後的跨境乘客需求,本署已揀選九巴營運來往新皇崗口岸及葵翠邨公共運輸交匯處的巴士服務,該路線將途經葵芳、青衣及大欖隧道轉車站一帶。 本署備悉委員對上述路線的中途站、班次安排、轉乘優惠及分段收費的關注,並會於規劃服務詳情時一併考慮有關意見。本署會於稍後時間適時公布服務詳情。 感謝委員對上述事宜的關注。
60M修訂班次 Timetable Amendment 🗓️ 11/8/2026 詳情於 11/5 試辦時間表一樣 繁忙時間:朝早15分鐘、夜晚最密10分鐘 加密班次:屯門開出部分非繁忙時間 Details same as trial implemented on 11 May Peak hours: AM 15 mins, PM most frequent 10 mins Service interval shortened during serval off-peak sessions from Tuen Mun
2026年08月06日 13:12 運輸署接獲港鐵公司通知,由於錦上路站附近有信號設備故障,來往紅磡站及屯門站的行車時間預計需要額外15-20分鐘。 請考慮使用港鐵其他綫路或其他交通工具。請為行程預留充裕時間。
💩2🖕1🤬1
NA21 加經美孚 Additional Stop at Mei Foo 🗓️ 09/8/2026 所有班次改行荔橋,新增巴士站包括 🚏 葵涌交匯處(來回) 🚏 美孚(來回) 美孚往機場巴士站位於四期近百老匯街 Add departures divert via Lai Chi Kok Bridge, additional stops including 🚏 Kwai Chung Interchange (both bounds) 🚏 Mei Foo (both bounds) From Mei Foo to Airport, board outside phase 4 (Broadway) 路線來回設有下列各站 Calling at following stops (both bounds) 🚏 國泰城 Cathay Pacific City 🚏 機場客運大樓 Passenger Terminal 🚏 港珠澳大橋 Ho…
葵青區議員要求運輸署公佈部份新皇崗路線服務資訊 ① 青衣巴士站位置 ② 轉乘優惠金額、涵蓋路線 ③ 日間及深宵服務時間及班次 ④ 分段收費 提出以下要求 ① 青衣北、青衣中、青衣南至少兩處設站 ② 繁忙時間增加中途站 ③ 轉乘優惠包括 41A、42A、42C、49M、68A、248M、249M ④ 提供分段收費予青衣巴士站
E32A N31 加經匯東街裕豐苑 Calling at Yu Fung Court, Wui Tung Street 🗓️ 10/8/2026 改行翔東邨巴士總站,暫停行經迎禧路 (東環/可譽) Divert via Cheung Tung Bus Terminus NOT CALLING at Ying Hei Road (Century Link & Ho Yu School) 往大嶼山 ⛔取消巴士站 → 🚏 新/替代巴士站 迎禧路裕雅苑 → 裕雅苑雅盛閣(迴旋處) 🆕 匯東街(裕豐苑) 迎東站不變 東環、昇薈北行 → 昇薈南行(⚠️留意對面站) 映灣園之後不變 往荃灣 ⛔取消巴士站 → 🚏 新/替代巴士站 昇薈南行 → 昇薈北行(⚠️留意對面站) 迎東(路邊)→ 🆕 翔東巴士總站 🆕 匯東街(裕豐苑) 裕雅苑兩站不變 For Lantau ⛔ Bus Stop SUSPENDED → 🚏 New/Replacem…
20260804 今日較早時九巴一輛冷氣雙層巴士於長沙灣廣場附近甩轆 九巴將於今晚通宵檢查有相同部件設計巴士,確保安全後會安排重新投入服務
2026年5-6月葵青區脫班 Loss Trips for Kwai Chung & Tsing Yi Buses May - June 2026 朝早繁忙時間 AM Peak >5.0%: 31B 31M 35A >7.5%: 73X 下午繁忙時間 PM Peak >5.0%: 6 30 31 31M 34 36 36A 38 42A 43B 44 58M 60X 67M 235M >7.5%: 31B 33A 42 61M 73X 235 全日 All-Day >5.0%: 31M 33A 40X 41M 42 42A 60X 61M 67M 235 >7.5%: 31B 73X 大嶼山及過海路線脫班率:所有路線<5.0% All loss trip rate for Lantau and Cross-Harbour Services <5.0% ⌨️ 脫班率按照服務詳情表計算無開班次數字vs編定班次數字 ⚠️ 所…
九巴青衣巴士廠首次專營巴士駕駛考試 First Examation for Franchised Bus Driver in KMB Tsing Yi Bus Depot 🗓️ 17/8/2026 星期一 Monday
青衣巴士路線減班 Service Reduction for Tsing Yi Services 🗓️ 10/8/2026 🚍 44M 青衣站 ↔ 葵涌邨(正班) Tsing Yi Station ↔ Kwai Chung Estate (Normal Route) 🗓️ 10/8/2026 🚍 248M 青衣站 ↔ 長亨、長宏 Tsing Yi Station ↔ Cheung Hang & Cheung Wang 🗓️ 17/8/2026 🚍 249M 青衣站 ↔ 涌美路、長青、美景花園 Tsing Yi Station ↔ Chung Mei Road, Cheung Ching & Mayfair Gardens
Showing the 12 most recent of 18 posts we hold for @TW_KC_TY_Transport_channel. 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.
Forward network
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.
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.
@HK_Traffic_News · 44,059
Telegram ranks this channel #7 of 70 here — alongside 69 others — read 28 August 2026
@channelchk · 23,240
Telegram ranks this channel #23 of 72 here — alongside 71 others — read 18 September 2026
@weatherjj · 42,911
Telegram ranks this channel #25 of 74 here — alongside 73 others — read 28 August 2026
@HK_Schedule · 23,100
Telegram ranks this channel #32 of 75 here — alongside 74 others — read 19 September 2026
@rthk_new_c · 49,581
Telegram ranks this channel #34 of 68 here — alongside 67 others — read 25 August 2026
@metwarn · 24,367
Telegram ranks this channel #35 of 71 here — alongside 70 others — read 16 September 2026
@youarenotalonehk · 48,344
Telegram ranks this channel #35 of 68 here — alongside 67 others — read 28 August 2026
@youarenotalonehk_live · 32,152
Telegram ranks this channel #43 of 75 here — alongside 74 others — read 5 September 2026
@hktgb · 38,552
Telegram ranks this channel #51 of 61 here — alongside 60 others — read 31 August 2026
@inmediahknet · 39,025
Telegram ranks this channel #54 of 82 here — alongside 81 others — read 31 August 2026
@nowtv_news · 42,741
Telegram ranks this channel #60 of 72 here — alongside 71 others — read 29 August 2026
This channel appears in 11 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“荃葵青交通 Transport for TW & KT Channel” (@TW_KC_TY_Transport_channel), 1,670 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/TW_KC_TY_Transport_channel.
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.