#九巴 路線13(安峯<>西九龍中心)將於8月10日起,延長服務時間。 詳情請參閱上圖。 #觀塘區 #太子道東 #亞皆老街 #旺角 #深水埗區
❤1
Channel
@busnohkmtr
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,152subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001447691142 |
|---|---|
| Type | Channel |
| Username | @busnohkmtr |
| Created | 6 September 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/busnohkmtr |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 13:26 | 3,152 | -1 |
| 9 Aug 2026, 16:31 | 3,153 | -1 |
| 7 Aug 2026, 00:58 | 3,154 | +1 |
| 6 Aug 2026, 04:50 | 3,153 | no change |
| 6 Aug 2026, 01:48 | 3,153 | first reading |
19 posts held, back to 26 July 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 3 pagesof 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 5 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 19 (26 July 2026 – 6 August 2026) |
| Views total | 8,750 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:45 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.
6 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 50.0% | |
| 👍 | 3 | 50.0% |
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 5 of the 19 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 26 July 2026 to 6 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.
#九巴 路線13(安峯<>西九龍中心)將於8月10日起,延長服務時間。 詳情請參閱上圖。 #觀塘區 #太子道東 #亞皆老街 #旺角 #深水埗區
❤1
循環線273A將於8月10日起,每日所有班次延長為彩石邨來往華明邨。 詳情請參閱上圖。 #北區
巴士路線44M(青衣城/長安邨<>葵涌邨/新葵興花園)將於8月10日起,調整少部分班次。 詳情請參閱上圖。 #青衣 #葵青區
#城巴 特快路線790(清水灣半島<>尖沙咀麽地道)於8月2日起,延長服務時間;並增設特別班次加經將軍澳工業邨,途經:駿日街、駿宏街、駿才街、駿盈街及駿光街。 詳情請參閱上圖。 #將軍澳區 #油尖旺區
#城巴 路線796x將於8月2日起,縮短為日出康城來往紅磡,不再途經尖沙咀,並改為循環線形式運作,依次序途經:清水灣半島、怡明邨、至善街、天晉、將軍澳站、唐明街、調景嶺站、彩明苑、健明邨、家維邨、馬頭圍道、馬頭圍邨、馬頭涌道、富豪東方酒店、譽港灣、太子道東、調景嶺站、健明邨、唐明苑、TKO Spot、唐俊街、寶盈花園、至善街。詳情請參閱上圖。 受影響乘客請改搭城巴路線790或796p。 #將軍澳區 #九龍城區
👍3❤2
巴士路線67M將於8月3日起,延長為寶田邨來往新葵芳花園,途經:和田邨、NOVO LAND、紫田村、欣田邨、富泰邨、嶺南大學、彩暉花園、景峰花園、華都花園、愉景新城、荃錦中心、福來邨、葵俊苑、新葵興花園、葵芳邨、新都會廣場;並加密班次及新增由兆康苑開往新葵芳花園的短途特別班次,走線跟原有67M相同。 同日起,路線67A(寶田邨<>葵翠邨)取消服務,受影響乘客請改搭路線67M(寶田邨<>新葵芳花園)。 詳情請參閱上圖。 #屯門區 #荃灣區 #葵青區
#城巴 循環線797將於8月2日起,縮短為日出康城來往啟德,途經:峻瀅、清水灣半島、偉業街、海濱道、MegaBox、啟德天璽·天、德朗邨、盛緻苑、宏緻苑。 另外,797特別班次(日出康城經怡明邨、至善街、唐賢街、調景嶺站、健明邨往新蒲崗爵祿街)服務維持不變。 詳情請參閱上圖。 #將軍澳區
#城巴 特快路線796p(將軍澳天晉<>尖沙咀康達徑)將於8月2日起,延長服務時間。 詳情請參閱上圖。 #將軍澳區 #油尖旺區
巴士路線11k(竹園邨<>紅磡國際都會置富都會)將於8月1日起,加密星期六下午時段往竹園邨方向班次。 詳情請參閱上圖。 #黃大仙區 #九龍城區
循環線83k(黃泥頭村/石門邨<>沙田新城巿廣場)於7月27日起,調整少部分班次。詳情請參閱上圖。 乘客亦可改搭特快路線83s(黃泥頭村<>沙田新城巿廣場)。 #沙田區
🟡🔵15:30 更新 #城巴 宣佈,服務安排如下, ✅城巴日間路線今日已大致恢復正常服務。 ⚠️個別路線因為路面情況等因素正實施臨時安排。顧客如要查詢各路線服務安排,請透過城巴流動應用程式及網頁輸入巴士路線查詢。
🟠🔴18:00 更新 #九巴 及 #龍運巴士 宣佈,轄下路線服務安排如下, ✅九巴及龍運巴士大部分日間路線已陸續恢復,部分路線或因路面狀況需改道行駛,詳情請參閱九巴網頁或www.kmb.hk及智能手機應用程式APP1933。 ⚠️因應迪欣湖暫停開放,龍運路線R8、R33將改道不經迪欣湖。 ⛔️以下路線是日將暫停服務: 33R、74R、91R、92(特快班次)、92R、96R、99R、275R、289R、960p、HK1、HK2,及所有「寵物巴士團」。
Showing the 12 most recent of 19 posts we hold for @busnohkmtr. 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 — 31,829 of 1,350,102entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Named by 3 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“戒搭港鐵” (@busnohkmtr), 3,152 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/busnohkmtr.
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.