信息标题:长沙风骚大波妹少妇 所属地区:湖南长沙 小姐年龄:27 小姐颜值:8 单次价格:500p,800pp 服务项目:鸳鸯浴、胸推、漫游、丝袜制服高跟、360度口活、毒🐉、爱爱 QQ:3454951366 微信:nizi520jj 与你号:abc8182 频道TG: 频道点击浏览👀 私信 @mmliu88880000 地址:芙蓉区 🔴标签 #已验证上榜
❤1

Channel
@cscyh88
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
30,432subscribers
-7,149 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001310026370 |
|---|---|
| Type | Channel |
| Username | @cscyh88 |
| Description | 【修车老总】 @hxr88899bot 【修车频道】 https://t.me/cscyh88 【修车老群】https://t.me/cyh8899 【全国修车】 @langtianxia 【公用防雷】https://t.me/bikan888 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 61 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/cscyh88 |
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 74% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @jipin16/81620 Aug 2026, 15:49 UTC | @cscyh88/1712 · this entry21 Aug 2026, 04:49 UTC | 1.00 | 13 hours |
| @cscyh88/1745 · this entry5 Sept 2026, 09:30 UTC | @jipin16/8505 Sept 2026, 09:31 UTC | 1.00 | under a minute |
| @cscyh88/1750 · this entry7 Sept 2026, 04:19 UTC | @jipin16/8557 Sept 2026, 07:09 UTC | 1.00 | 2.8 hours |
| @cscyh88/1754 · this entry14 Sept 2026, 11:22 UTC | @jipin16/86614 Sept 2026, 11:23 UTC | 1.00 | under a minute |
| @jipin16/87015 Sept 2026, 08:16 UTC | @cscyh88/1761 · this entry21 Sept 2026, 04:56 UTC | 1.00 | 6 days |
| @cscyh88/1779 · this entry5 Oct 2026, 09:52 UTC | @jipin16/9025 Oct 2026, 09:59 UTC | 1.00 | 6 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @jipin16 | 8 (8/8 hand-verifiable sample passed) | 1.00 | 8 minutes | this entry (6–2) |
| @huis888 | 5 (5/5 hand-verifiable sample passed) | 0.99 | 3 minutes | this entry (4–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 2 of the 3 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 25 comparable posts for this entry, running 4 August 2026 to 12 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 3 channels, the one whose matching posts we hold earliest is @jipin16. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 13 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 00:07 | 30,432 | -103 |
| 11 Nov 2026, 09:36 | 30,535 | -5 |
| 9 Nov 2026, 12:46 | 30,540 | -80 |
| 8 Nov 2026, 07:07 | 30,620 | -141 |
| 6 Nov 2026, 22:29 | 30,761 | -86 |
| 6 Nov 2026, 00:10 | 30,847 | -25 |
| 4 Nov 2026, 21:50 | 30,872 | -24 |
| 4 Nov 2026, 00:16 | 30,896 | -14 |
| 3 Nov 2026, 02:56 | 30,910 | +45 |
| 1 Nov 2026, 23:29 | 30,865 | -50 |
| 31 Oct 2026, 22:58 | 30,915 | -56 |
| 30 Oct 2026, 21:01 | 30,971 | -68 |
| 29 Oct 2026, 21:16 | 31,039 | -79 |
| 28 Oct 2026, 22:17 | 31,118 | -61 |
| 27 Oct 2026, 21:57 | 31,179 | -4 |
| 26 Oct 2026, 21:58 | 31,183 | -79 |
| 25 Oct 2026, 22:21 | 31,262 | +6 |
| 24 Oct 2026, 19:47 | 31,256 | -90 |
| 23 Oct 2026, 19:40 | 31,346 | -33 |
| 22 Oct 2026, 22:37 | 31,379 | first reading |
43 posts held, back to 4 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 171 pages of Telegram’s post history, 20 posts per page.
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. It is computed over the 3 of 13 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 12 November 2026 |
|---|---|
| Posts held | 43 (4 August 2026 – 12 November 2026) |
| Views total | 32,121 |
| Reactions total | 5 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Nov 2026, 23: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.
Lifetime counters from Telegram’s own channel header, read 15 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 14 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.
13 reactions across 10 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 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 16 of the 43 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 43 most recent posts we hold, published 4 August 2026 to 12 November 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.
Telegram’s own ‘edited’ marker: 0 of 13 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
信息标题:长沙风骚大波妹少妇 所属地区:湖南长沙 小姐年龄:27 小姐颜值:8 单次价格:500p,800pp 服务项目:鸳鸯浴、胸推、漫游、丝袜制服高跟、360度口活、毒🐉、爱爱 QQ:3454951366 微信:nizi520jj 与你号:abc8182 频道TG: 频道点击浏览👀 私信 @mmliu88880000 地址:芙蓉区 🔴标签 #已验证上榜
❤1
🟡昵称:#哈哈 🕐地区:#岳麓区 🤖双向: 🚀电报:@wowo2500 🔴水费:📤课表查看图📤 #禁收车费定金和没见人就给课费
#长沙 /SPA /私影/94/95/98天花板 新增商K、私影、摸摸看、剧本SPA+94服务(监狱、学校、医院、婚礼)📌📌尊享🥰项目:全裸服务,体贴入怀,浪漫调情,舔蛋舔杆,特色毒龙,洗澡🛁、浪漫床前调情、柔式按摩、全身指划、全身👃尖👅尖漫游、后掏式调情、果冻毒龙、丝袜诱惑、🐍尖过蛋、肾保健、热油滚蛋;可😀胸出 😁臀出,腿夹👋夹,丝足诱惑 ❗️(摸摸看可海选❗️可舌吻❗️可出水❗️妹子全部20岁左右) ❗️(剧本SPA有监狱、老师、医院、结婚四种不同的情景房间可供选择,94全裸SPA➕剧情演绎) ❗️(KTV商k游戏场 真空 全程游戏、妹子酒水全包干 ) ❗️(95/98都是公寓 私信我给你发位置) ❗️(94油推客人和技师都全身淋油在油床上做服务 油不停 服务不停 体验感拉满 像av动作片一样刺激 欢迎各位老板预约 ) 长沙市:点击区域跳转👇👇 可心频道 预约客服:@kexinspa 频道:点击这里预览👀 预约微…
📱📱📱😀😀😀😀 长沙顶级娱乐推荐 🤪😘 费用 ⚡️⚡️⚡️起,项目介绍,服务以全裸为主 帝王享受💗花式口爆💗高山流水 新式臀推💗冰火两重💗温水回龙 ⑥⑨毒龙💗无套口爆💗射嘴里! 🤪🥳费用650p 950pp 服务介绍,质量高都是小妹子以质量为主 鸳鸯浴💗无套口💗 调情💗胸推💗 舌尖漫游💗高山流水💗 各种姿势pp #长沙各区#95#98 😜😝😜😜😀😀😀😀 在线客服 @cswY6 频道: 频道点击浏览👀 Q Q:3422809240 ⚠️92-94没报预约号一律按正规按摩处理 😁挑选佳丽:😁到店里去选,不 满意可以换,选到满意为止
长沙📱📱📱92/94/95/98,mmk,商k,外围等 100+家门店 · 与酒店合作全城覆盖 只要你需要 什么都能安排! 点击 导航:小雅客服 不论你在哪个区,随时沉浸氛围享受。 🔥 92特色项目 · 感官爆炸 🚿👅👃💰379 点击导航📱📱【项目流程】 💎 94全裸升级· 全面进化 🖤👅🍑💰409明星老师加30 以客服报价为准 点击导航📱📱【项目流程】 💎🥰94油推:客人和技师都全身淋油在油床上做服务 油不停 服务不停 体验感拉满 像av动作片一样刺激 欢迎各位老板预约 💎🥰新增加剧本SPA 剧本SPA 带场景 有监狱 教室 医院 新娘 价格实惠 欢迎老板预约 体验各种不一样的快乐✨✨ ✨ 独家流程 · 环环入魂 点击导航📱📱【项目流程】 (不同技师会在某些环节加重或延伸,可按需求灵活调整,保证每次体验都有惊喜 📱95口爆👄【预约价499】 点击导航📱📱【项目流程】 📱98全套啪啪啪 1p七百 2p1000 …
#株洲 最嗨的游戏荤场 妹妹可以厕所文化和外出吃夜宵 话不多说上现场才艺表演 各种特色荤玩法 #株洲荤场 #激情舞蹈👯♂️ #关灯环节 #集体互动 #主打00后 特色玩法 舌吻*舔乳头*360°旋转*沙发秀,脱内衣👙,两个奶子真空,想怎么玩怎么亲怎么舔都可以,基本上都是年轻小妹子00后,乳头都是粉嫩嫩的,玩起来特别舒服,适合几兄弟组局,也能自己单刷✅ 各种做爱动作互动,把你小弟弟摸硬,吃包子油条豆浆简直不要太爽了💯💯💯💯💯💯💯💯💯 微信/☎️ 19173355999 电报 @biao1917335599 频道链接:@biao191733
全国林妹高端外围【大⭕️圈】 #定金预约 本群已担保 💎专注各市区修车 🈶洋马,空姐,少妇,萝莉, 学妹 御姐等高素质高颜值🉑上门 🈶教室 ✡️奢华的环境、全套服务、至尊享受、帝王体验 没有玩过大圈的建议先点下方频道查看规则 ♏️双向客服林妹: @wai998bot ♒️总频道: 频道点击浏览👀 #本群推荐信誉客服 24小时接待联系即可
🟡昵称:#韩冰 🕐地区:#岳麓区 🤖双向:@hanmm77_bot 🚀电报:@hanmm66 🔴水费:📤课表查看图📤 #禁收车费定金和没见人就给课费
❤1
🟡昵称: 小悠悠 🕐地区:#雨花区 🤖双向:@Lele112bot 🚀电报:@youyou9899 🔴水费:📤课表查看图📤 🔴标签:#已验证 最近有人冒充管理,欺骗老师收¥, 找管理可看群公告或点击下方底部按钮。
🟡昵称:#小甜 🕐地区:#雨花区 🤖双向: @tiantain121_bot 🚀电报:@zayfwh_361 🔴水费:📤课表查看图📤 #禁收车费定金和没见人就给课费
【全区95 98莞式全套海选会所】🌸私人定制spa私密会所 😇 海选 😇 油压 😇 莞式 😇 全套 😇 花式 🟢会所介绍 :海选模式 莞式服务, 环境豪华私密安全, 给您至尊享受的高端体验,可依您的喜好和需求为您做专属的私人项目定制。 更多剧本等你来解锁 主题房,制定角色,制定服装,满足你的所有幻想莞式36式 , 🛁皇帝共浴,💆菲式按摩,💪莞式抓龙, 👙制服诱惑, 👯♀️ 双人系列, ⛓️SM, 🍆情趣道具, ㊙️情景互动 全裸艳舞 😃 鸳鸯戏水😄 水磨推拿😄 口舌调情 😄 后口毒龙 😀胯下吞龙 😃手推胸推😄 足推臀推 😊 激情爱爱 😄 制服情趣😀 到店海选 😄【冰火双重天】😃 等三十多种项目。💒 🔥服务流程:皇帝共浴🛁指滑🫳🏻鼻息🗓舌尖漫游🥂-ab面骑士-💋柔式按摩放松-❤️花式调情雄起📞-水漫金山-🎯漫水吹箫💖-深情直入🥂🍀深喉😒69+ 🌹舔耳😒鸳鸯浴 玫瑰浴 ☘️…
❤3
信息标题:长沙风骚大波妹少妇 所属地区:湖南长沙 小姐年龄:27 小姐颜值:8 单次价格:500p,800pp 服务项目:鸳鸯浴、胸推、漫游、丝袜制服高跟、360度口活、毒🐉、爱爱 QQ:3454951366 微信:nizi520jj 与你号:abc8182 频道TG: 频道点击浏览👀 私信 @mmliu88880000 地址:芙蓉区 🔴标签 #已验证上榜
Showing the 12 most recent of 43 posts we hold for @cscyh88. 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.
@cscyh88 edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 1 post on @cscyh88 as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“长沙品茶汇资源” (@cscyh88), 30,432 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/cscyh88.
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.