Channel
@fengyinzhualongjin
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
2,090subscribers
+331 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003862411264 |
|---|---|
| Type | Channel |
| Username | @fengyinzhualongjin |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/fengyinzhualongjin |
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 73% 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 |
|---|---|---|
| 27 Sept 2026, 14:39 | 2,090 | -428 |
| 18 Sept 2026, 13:38 | 2,518 | +580 |
| 14 Sept 2026, 08:17 | 1,938 | +27 |
| 11 Sept 2026, 00:41 | 1,911 | +6 |
| 6 Sept 2026, 10:35 | 1,905 | +17 |
| 2 Sept 2026, 11:23 | 1,888 | +13 |
| 30 Aug 2026, 07:13 | 1,875 | -1 |
| 27 Aug 2026, 05:16 | 1,876 | -247 |
| 24 Aug 2026, 02:28 | 2,123 | +79 |
| 20 Aug 2026, 06:34 | 2,044 | +185 |
| 17 Aug 2026, 12:06 | 1,859 | +63 |
| 14 Aug 2026, 04:15 | 1,796 | +40 |
| 10 Aug 2026, 17:45 | 1,756 | -10 |
| 7 Aug 2026, 08:30 | 1,766 | +7 |
| 6 Aug 2026, 20:17 | 1,759 | first reading |
9 posts held, back to 6 August 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
💖南山玉桂狗嫩妹半裸丝足抓龙筋 #南山 #丝足 #SM #抓龙筋 #嫩妹 #半裸 深圳独家05后高颜值嫩妹抓龙筋 适合足控 颜值控 兼顾颜值和手法 本人照片 假一赔十 手法专业 前列腺高潮比开大更舒服😍 高潮时间更久😳 1.半裸调情/全身推油 二选一 2.三角区专业抓龙筋 3.丝足足疗调情 4.双手丝足高潮释放 ✅A套餐 598 70分钟 ✅B套餐 798 90分钟 ✅C套餐 998 120分钟 南山预约 @szyggblpm 频道 @szyggpd 聊天抽奖福利群 @szklmgp qq:1591914964
艺名 : 小雨 地区：#龙华 #清湖 标签：御 六九 波推 丝袜制服 水中萧 毒龙 水中萧 消费：600P 1000PP 联系：@xiaoyu9688 频道：@xiaoyu6997
艺名 : 可可（环保） 地区：#宝安 #坪洲 标签: 六九 御姐 漫游 六九 环保95 冷白皮 消费：500/45分钟P 900/90分钟PP 联系：@Keke885996 频道：@aKeke885996
艺名：梦婷抓龙筋 地区：#宝安 标签：御 抓龙筋 肾脏保养 全身spa 制服诱惑全果口 凤吟认证按摩手法大师服务一流 消费：499 699 800 联系：@lcllclllll 双向联系: @lcllclllllbot 频道；@lcllcllllll
艺名：小雅 地区：#龙岗 #中心城 标签：嫩 蛇吻 三点粉 丝袜制服 冷白皮 白小纯 视频已验证 消费：1000p 1800pp 联系：@futianxy 频道；https://t.me/hutianxiaoya
🎉 深圳凤吟修车茶馆 📝 抽奖说明：龙岗坂田-漫怡老师的1p半价福利优惠 中奖联系 @ouioex 点击下方链接可一键关注抽奖 @fyzzzgk ✅ 参与条件： 1. 加入 深圳凤吟修车茶馆 2. 加入 深圳凤吟修车娱乐资源 3. 加入 深圳凤吟中转站 4. 加入 深圳凤吟修车茶馆备用榜单3 5. 加入 漫怡个人朋友圈🎀 6. 加入 免费抽奖导航 🎁 奖品内容： • 龙岗坂田-漫怡老师的1p半价优惠券 × 1 ⏰ 开奖时间：2026-08-10 20:00 👇 点击下方按钮参与抽奖
艺名：芯芯 地区：#南山 标签： 嫩 六九 蛇 波推 喷水 视频已验证 消费: 800p 1500pp 联系：@xinxin1419 频道：@xinxin1418
听风晓月SPA馆 🌺专业手法，极致体验。私密的空间，让哥哥们尽情释放性欲野性 😍性感胸滑臀推、海底捞月、波涛汹涌、蚂蚁上树、高山流水、日式调情、猴子偷桃、鼻吸指滑 💦手、足、胸无限释放、深度抓龙筋+前列腺高潮/龟责榨精 🫣柔式SPA，更有神秘道具加持，无限变装及丝袜，满足哥哥的小癖好哦 💥听觉、触觉、嗅觉感官全面提升，让互动更深入、出水更彻底 项目A：浅层放松，唤醒感官 699/60min 项目B：深层修复，释放渴求 899/80min 项目C：身心合一，巅峰体验 1099/100min 标签：#福田 #抓龙筋 #泰式抓龙筋 #精油SPA #丝足 #道具 #剧情 #cos 关注频道：https://t.me/tingfengSPA TG联系：@yefeng0918 双向联系：@tfxybot QQ联系：2894775064
艺名：灿灿 地区：#龙岗 #中心城 标签： 嫩 六九 蛇 深猴 外出 视频已验证 消费: 700p 1300pp 联系：@cancan566 频道：@cancan3464
Showing the 9 most recent of 9 posts we hold for @fengyinzhualongjin. 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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳凤吟修车茶馆备用榜单3” (@fengyinzhualongjin), 2,090 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/fengyinzhualongjin.
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.