15 Jan 2026, 04:59 UTC≈2,420 viewsread 12 August 2026
Am selling unlimited Textnow Talkatone Google voice Textplus Textme Textplus
Channel
元朗牛哨兵
@yuenlongox
On this record: Growth · Engagement · Posts · Citations · Cite this entry
9,055subscribers
-28 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001180159553 |
|---|---|
| Type | Channel |
| Username | @yuenlongox |
| Created | 4 October 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/yuenlongox |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 23:23 | 9,055 | -12 |
| 10 Aug 2026, 06:31 | 9,067 | -13 |
| 6 Aug 2026, 22:23 | 9,080 | -3 |
| 6 Aug 2026, 06:45 | 9,083 | no change |
| 6 Aug 2026, 06:37 | 9,083 | first reading |
Engagement
15 posts held, back to 28 January 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 14 pagesof 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 15 posts for this entry, the most recent from 15 January 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
15 Jan 2026, 04:56 UTC≈2,430 viewsread 12 August 2026
Am selling unlimited Textnow Talkatone Google voice Textplus Textme Textplus
19 Nov 2024, 03:47 UTC≈8,410 viewsread 12 August 2026
Forwarded from @thewitnesshkPhoto
47人案 判刑結果
13 Sept 2024, 13:54 UTC≈9,790 viewsread 12 August 2026
Forwarded from @busnohkmtrPhoto
#九巴 宣佈，以下 #元朗 、 #天水圍 路線於9月17日（中秋節），提早下午班次服務時間： 69c（觀塘碼頭 往 天恩邨） 268A（觀塘碼頭 特快往 朗屏邨） 268p（觀塘碼頭 特快往 朗屏8號） 269p（葵芳邨 往 濕地公園路） 269s（觀塘碼頭 特快往 天水圍栢慧豪園） 276c（祥華邨＜＞天水圍站） 968x（鰂魚涌英皇道 特快往 元朗德業街） 詳情請參閱上圖。 #元朗區
3 Sept 2024, 00:36 UTC≈5,860 viewsread 12 August 2026
Forwarded from @ncetransport
✅08:31 更新 較早前長青隧道，往屯門方向管道內的緊急工程已經完成，全線解封，交通恢復正常。 #路面情況
3 Sept 2024, 00:15 UTC≈5,450 viewsread 12 August 2026
Forwarded from @HK_Traffic_News
長青隧道緊急維修：往機場方向的全線現已封閉，長青隧道往九龍方向現已實施單管雙程行車措施，往機場方向龍尾：青葵公路近葵涌公園；往九龍方向龍尾：青朗公路近汀九橋。 2024-09-03 HKT 07:50
18 Jul 2024, 06:17 UTC≈6,200 viewsread 12 August 2026
Forwarded from @busnohkmtr
‼️14:07 #水邊圍 輕鐵站發生事故，港鐵輕鐵綫列車服務嚴重受阻。 乘客請改搭其他交通工具： 巴士路線69（元朗德業街＜＞天水圍栢慧豪園），途經：尚豪庭、元朗大橋村、朗屏邨、元朗廣場、水邊圍邨、朗屏路鳳池村、濕地公園路、香港濕地公園、天逸邨、天澤邨、天富苑、天恩邨、天悅邨、天頌苑
18 May 2024, 02:11 UTC≈6,530 viewsread 12 August 2026
Forwarded from @busnohkmtr
‼️10:05 更新 #鍾屋村 輕鐵站有列車出軌，鍾屋村站附近輕鐵服務停駛，乘客請改搭其他交通工具。 輕鐵綫610、614、615、751不停藍地站至洪水橋站。港鐵現安排免費接駁巴士，行走來往洪天路緊急月台至兆康。
17 May 2024, 11:13 UTC≈5,890 viewsread 12 August 2026
https://t.me/busnohkmtr/3802
7 May 2024, 14:16 UTC≈4,170 viewsread 12 August 2026
5月7日 元朗攸田東路天橋、鳳群街、元龍街一帶 清單車
18 Mar 2024, 12:03 UTC≈5,410 viewsread 12 August 2026
3月19日 YOHO天橋+鳳攸北街一帶 清單車
13 Mar 2024, 10:53 UTC≈5,340 viewsread 12 August 2026
Forwarded from @busnohkmtrPhoto
巴士循環線54（元朗擊壤路＜＞上村）將於3月17日起，調整星期日及公眾假期班次，星期一至六班次維持不變。 詳情請參閱上圖。 #元朗區
Showing the 12 most recent of 15 posts we hold for @yuenlongox. 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
Citation-graph rank — 1,028,549 of 1,345,403entries 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.
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
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“元朗牛哨兵” (@yuenlongox), 9,055 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/yuenlongox.
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.