Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_7089868724

Channel
武汉认证资源
@cph996
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
33,718subscribers
-2,169 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001564549341 |
|---|---|
| Type | Channel |
| Username | @cph996 |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 26 October 2026 |
| Measurements held | 45 |
| Confirmed unchanged | 1 time, most recently 26 October 2026 |
| On Telegram | t.me/cph996 |
Topic
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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 |
|---|---|---|
| 26 Oct 2026, 07:06 | 33,718 | -72 |
| 25 Oct 2026, 10:40 | 33,790 | +10 |
| 24 Oct 2026, 08:04 | 33,780 | -157 |
| 23 Oct 2026, 08:59 | 33,937 | -23 |
| 22 Oct 2026, 07:00 | 33,960 | -112 |
| 21 Oct 2026, 03:48 | 34,072 | -112 |
| 20 Oct 2026, 03:41 | 34,184 | -64 |
| 19 Oct 2026, 02:46 | 34,248 | -97 |
| 18 Oct 2026, 01:39 | 34,345 | -46 |
| 17 Oct 2026, 02:36 | 34,391 | -188 |
| 16 Oct 2026, 00:06 | 34,579 | -63 |
| 15 Oct 2026, 03:16 | 34,642 | -208 |
| 13 Oct 2026, 21:36 | 34,850 | -67 |
| 10 Oct 2026, 09:55 | 34,917 | -381 |
| 6 Oct 2026, 06:57 | 35,298 | -319 |
| 1 Oct 2026, 06:41 | 35,617 | -944 |
| 18 Sept 2026, 11:41 | 36,561 | -107 |
| 16 Sept 2026, 04:40 | 36,668 | -176 |
| 14 Sept 2026, 13:40 | 36,844 | -225 |
| 13 Sept 2026, 03:16 | 37,069 | first reading |
Engagement
47 posts held, back to 31 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 136 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 6.15%
- avg views ÷ 33,718 subscribers
- Avg views / post
- 2,070
- 17 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 17
- of 47 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 25 October 2026 |
|---|---|
| Posts held | 47 (31 July 2026 – 25 October 2026) |
| Views total | 35,262 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 26 Oct 2026, 01:28 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.
What this channel posts
- Video runtime
- 2m 11s
- Average length
- 11s
Measured directly from 12 videos 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.
Reaction mix
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 1 | 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 1 of the 47 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 47 most recent posts we hold, published 31 July 2026 to 25 October 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
圈界NO.1 🟡昵称:咸鱼 🕐地区:#武昌 🤖双向:@xianyu5201_bot 🚀电报:@xianyu5201 🔔频道: 点击浏览频道👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】你的轮廓线条柔美流畅,没有生硬尖锐的棱角,柔和的五官,带给人内心抚慰,看着就让人觉得很舒服。 🔰#点击下方查看详情⬇️
🩷❤️🧡武汉美女王SM私人影院💛💚🩵 带你体验女王的调教与白月光初恋般的温柔 初恋般的温柔系列 A套餐🌟🌟🌟 可亲脸可伸进去摸🐻🐻🐻 可感受小姐姐的体温和香味👙 时间(60分钟 ) B套餐推荐🌟🌟🌟🌟 剧情演绎或cos系列 二选一 和小姐姐深度接触开放热情 包含换装 撕丝袜 🐍吻或者隔摸🦐二选一(60分钟 ) C 特色套餐推荐🔥🔥🔥🔥 剧情演绎或cos系列 二选一 指定换装 撕丝袜 和小姐姐更加深度接触 西施拍豆腐:🐻揉脸 西施喂豆腐:喂你吃舔🐻 西施的私语:耳边呻吟 🐍吻/摸🦐/手出💦 三选二 时间60分钟 D 定制特色套餐👙👙👙👙 顶顶顶👍 🉑零距离接触 最后都不会让哥哥难受 想要具体了解请到店详询 女S女王的调焦系列(此项目定制仅接受预约) 剧情实例(可提前沟通定制): 老师与学生/老板与下属/护士与病人/嫂子/美女邻居 SM1套餐(轻度可定制)👠👠👠 舔脚爱好者的福音(恋足)玉足深喉 丝袜美腿诱惑调教…
预约价格420拍照评价立减20 武汉小悠带队 服务大升级 大升级服务 环境升级 全场00后00年~06顶美全新佳丽 骚的一批活好 联系客服安排顶美小姐姐 门店价格:420 到店跟前台说小悠预约可享买单价格400(需拍照点评反馈) 双飞特价仅需:750元 门店营业时间 12:00~04:00 稳定在岗10~20多位佳丽全场00后 持4T服务证上岗🕵️♀️ 气质御姐,风韵小嫂子,小母狗,小巧萝莉,邻家小妹,A4,大奶牛,水娃💦,黑丝吊带高跟鞋👠,好玩不贵,透明消费😀 😀服务流程如下📱 👩🎤 沐浴洗澡 小按开场 指滑鼻吸 👩🎤 胸滑全身 滚水漫游 纯舌漫游 👩🎤 胯下毒龙 海底捞月 莞式干磨 👩🎤 飞龙在天 百变调情 肾保健操 👩🎤 一柱擎天 激情互动 4T 齐上 👩🎤 各种姿势 完美释放 临别温存 门店新出特惠全场400 50分钟不限次数 多次需提前告知 环境优雅私密,每个房间都很大,带有单独淋浴,不办卡不充足…
#杰克外围 武汉高端外围 全国大圈可安排 妹子多多,每天更新,等你来挑 👉武汉外围频道: 频道点击浏览👀 🎙杰克外围频道群: 点击浏览👀 👉预约联系 客服 @jieke312 👉双向私信机器人 @jiekepjbot
😃武汉最大的门店海选SPA顶级服务莞式服务一条龙权威认证嫩妹全裸全裸9️⃣🔠任盘舔逼😡👅 🤕全裸9️⃣🤩SPA全场嫩妹任盘 🤯服务天花板、韵味少妇、服务大师、大胸导师 异域风情应有尽有、绝对的高质量高颜值嫩妹 预约客服:@AsJ9907 双向:@GTE9988bot 微信1️⃣:AaJ8807 微信2️⃣:ys888868688 QQ1️⃣:3174753612 QQ2️⃣:2623356744 预约电话☎️:18807143592 交流群: 点击这里预览👀 技师频道:点击这里预览👀 技师点评:点击这里预览👀 😀原价:4️⃣9️⃣8️⃣ 😀活动价:3️⃣8️⃣0️⃣ 😀服务时间60分钟 出勤10➕ 😵双飞特价➕3️⃣0️⃣0️⃣一龙二凤 😀环境高档招待领导 朋友聚会不二选择。房间带淋浴,私密性拉满 😀没有T路 无任何隐形消费 🔰武汉光谷全裸9️⃣🔠嫩妹会所🔰 😀😀😀😀😀😀😀😀😀 🧩胸推🧩臀推🧩腿推🧩丝足🧩腿夹🧩 推荐🥰毛推🛡逼推…
圈界NO.1 🟡昵称:小燕子 🕐地区:#洪山区,光谷五路 🤖双向:@ananping118bot 🚀电报:@anping0811 🔔频道: 点击浏览频道👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】 你的笑颜胜过漫山遍野的春色,让人心生欢喜。 🔰#点击下方查看详情⬇️
莞式十八式00后全裸嫩妹会所 榨精 #武昌#徐东#小北#94#4T#养生SPA 🤪😜项目介绍:全裸嫩妹推油榨精 【全场一口价400】拍照点评优惠20 十指弹琴😼比翼双飞😼柔情似水 高山流水😼丝足诱惑😼贴身抚摸 舔奶吸奶😼⑥⑨舔逼😼猴子偷桃 胸推臀推😼粉鲍可摸😼奸式胸推 波推全身😼舌尖环游😼可摸可亲 💥正宗莞式十八招💥花式毒龙 出水:手推:腿推:胸推:腿夹:丝足:(不限次出水) 丝袜诱惑 情趣诱惑 骚逼诱惑 AV剧情 御姐 人妻 少妇 嫩妹 AV骚逼 龟责 高跟 SM 女仆 老师 JK 空姐 护士 顶级推荐(臀交榨精)😍 📱📱📱📱📱📱📱📱 😵😐小北电话:17307181095 😵📱小北微信:ok7894T 😵😵 小北QQ: 2402356717 😵😵 小北电报群:点击这预览👀 😵😵 小北频道点评:点击这预览👀 😵😵 小北电报私信:点击这预览👀 😵😵 小北双向机器人:@Linb123bot …
🟡昵称: 莉娅女王 🕐地区:#汉阳区 🤖双向:@as1566z12345bot 🚀电报:@as1566z12345 🔔频道: 频道点击浏览👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】 你的身姿婉约如诗,一步一景,步步生莲。 🔰#点击下方查看详情⬇️
圈界NO.1 🟡昵称:安琪拉 🕐地区:#武昌 徐东 🤖双向:@bao8855_bot 🚀电报:@bao888555 🔔频道: 点击浏览频道👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】 你身上那份不慌不忙的从容,和你的容貌相辅相成,外在赏心悦目,气度优雅大方,实在令人心生赞叹。 🔰#点击下方查看详情⬇️
🔰武汉市硚口首家全裸🔰9T➕❓ 武汉市硚口区首家全裸9T全场:398 (评价拍照反馈享受优惠只需398)🎉 🔰武汉硚口区全裸🔰9T➕❓ 🏅金牌客服:@HZ88007 🏅加入技师频道:点击这里预览👀 🏅加入群组: 点击这里预览👀 🏅加入点评:点击这里预览👀 双向机器人🤖: @NB5887bot 电话预约☎️: 18162349983 微信1️⃣预约:Z555L222H000 QQ1️⃣预约:2019210854 微信2️⃣:W888Z999Y888 QQ 2️⃣:2980228817 硚口首家全场高颜值 主打00后嫩妹 服务时间60分钟时间内不限次数 营业时间: 12:00-4:00嫩妹 联系客服可安排隐藏服务 隐藏服务 武汉全裸最大的门店海选SPA顶级服务莞式服务一条龙权威认证嫩妹活好 兄弟们标配服务是主打00后全裸60分钟不限水 全场398亲嘴 69 舌吻 店铺服务: 鸳鸯浴 胸推 腿推 臀推 逼推 阴推 毛推 脖推 …
【全区95 98莞式全套海选会所】🌸私人定制spa私密会所 😇 海选 😇 油压 😇 莞式 😇 全套 😇 花式 🟢会所介绍 :海选模式 莞式服务, 环境豪华私密安全, 给您至尊享受的高端体验,可依您的喜好和需求为您做专属的私人项目定制。 更多剧本等你来解锁 主题房,制定角色,制定服装,满足你的所有幻想莞式36式 , 🛁皇帝共浴,💆菲式按摩,💪莞式抓龙, 👙制服诱惑, 👯♀️ 双人系列, ⛓️SM, 🍆情趣道具, ㊙️情景互动 全裸艳舞 😃 鸳鸯戏水😄 水磨推拿😄 口舌调情 😄 后口毒龙 😀胯下吞龙 😃手推胸推😄 足推臀推 😊 激情爱爱 😄 制服情趣😀 到店海选 😄【冰火双重天】😃 等三十多种项目。💒 🔥服务流程:皇帝共浴🛁指滑🫳🏻鼻息🗓舌尖漫游🥂-ab面骑士-💋柔式按摩放松-❤️花式调情雄起📞-水漫金山-🎯漫水吹箫💖-深情直入🥂🍀深喉😒69+ 🌹舔耳😒鸳鸯浴 玫瑰浴 ☘️…
Showing the 12 most recent of 47 posts we hold for @cph996. 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
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.
@AAJJ99880 · 17,0403 posts极搜🔍资源搜索@JISOU
@jisou2 · 2,102,4673 posts武汉同城精选🏠
@xiajiawuhanwaiwei1 · 2,4433 posts咸鱼🐟
@xianyu52111 · 5283 posts武汉休闲
@You29812 · 1,2963 posts武汉同城精选验证群🏠
@zswedx2 · 23,5513 posts武汉光谷技师频道
@AAJJ9988 · 5,2512 posts武汉会所点评
@AJJ899 · 4,7482 posts全国莞式全套会所
@bao5558888 · 52 posts琳琳(洪山区光谷)
@cccddd25889 · 3,7402 posts武汉#斑马小镇摄影师点评频道
@LinB6789 · 1,1472 posts武汉八戒技师自拍馆
@NBB8887 · 1,6262 posts武汉顶美点评
@NBN8899 · 6,0452 posts武汉莉娅女王福利群
@s123m789 · 9492 posts武汉 养生 4T会所 技师榜
@whgg55555 · 12,0062 posts武汉精品皖式养生SPA会所
@wuhanvipchuyi · 7,0662 posts鄂A斑马小镇(武汉口嗨)
@XTXT8889 · 5,8062 posts武汉闲聊休闲(禁止广告)
@You29815 · 7,9072 posts橙子🍊家
@bao52122 · 8931 post楠枳闺房
@gfhv568 · 4771 post95 98莞式海选会所
@jq98hs · 6,1541 post武昌晴晴频道
@khhsjkak · 3041 post武汉顶美交流会所群
@NBAG988 · 7,0541 post武汉悦影私影mmk
@yueying188 · 4751 post
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 2
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@cph996 named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 1 post, 26 August 2026 – 26 August 2026 · confirmed gone 7 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 26 August 2026 – 26 August 2026 · confirmed gone 8 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 26 October 2026 — this entry's latest reading, not the date you are reading this.
“武汉认证资源” (@cph996), 33,718 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/cph996.
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.