在 Telegram 里找内容,先打开 SOSO 搜搜。 频道、群组、帖子、贴纸都可以搜;也可以从发现页继续浏览。

Channel
香港楼凤
@HKguifei
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
14,898subscribers
-471 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001197087022 |
|---|---|
| Type | Channel |
| Username | @HKguifei |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 33 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/HKguifei |
Topic
Adult — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 |
|---|---|---|
| 19 Sept 2026, 08:01 | 14,898 | -20 |
| 16 Sept 2026, 20:41 | 14,918 | -7 |
| 14 Sept 2026, 21:37 | 14,925 | -20 |
| 13 Sept 2026, 06:21 | 14,945 | -24 |
| 11 Sept 2026, 05:56 | 14,969 | -33 |
| 8 Sept 2026, 12:35 | 15,002 | -32 |
| 5 Sept 2026, 05:57 | 15,034 | -10 |
| 3 Sept 2026, 10:59 | 15,044 | -6 |
| 2 Sept 2026, 08:14 | 15,050 | -21 |
| 1 Sept 2026, 10:05 | 15,071 | -22 |
| 31 Aug 2026, 07:48 | 15,093 | -17 |
| 30 Aug 2026, 07:24 | 15,110 | -10 |
| 29 Aug 2026, 05:13 | 15,120 | +1 |
| 28 Aug 2026, 04:08 | 15,119 | -1 |
| 27 Aug 2026, 07:15 | 15,120 | -14 |
| 26 Aug 2026, 09:24 | 15,134 | -4 |
| 25 Aug 2026, 05:54 | 15,138 | -11 |
| 24 Aug 2026, 05:05 | 15,149 | -21 |
| 22 Aug 2026, 09:53 | 15,170 | -7 |
| 20 Aug 2026, 20:46 | 15,177 | first reading |
Engagement
32 posts held, back to 29 June 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 51 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 2.02%
- avg views ÷ 14,898 subscribers
- Avg views / post
- 302
- 3 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 3
- of 32 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.
| Window | Rolling 30 days · latest post in window 31 August 2026 |
|---|---|
| Posts held | 32 (29 June 2026 – 31 August 2026) |
| Views total | 905 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:58 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
12 reactions across 9 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 12 | 100.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 11 of the 32 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 32 most recent posts we hold, published 29 June 2026 to 31 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
#频道互推 #相似推荐 ------------------------------ 📢 95/96 服务 SPA 会所|深圳全城门店 📢 重庆品茶 📢 上海艳遇 📢 武汉寻花 📢 杭州马家 📢 武汉青莲楼 📢 深圳98楼凤修车探花选妃 📢 同城约炮.学生少妇 📢 海口优选 📢 大连-靓妹 ------------------------------ ☁️ 互推入口:@sosoo
#频道互推 #相似推荐 ------------------------------ 📢 广州万花 📢 天津百花榜 📢 深圳本地 SPA 会所|95/96 专属服务 高端臻选 📢 西安逍遥宫 📢 广州 深圳 东莞 佛山 选妃总汇 📢 郑州少妇圈 📢 深圳会所95优质店 在线频道 📢 汕头女园 📢 泉州鲜花 📢 台州红楼 ------------------------------ ☁️ 互推入口:@sooo
#频道互推 #相似推荐 ------------------------------ 📢 95/96 服务 SPA 会所|深圳全城门店 📢 重庆品茶 📢 上海艳遇 📢 武汉寻花 📢 杭州马家 📢 武汉青莲楼 📢 深圳98楼凤修车探花选妃 📢 同城约炮.学生少妇 📢 成都娱乐商务KTV 📢 郑州外围💎郑州约炮💎郑州上门💎郑州修车 ------------------------------ ☁️ 互推入口:@sooo
SOSO 搜搜 把 Telegram 搜索和发现放在一个入口。 想继续找频道、群组、帖子或贴纸,直接输入关键词。 也可以从发现页继续浏览同类入口。
#频道互推 #相似推荐 ------------------------------ 📢 广州万花 📢 天津百花榜 📢 深圳本地 SPA 会所|95/96 专属服务 高端臻选 📢 西安逍遥宫 📢 广州 深圳 东莞 佛山 选妃总汇 📢 郑州少妇圈 📢 深圳会所95优质店 在线频道 📢 汕头女园 📢 郑州学生会 📢 大理古城选美 ------------------------------ ☁️ 互推入口:@sooo
#频道互推 #相似推荐 ------------------------------ 📢 95/96 服务 SPA 会所|深圳全城门店 📢 重庆品茶 📢 上海艳遇 📢 武汉寻花 📢 杭州马家 📢 武汉青莲楼 📢 深圳98楼凤修车探花选妃 📢 同城约炮.学生少妇 📢 东莞外围💎东莞约炮💎东莞上门💎东莞修车 📢 熟女乱伦/人妻少妇约炮 ------------------------------ ☁️ 互推入口:@sooo
新群变化快,手动找很容易漏。 SOSO 会展示最近同步的新群入口,适合快速补充新的群组来源。
❤1
#频道互推 #相似推荐 ------------------------------ 📢 广州万花 📢 天津百花榜 📢 深圳本地 SPA 会所|95/96 专属服务 高端臻选 📢 西安逍遥宫 📢 广州 深圳 东莞 佛山 选妃总汇 📢 郑州少妇圈 📢 深圳会所95优质店 在线频道 📢 汕头女园 📢 银时cos 学妹 jk兼职线下约会 资料反馈 📢 涿州约约 ------------------------------ ☁️ 互推入口:@sooo
#频道互推 #相似推荐 ------------------------------ 📢 95/96 服务 SPA 会所|深圳全城门店 📢 重庆品茶 📢 上海艳遇 📢 武汉寻花 📢 杭州马家 📢 武汉青莲楼 📢 深圳98楼凤修车探花选妃 📢 同城约炮.学生少妇 📢 中山 中山外围🔥中山上门🔥 极品后宫 📢 烟台艳遇 ------------------------------ ☁️ 互推入口:@sooo
频道适合看内容,群组更适合继续交流。 SOSO 可以直接找热门群组,也能按关键词搜同类圈子。 先打开看看当前推荐。
❤1
#频道互推 #相似推荐 ------------------------------ 📢 广州万花 📢 天津百花榜 📢 深圳本地 SPA 会所|95/96 专属服务 高端臻选 📢 西安逍遥宫 📢 郑州少妇圈 📢 广州 深圳 东莞 佛山 选妃总汇 📢 深圳会所95优质店 在线频道 📢 汕头女园 📢 =♡成都修车真实评价[报告墙] 📢 🥇台灣玲子賴wrq1014外送茶叫小姐上門服務 ------------------------------ ☁️ 互推入口:@sooo
Showing the 12 most recent of 32 posts we hold for @HKguifei. 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.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“香港楼凤” (@HKguifei), 14,898 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/HKguifei.
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.