Channel
@freedomcab_hk
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
735subscribers
-14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001481722715 |
|---|---|
| Type | Channel |
| Username | @freedomcab_hk |
| Created | 23 August 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/freedomcab_hk |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 17:37 | 735 | -5 |
| 12 Sept 2026, 00:57 | 740 | -2 |
| 4 Sept 2026, 12:15 | 742 | -1 |
| 28 Aug 2026, 18:59 | 743 | -1 |
| 21 Aug 2026, 13:35 | 744 | -1 |
| 13 Aug 2026, 12:05 | 745 | -4 |
| 6 Aug 2026, 16:03 | 749 | no change |
| 6 Aug 2026, 10:45 | 749 | first reading |
20 posts held, back to 20 February 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 20 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.
自由的 的士平台 pinned «【自由的 🚕 call 車 pin】 ➡️想搭自由號 🚕？ 請 copy「Call 車格式」，填妥資料按出發點交俾相關當值Admin 👤 🚕 即時 order (可於大約 15 - 30分鐘前落 Order) 當值admin : @cook2cook 📆 預約order (只接受翌日或之後)：@cook2cook 📲 Call 左車請留意 TG message ⭕️ 全部按錶收費 🚦 過海需要收回程隧道費 ❌ 不接受 Secret Chat ☎️ 預約 order 必須留聯絡電話及TG username…»
日期 (dd/mm)：06/08 時間 (24小時制)： 人數： 出發點 (地區＋街名/地標)： 中途站 (地區＋街名/地標)： 目的地 (地區＋街名/地標)： 使用隧道： 特別要求：
【自由的 🚕 call 車 pin】 ➡️想搭自由號 🚕？ 請 copy「Call 車格式」，填妥資料按出發點交俾相關當值Admin 👤 🚕 即時 order (可於大約 15 - 30分鐘前落 Order) 當值admin : @cook2cook 📆 預約order (只接受翌日或之後)：@cook2cook 📲 Call 左車請留意 TG message ⭕️ 全部按錶收費 🚦 過海需要收回程隧道費 ❌ 不接受 Secret Chat ☎️ 預約 order 必須留聯絡電話及TG username (@xxx) 📆 翌日預約 order 將於每日 15:00 及 21:00 安排，請屇時留意TG message Call 車 🚕 格式
【自由的 🚕 call 車 pin】 ➡️想搭自由號 🚕？ 請 copy「Call 車格式」，填妥資料按出發點交俾相關當值Admin 👤 🚕 即時 order (可於大約 15 - 30分鐘前落 Order) （唔好意思，暫時沒有義務admin當值） 📆 預約order (只接受翌日或之後)：@never2slow 📲 Call 左車請留意 TG message ⭕️ 全部按錶收費 🚦 過海需要收回程隧道費 ❌ 不接受 Secret Chat ☎️ 預約 order 必須留聯絡電話及TG username (@xxx) 📆 翌日預約 order 將於每日 15:00 及 21:00 安排，請屇時留意TG message Call 車 🚕 格式
自由的 的士平台 pinned Deleted message
自由的 的士平台 pinned Deleted message
自由的 的士平台 pinned Deleted message
自由的 的士平台 pinned Deleted message
自由的 的士平台 pinned Deleted message
自由的 的士平台 pinned Deleted message
自由的 的士平台 pinned Deleted message
自由的 的士平台 pinned Deleted message
Showing the 12 most recent of 20 posts we hold for @freedomcab_hk. 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 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“自由的 的士平台” (@freedomcab_hk), 735 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/freedomcab_hk.
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.