Channel
@shgrxcb689
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
5,124subscribers
-270 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002781532664 |
|---|---|
| Type | Channel |
| Username | @shgrxcb689 |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/shgrxcb689 |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 16 Sept 2026, 23:38 | 5,124 | -19 |
| 13 Sept 2026, 04:36 | 5,143 | -35 |
| 9 Sept 2026, 10:02 | 5,178 | -57 |
| 3 Sept 2026, 21:38 | 5,235 | -7 |
| 31 Aug 2026, 08:44 | 5,242 | -18 |
| 27 Aug 2026, 22:48 | 5,260 | -16 |
| 25 Aug 2026, 04:14 | 5,276 | -16 |
| 22 Aug 2026, 00:25 | 5,292 | -20 |
| 18 Aug 2026, 12:23 | 5,312 | -29 |
| 15 Aug 2026, 01:53 | 5,341 | -27 |
| 11 Aug 2026, 08:27 | 5,368 | -25 |
| 8 Aug 2026, 01:14 | 5,393 | -1 |
| 7 Aug 2026, 18:32 | 5,394 | first reading |
19 posts held, back to 24 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 6 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 19 posts for this entry, the most recent from 10 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.
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 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 1 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 24 July 2026 to 10 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-10 【老师】：沐言 @muyan2003 【留名】：匿名 【评价】：👍 好评 【人照】：10 【颜值】：10 【身材】：10 【服务】：8 【态度】：8 【环境】：9 【综合】：9.17 【过程】：昨天刚去完其他老师感觉意犹未尽，今天在群里找老师看到沐言老师还不错，问了问离我家不远就约了晚上8点过去，本来还以为假照，看到老师那一刻觉得确实可以，感觉比照片好看，个子很高，穿了黑色裙子，大概23左右的样子，随即交钱洗澡，老师确实不是服务系，也感觉是刚干这行没多久，但口的时候也是很认真，然后女上抓着老师的胸，胸不大不小，女上一会后老师有点累，但我因为昨天刚去最近状态不太好，居然软了下来，但老师还是比较配合的又让硬起来，随后后入123结束战斗。 总体来说看身材，颜值来说7张还可以，如果增加服务后相当有性价比了！
Photo, posted without a caption
【出击时间】：8月9日 【我的花名】：诗妍 【出击留名】：艾伦 【联系诗妍】：@shiyan69 【修车水费】：400 【服务内容】:全裸69 真毒龙 胸推 阴推 回萧 爆嘴了 【凶器罩杯】：感觉比D还大 【总体描述】：在老师群里潜水一段时间了，趁着今天有空出击！遥控上楼见了真人，就知道这一趟没来错，颜值方面：跟照片八九成像，频道照片有参考的价值，臀部丰满，胸部尺寸超级大，稍微有一点肉，但是不胖，胸这么大微微有点肉我觉得才是正常的，出击过程：老师先给我洗澡，洗完后交的水费，擦干后上床开始B面过水，不得不说老师的舌头是非常的灵活，舔的那叫一个爽，然后俩大灯在我身上柔一个遍，又来个背部口罐，紧接着毒龙，真毒龙确定很顶了，反叼一会，老师让我站在床上老师跪着给我口半天，视觉冲击力太强了，一会儿老师又让我躺着然后又亲眯咪，我两手摸着老师的奶子，我手这么大居然握不住，尴尬了，哈哈哈😂胸舔的如同电流穿过一样酥麻，随后开始口，老师绝对是我见过口…
❤1
【时间】：2026-08-09 【老师】：昕月 【留名】：张根硕（我chovy,给我来点骚的啊） 【人照】：10 【颜值】：8 【身材】：8 【服务】：10 【态度】：10 【环境】：10 【综合】：9.33 【过程】：省流版:这是一个好评，老师是服务系少妇，吃服务的可以无脑冲。 详细版:课室环境很好，老师是瘦瘦小小的一直，人照基本没差，课表上的服务一个不落全做了，技术也很好约的pp顺利全被老师榨出来，不管是口活还是夹鸡术都很强，毒龙也舒服。老师说话温声细语软软糯糯，初见是觉得有些腼腆，开始服务后又骚又活泼，情绪价值给的也很足。。 最最重要的一点，pp的话服务是做满两套的ab面那些全部都是两遍，这个确实是十分的罕见了，毕竟绝大部分都是默认一遍服务。所以喜欢服务系和情绪价值的可以无脑冲。
【时间】：2026-08-08 【老师】：沐言 【联系方式】：@muyan2003 【留名】：anthropic 【人照】：10 【颜值】：9 【身材】：9 【服务】：8 【态度】：9 【环境】：9 【综合】：9 【过程】：她人比较腼腆，在嫩妹和御姐之间，进门以后看到就知道来对了，人照没有什么差别，属于走在路上会多看一眼的那种，高挑，比较会化妆，身材比较好，没有赘肉，修长的身体，进门以后洗澡，洗完以后到了床上，脱完以后更惊艳了，没有那种俗套的纹身，是那种红色的线条感的那种看着还挺好看的那种，她皮肤很好，白，偏白的那种，比较光滑，摸起来比较舒服，奶子大概b➕或者c-，握住刚刚好，不同于很多嫩妹的那种还不如不化的妆，她的妆容恰到好处，自然，清新，靓丽，美。略作缠绵，她舔舐我的胸，咬住奶头，看到她的样子，有一些娇羞，有一些妩媚，比较动人，她边做，我边和她聊天，时间差不多了带上套给我口，没有齿感，没有敷衍，算是口的比较好的，矫好的面容，…
✅郑州开心修车群： @zhengzhou1658 ✅郑州开心修车榜： @gongkaibang663 ✅本群个人老师在线： @zhzhgr ✅本群在线商户 : @hsspkmzh 上榜请联系: @conggeguanli
【时间】：2026-08-06 【老师】：知念 【留名】：匿名 【人照】：8 【颜值】：8 【身材】：9 【服务】：10 【态度】：10 【环境】：10 【综合】：9 【过程】：下班无事刷到了老师的狼友分享，想体验下服务是不是真的这么好，老师遥控上楼后，老师身型均匀，小梁家碧玉，穿着小裙子👗，眼睛会说话很有神，南方人说话也很温柔，一进门給我拿娃哈哈水，很主动的帮我脱衣服，轻轻的舔一下，我的胸很温柔地说有点咸，有点小调皮帮忙洗澡，边洗还帮口下，很舒服。到床上正式服务开始，从a面舔到b面，S P A柔式，后背口杀加毒龙反叼，跪起来舔更爽，提示一下，这个环节小心被秒，这个流程下来很迫不及待大干，女上九显一深．．．全程自动，很舒服确实是专业的，喜欢服务的一定要体验下，从放松的角度来看，比单纯做爱有意思的多，做完上班的疲惫一扫而空，
【出击时间】：8.3 【妹子花名】：甜甜 【联系方式】 ：@yybb111 【修车水费】： 800 【颜值身材】：9 【凶器罩杯】：d 又大又嫩又挺，手感好 【服务内容】：课表都有 【总体评分】：10 【总体优点】：老师不但人漂亮还很嫩，胸大服务好，口活好， 【综合评述】：昨天预约，今天下班直接出发，小区安全性高，在老师指挥下进去。开门看到老师，惊为天人，人照10分，老师不怎么会拍，看到本人比照片颜值还要高。房间干净卫生，洗个澡，躺床上。老师漏出两个大雷子，晃的我两眼冒精光，二弟瞬间起立，在老师的口中和两个大雷子双重夹击下，差点缴械，戴上雨衣，第一在老师的上位下缴械了，人中只有强中手，很快败下阵来！强烈建议二刷，三刷！
【时间】：2026-08-02 【老师】：温妮 【留名】：闹钟你别闹3.0 【评价】：👍 好评 【人照】：9.0 【颜值】：8.5 【身材】：8.0 【服务】：8.0 【态度】：9.0 【环境】：7.5 【综合】：8.33 【过程】：跟老师约好时间，随出发过去，老师的地方有点偏，在小区里比较安全。到地方后老师在电梯口迎接。人照一致，除去美白效果基本没差。到达教室之后，看到教室有点乱，聊了一会天，然后洗澡，老师洗过了所以没有助浴。出来后看到老师换好了情趣衣服，老师属于bbw身材，正常肤色，有点微胖。乳头有点偏黑，下面毛有点旺盛。然后大蟒蛇，舌吻管够。随后老师开始服务，口的很认真，次次深喉，差点起飞，然后让老师停止，带上小雨伞开始正题，先是传教士，进入以后感觉水真是有点多。舌吻着然后下面进行着。然后换后入，老师的屁股是真的大，而且老师还会夹，搞了个我措不及防，在老师一声声不要停，快给我中顺利出水。随后事后一支烟，聊了一会天以后吻别离…
【出击时间】：7.30号 【妹子花名】：九妖妖 【联系方式】： @wwbb911 【修车水费】：800 【胸围】: c 【颜值相似度】: 9 【服务内容】: 毒龙反刁 69互舔 360°旋转吹箫 【出击体验】：昨晚准时赴约，九妖妖真人比照片还骚，颜值9分绝对保真，皮肤白嫩水滑，身材火辣，C杯挺翘手感极佳，一上来就主动贴上来舌吻，骚劲十足。 服务细节： • 毒龙：技术顶级，舌头又软又灵活，360°无死角舔得我腿软，边舔边用手指辅助，爽到头皮发麻。 • 69互舔：她特别主动，下面又粉又紧，味道干净，边舔边浪叫，互舔过程中她直接高潮了一次，汁水超多。 • 360°旋转吹箫：这才是重头戏！深喉一流，舌头缠绕+旋转+吸吮三连击，节奏掌控完美，边吹边用眼睛勾人，差点当场缴械。技术娴熟到像练过，持续时间长，最后吞完还舔干净，服务态度满分。 全程主动热情，不磨蹭，不推拒，氛围拉满。800块这个价位性价比爆棚，绝对是近期出击最爽的一次…
【时间】：2026-07-20 【老师】：晴子 【留名】：卡其S 【人照】：9 【颜值】：9 【身材】：9 【服务】：9 【态度】：9 【环境】：9 【综合】：9 【过程】：今天群里突然看见心意的老师，果断换卷出击，开到地方，看见人照不差，各方面都可以，交了水费就洗澡，本来想玩点花的，奈何老师刚入行，懂的不多，吹了会，就开始我表演，各种亲，浑身亲了一遍，然后老师开始求我插入，进入小穴，有股热热的暖意，然后疯狂插入，各种姿势，最后在老师呻吟中出货，累的我2天鸡鸡不能战斗，最后洗洗澡，回家，非常不错的路程，值得推荐，
【评价等级】: 10 【日 期】: 7月25日 【验 证 人】: 王 【美女昵称】: @xiawanwan715 【地 区】: 二七区 【人照得分】: 9 【年 龄】:22 【颜值得分】: 9 【身材得分】:9 【服务得分】: 10 【态度得分】: 10 【环境得分】: 10 【综合得分】: 9.5 【凶 器】: C+ 【推荐指数】:10 【服务过程】: 这次出击很愉快，身材好 奶子大，摸起来手感不错，让我意外的是这个妹妹下面掰开居然是粉的，哈哈 服务这块也很巴适，陪洗很温柔，口技也不错，最让我满意的是我不想动了，她会自己骑上来动。她在上位的时候看那两个大奶子一跳一跳的，真的爽。而且妹妹很听话基本我怎么说她怎么做，拍拍屁股就知道换姿势。这个妹妹是我近期出击比较满意的一个，感觉很爽。
Showing the 12 most recent of 19 posts we hold for @shgrxcb689. 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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“郑州开心群车评报告” (@shgrxcb689), 5,124 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/shgrxcb689.
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.