Channel
@guichengzhualongjin
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,292subscribers
+85 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004419969536 |
|---|---|
| Type | Channel |
| Username | @guichengzhualongjin |
| Created | Between 1 June 2026 and 10 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/guichengzhualongjin |
Other / unclassifiable — 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 66% 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 |
|---|---|---|
| 25 Sept 2026, 19:22 | 2,292 | +8 |
| 15 Sept 2026, 00:39 | 2,284 | +4 |
| 11 Sept 2026, 10:37 | 2,280 | -3 |
| 6 Sept 2026, 10:59 | 2,283 | +10 |
| 1 Sept 2026, 19:19 | 2,273 | +4 |
| 30 Aug 2026, 05:38 | 2,269 | -1 |
| 27 Aug 2026, 10:57 | 2,270 | +2 |
| 24 Aug 2026, 16:56 | 2,268 | +11 |
| 21 Aug 2026, 05:12 | 2,257 | +7 |
| 18 Aug 2026, 13:23 | 2,250 | -252 |
| 15 Aug 2026, 17:56 | 2,502 | +280 |
| 12 Aug 2026, 16:53 | 2,222 | +15 |
| 12 Aug 2026, 09:45 | 2,207 | no change |
| 12 Aug 2026, 09:32 | 2,207 | first reading |
19 posts held, back to 10 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 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 19 posts for this entry, the most recent from 12 August 2026. An engagement rate over an empty window would be a number about nothing.
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 2 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 2 reactions 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 10 July 2026 to 12 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.
🎉 桂城 小莫抓龙筋的半价优惠 📝 抽奖说明：半价免定，中奖者主动联系老师 @gcxmzlj ，不得转手转卖，兑奖必须写报告，中奖后五天内有效。 ✅ 参与条件： 1. 加入 佛山桂城 小莫 专业抓龙筋 2. 加入 广州凤吟修车茶馆 3. 加入 广州凤吟修车茶馆备用群 4. 加入 广州凤吟修车娱乐资源 5. 加入 广州凤吟修车娱乐资源私密1 6. 加入 免费抽奖导航 🎁 奖品内容： • 套餐一半价券 × 1 ⏰ 开奖时间：2026-08-16 20:00 👇 点击下方按钮参与抽奖
来自老客户的神仙评价😂😂
今天，立秋。 风里有了一丝不易察觉的凉意，但地表的湿热还未散去。 中医说："秋收冬藏"，秋天是身体开始向内收拢能量的时候。 而你，准备好了吗？ 带着一整个夏天的透支、积劳、湿热，就这样迎接秋天——那些没有清理干净的疲惫，会在秋冬的干燥与寒凉中，变得更加难以疏解。 立秋这一天，三伏还剩最后5天。 这是今年最后一次，在阳气托举下完成深度清仓的机会。 九品护理·古法抓龙筋，在立秋的节点，为您做最后一次温柔而坚定的"送别"—— 送走骨盆深处积压一夏的湿寒与瘀滞， 送走那些因久坐高压而打结的经络， 送走那个总是强撑着、从不被温柔对待的自己。 当身体在这个秋天的入口处重新变得轻盈， 你会发现，秋天不只是收获季节， 更是一个终于可以真实地陪伴、真实地感受、真实地去爱的季节。 立秋之后，是秋天。秋天之前，还有5天。 九品护理，等您来完成这场告别。 #桂城抓龙筋 #佛山抓龙筋
前列腺，男人的"生命线" 真正的男人，可以倒在前线，决不能倒在前列腺上！ 高发人群： 久坐一族、长期驾车、憋尿习惯、经常饮酒应酬 常见症状： 尿频尿急、腰骶酸胀、精力涣散、睡眠变浅、晨起疲惫 九品护理·古法抓龙筋 专注骨盆深层物理疏通，无药物，直达核心 末伏最后7天，今年最后机会 📍 佛山桂城德高信 · 一对一私密预约 📞 #桂城抓龙筋 #佛山抓龙筋
抓龙筋🐉男士专属私密保养，调理肾气，疏通堵塞，缓解疲劳，重拾年轻状态。
正宗泰国抓龙筋🐉 前列腺高潮开发 男士潮喷开发
微信号qqaa8755 可以添加这个微信
末伏开始了。 很多男人在夏天会莫名感到——腰酸加重、夜尿次数增多、久坐后骶骨酸胀难忍。 这不是偶然，也不是单纯的"累"，而是前列腺在整个夏季的持续充血与积压，终于在末伏天集中爆发的信号。 三伏天高温让骨盆腔血流加速，却也让前列腺持续处于"充血-压迫-充血"的恶性循环。若此时不加以干预，带着这些积弊进入秋冬，调理的成本将成倍增加。 末伏，是在这一切固化之前，最后一次深度清仓的机会。 九品护理·古法抓龙筋，以正统泰医手法直达骨盆核心： 🔹 精准松解腺体周围筋膜，释放慢性积压 🔹 激活盆腔微循环，将滞留的湿热废物彻底代谢 🔹 借末伏余阳，将下半年的健康基底打扎实 秋天来了，要收。 伏天结束前，先把该清的清干净。 末伏9天，今年最后的黄金窗口。 九品护理，为您完成这最重要的一次"季末清仓"。 #桂城抓龙筋 #佛山抓龙筋
八点后才有位置啦！！！
中伏已过三分之一。 这段时间，很多男性反映一个共同的感受：明明没做什么，却总觉得腰酸、乏力、睡不深。 这不是普通的疲惫，而是前列腺在伏天高压下，向你发出的一个清晰信号。 为什么伏天前列腺问题更容易爆发？ 夏季湿热蒸腾，人体代谢加速，但骨盆腔的微循环却因久坐而严重滞后——腺体局部充血、温度升高、分泌物积聚，这正是前列腺炎、前列腺增生等问题在夏季高发的根本原因。 与此同时，伏天的高温会让人倾向于久坐空调房、减少活动，这恰恰加重了盆腔底部的"死水"状态。 九品护理·古法抓龙筋，专注于这一区域的物理干预： 🔹 精准作用于腺体周围的筋膜网络，释放慢性压迫 🔹 激活盆腔微循环，改善腺体局部充血状态 🔹 松解骨盆底肌，从根本上恢复自主神经平衡 做完之后，你会注意到：夜尿减少了，腰不那么沉了，睡眠也深了。 这不是巧合，这是身体在通透之后，给你最诚实的回馈。 中伏是窗口，前列腺不等人。 趁经络大开的时节，认真疏通一次，抵得上平时…
❤2
感谢支持
三伏已至，佛山的湿热几乎令人窒息。 中医讲，暑湿困体，最易损耗男性的阳气与生机。而那个首当其冲、却最少被关注的部位，正是骨盆腔深处的前列腺。 久坐的高管、长期驾车的商人、每日伏案的精英——这些人的前列腺，正在以一种沉默的方式承受着： 🔸 湿热内蕴：夏季代谢紊乱加剧腺体充血，尿频、尿不尽的症状明显上升 🔸 气血瘀滞：长时间保持同一姿势，骨盆腔微循环严重受阻 🔸 神经慢性压迫：骨盆底肌持续紧张，直接影响睡眠深度与情绪稳定 九品护理·古法抓龙筋，是一次对抗夏季透支的物理干预。 通过正统泰医 Nuat Karsai 手法，我们精准作用于腺体周围的经络网络——疏通盆腔微循环，松解底肌压迫，激活身体深处的自愈机制。做完之后，你最先感受到的往往是：睡得沉了，身体轻了，那种无名的倦怠感也悄然散去。 入伏之后，身体的账不能再拖了。 趁三伏天阳气最盛，深度疏通一次，让夏天成为身体复原的起点，而非透支的终点。 九品护理，为您在盛夏之中，…
Showing the 12 most recent of 19 posts we hold for @guichengzhualongjin. 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 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.
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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“🐉佛山小莫 专业泰式抓龙筋🐉” (@guichengzhualongjin), 2,292 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/guichengzhualongjin.
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.