Channel
@SZHKFriends_lbpd
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,877subscribers
+14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002195589889 |
|---|---|
| Type | Channel |
| Username | @SZHKFriends_lbpd |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/SZHKFriends_lbpd |
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 16 September 2026 and assigned it the closest of 31 fixed categories, at 53% 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 |
|---|---|---|
| 18 Sept 2026, 01:21 | 1,877 | -7 |
| 14 Sept 2026, 05:57 | 1,884 | +6 |
| 10 Sept 2026, 06:41 | 1,878 | +4 |
| 5 Sept 2026, 01:39 | 1,874 | +1 |
| 1 Sept 2026, 18:54 | 1,873 | -2 |
| 26 Aug 2026, 10:38 | 1,875 | +5 |
| 23 Aug 2026, 21:14 | 1,870 | +3 |
| 20 Aug 2026, 02:36 | 1,867 | +2 |
| 17 Aug 2026, 13:15 | 1,865 | +2 |
| 7 Aug 2026, 13:23 | 1,863 | no change |
| 7 Aug 2026, 11:02 | 1,863 | first reading |
9 posts held, back to 29 May 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 9 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
10 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 70.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 7 | 70.0% | |
| 😱 | 2 | 20.0% | |
| 👻 | 1 | 10.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 4 of the 9 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 10 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 29 May 2026 to 4 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.
深圳香港老友会 [ 出击雷报 ] 工兵留名： 蓝胖子 踩雷时间：2026-08-03 老师昵称：# kk 地市坐标：#深圳 # 上课花费：800 颜值身材： 8分像 踩雷详情：上课，未退 （是否上课 是否退费 ） 踩雷吐槽：出击提前到半小时，然后楼下等到过了我约的时间才弄好让我上去，进门啥话也不说等着给💰。以下是和代聊反馈的内容： 不针对个人，仅说交易，你们真的有点问题，进门女孩摆个死鱼脸，一直就是哦，那怎么，哦。然后我给你发消息，你这边没回我说先做，她说等一下，然后坐那里搞手机。完事5.45左右给我说她约了别人要给我退钱让我走。在这之前我就说了我是请假过来的，可以先做，等你回消息，到这里她说这个点约了别人，我提前半小时到的，上去洗完澡给我说约的别人让我走，我火大正常吧，我原本是说服务好加个p，这个也是和你说好的但是你删记录死无对证了，然后你们说没得加了，这个我也没追究。然后过程中一点声音没有，一插就说疼，我又不大，一做就…
因之前的号被盗，明天开始实行特惠一周半价！从7月13号到7月19号！ 大家可以关注下我的频道 @wanghefeiqaz123 ，或者直接联系我 @fei02Z ，预约。 注：✌不在半价范围内，仅这一周有效，有缘的哥哥门欢迎来约！！！
深圳香港老友会 [ 出击雷报 ] 工兵留名： #探雷先锋 踩雷时间：2024-07-07 老师昵称：#芊芊 地市坐标：#深圳 #宝安 上课花费：无 颜值身材： 与 踩雷详情: 没有上课 （是否上课 是否退费 ） 踩雷吐槽: 罚站35分钟 明明知道约了 8:30 说是出去吃饭了， 解释不通。 明显中介排课没有排好 态度不行 或者是 故意发优惠券引流 性质恶劣。 老师电报: @qianqian6690 ( https://t.me/SZHKFriends_lbpd ) （提交报告需要提供相关资料，如聊天记录，付款记录等，记录不会公开）
深圳香港老友会 [ 出击雷报 ] 工兵留名： #id843832575* 踩雷时间：2024-07-07 老师昵称：#晗晗 地市坐标：#深圳 #南山 上课花费：无 颜值身材： 踩雷详情： （是否上课 是否退费 ） 踩雷吐槽：是本人身高没176，撑死168-170，真人比照片黑 老师电报： @hanhansz ( https://t.me/SZHKFriends_lbpd ) （提交报告需要提供相关资料，如聊天记录，付款记录等，记录不会公开）
深圳香港老友会 [ 出击雷报 ] 工兵留名： 逆天 踩雷时间：2024-07-07 老师昵称：@mmkeke100 可可妙妙屋 地市坐标：#深圳 # 上课花费：3000 颜值身材： 沒看到人 踩雷详情：經 t.me/+nB1g7CZ6nutlYzdh 這個平台約女女，但要先付款，付完款要求退款，還想繼續騙錢，說什麼保證金，當然沒有付款 （是否上课 是否退费 ） 踩雷吐槽：第一次出來玩被騙子 老师电报： ( https://t.me/SZHKFriends_lbpd ) （提交报告需要提供相关资料，如聊天记录，付款记录等，记录不会公开）
龙华 依依 @yiyia113 #网图 #盗用tiktok图片+视频 再次声明，有没有投诉，有没有雷报，和用网图恶意引流两回事。 1.对学生而言，网图就是欺骗，除非提前告知。 有些素质好的学生就是一次又一次的被这种网图消磨殆尽，甚至玩一次电报就不玩了。有些是来都来了所有想着算了。 2.对其他老师而言，你用网图把学生骗过去，不仅没人去用本人照片的老师，而且还导致一些新人老师都没人敢去。 ⚠️凡是老友会上榜老师使用网图(除非提前说明)，一经举报或者查出，曝光一个月。 学生如果遇到这种情况提前 截图聊天，拍下老师房间号 或者手机录音，留下证据。 拒绝网图 拒绝代打。
❤5
福田 韵茜 @yunxi101000 id8464143241 频道: t.me/+rIRLp_a69ugxMjM1 低素质中介 + ai验证 + 网图 + 辱骂管理员
😱2❤1👻1
曝光一个中介，每天2份假报告 ，过份了。 @mnjjjvv
南山 安宁 @anning0530 ai验证+网图 中介威胁。 ai验证+网图 不要来老友会上榜， 一经发现，严肃处理，备注 ai验证+网图 曝光一个月。
❤1
Showing the 9 most recent of 9 posts we hold for @SZHKFriends_lbpd. 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.
Named by 2 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳香港老友会雷报频道” (@SZHKFriends_lbpd), 1,877 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/SZHKFriends_lbpd.
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.