🟡昵称:#小涵 🕐地区:#番禺 🤖双向: 🚀电报:@pyxh8 🔴水费:📤课表查看图📤 #禁收车费定金和没见人就给课费
❤1

Channel
@shhjh2677
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
30,359subscribers
-3,727 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001472829966 |
|---|---|
| Type | Channel |
| Username | @shhjh2677 |
| Description | 【修车老总】 @ca6688bot 【修车频道】 https://t.me/shhjh2677 【修车老群】https://t.me/gffddgffgf 【全国修车】 @langtianxia 【公用防雷】https://t.me/bikan888 |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 17 November 2026 |
| Measurements held | 61 |
| Confirmed unchanged | 1 time, most recently 17 November 2026 |
| On Telegram | t.me/shhjh2677 |
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 65% 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 1 other registered channel. 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 |
|---|---|---|---|
| @cuivd/116928 Aug 2026, 04:43 UTC | @shhjh2677/1784 · this entry28 Aug 2026, 04:44 UTC | 1.00 | under a minute |
| @cuivd/12117 Sept 2026, 06:10 UTC | @shhjh2677/1798 · this entry7 Sept 2026, 06:10 UTC | 1.00 | under a minute |
| @cuivd/12219 Sept 2026, 15:12 UTC | @shhjh2677/1801 · this entry9 Sept 2026, 15:12 UTC | 1.00 | under a minute |
| @cuivd/124517 Sept 2026, 14:51 UTC | @shhjh2677/1821 · this entry17 Sept 2026, 14:51 UTC | 1.00 | under a minute |
| @cuivd/128126 Sept 2026, 14:23 UTC | @shhjh2677/1865 · this entry26 Sept 2026, 14:23 UTC | 1.00 | under a minute |
| @cuivd/132911 Oct 2026, 15:10 UTC | @shhjh2677/1891 · this entry11 Oct 2026, 15:10 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @cuivd | 12 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @cuivd (12–0) |
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. 12 of the 12 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 44 comparable posts for this entry, running 22 July 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 @cuivd. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, 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 |
|---|---|---|
| 17 Nov 2026, 03:07 | 30,359 | -687 |
| 13 Nov 2026, 22:46 | 31,046 | +690 |
| 11 Nov 2026, 03:21 | 30,356 | +505 |
| 9 Nov 2026, 12:37 | 29,851 | +936 |
| 8 Nov 2026, 05:50 | 28,915 | -375 |
| 6 Nov 2026, 21:20 | 29,290 | -146 |
| 5 Nov 2026, 22:48 | 29,436 | -60 |
| 4 Nov 2026, 19:51 | 29,496 | -69 |
| 3 Nov 2026, 17:20 | 29,565 | -24 |
| 2 Nov 2026, 20:17 | 29,589 | +199 |
| 1 Nov 2026, 21:22 | 29,390 | +200 |
| 31 Oct 2026, 23:41 | 29,190 | -40 |
| 31 Oct 2026, 02:39 | 29,230 | -538 |
| 30 Oct 2026, 03:58 | 29,768 | -543 |
| 29 Oct 2026, 01:09 | 30,311 | -304 |
| 27 Oct 2026, 20:37 | 30,615 | -154 |
| 26 Oct 2026, 22:29 | 30,769 | -283 |
| 25 Oct 2026, 20:27 | 31,052 | -110 |
| 24 Oct 2026, 22:46 | 31,162 | -48 |
| 23 Oct 2026, 23:56 | 31,210 | first reading |
59 posts held, back to 22 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 189 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 5 of 16 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 59 (22 July 2026 – 16 November 2026) |
| Views total | 32,795 |
| Reactions total | 4 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 12:57 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 17 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 19 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.
20 reactions across 18 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 20 | 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 24 of the 59 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 20 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 59 most recent posts we hold, published 22 July 2026 to 16 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 16 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).
🟡昵称:#小涵 🕐地区:#番禺 🤖双向: 🚀电报:@pyxh8 🔴水费:📤课表查看图📤 #禁收车费定金和没见人就给课费
❤1
【广州全区95 98莞式全套海选会所】🌸私人定制spa私密会所 【全区95 98莞式全套海选会所】🌸私人定制spa私密会所 😇 海选 😇 油压 😇 莞式 😇 全套 😇 花式 🟢会所介绍 :海选模式 莞式服务, 环境豪华私密安全, 给您至尊享受的高端体验,可依您的喜好和需求为您做专属的私人项目定制。 更多剧本等你来解锁 主题房,制定角色,制定服装,满足你的所有幻想莞式36式 , 🛁皇帝共浴,💆菲式按摩,💪莞式抓龙, 👙制服诱惑, 👯♀️ 双人系列, ⛓️SM, 🍆情趣道具, ㊙️情景互动 全裸艳舞 😃 鸳鸯戏水😄 水磨推拿😄 口舌调情 😄 后口毒龙 😀胯下吞龙 😃手推胸推😄 足推臀推 😊 激情爱爱 😄 制服情趣😀 到店海选 😄【冰火双重天】😃 等三十多种项目。💒 🔥服务流程:皇帝共浴🛁指滑🫳🏻鼻息🗓舌尖漫游🥂-ab面骑士-💋柔式按摩放松-❤️花式调情雄起📞-水漫金山-🎯漫…
🎁更多抽奖: https://t.me/cuivd 🎟️ 抽奖标题:#花店老板娘 📪抽奖说明:中奖者机器人会发送中奖信息 中奖截图🚀私聊: @huals88 🎫 参与条件: 🎫 加入-广州04年花店老板娘38D🌹 🎫 加入-广州认证资源 🎫 加入-广州后宫佳丽 🎁 奖品内容: 💰️ 口令红包10 × 1 💰️ 包夜优惠500 × 8 💰️ 两次优惠300 × 10 💰️ 一次优惠200 × 10 📅 开奖时间:2026-11-11 12:00自动开奖 👉 参与抽奖链接: https://t.me/cj888999bot?start=join-L179414235668
🟡昵称:#妍妍 🕐地区:#天河 🤖双向:@Yy757991bot 🚀电报:@Yanyan8873 🔴水费:📤课表查看图📤 #禁收车费定金和没见人就给课费
全国林妹高端外围【大⭕️圈】 #定金预约 本群已担保 💎专注各市区修车 🈶洋马,空姐,少妇,萝莉, 学妹 御姐等高素质高颜值🉑上门 🈶教室 ✡️奢华的环境、全套服务、至尊享受、帝王体验 没有玩过大圈的建议先点下方频道查看规则 ♏️双向客服林妹: @wai998bot ♒️总频道: 频道点击浏览👀 #本群推荐信誉客服 24小时接待联系即可
抽奖老板娘福利上车(编号L179334472120)已成功开奖: 创建人:茶总 { 唯一 管理}[62302294] 已参与人数:1004 中奖名单如下: dud*[18731847**](奖品为两次优惠300) 顾全大*[57298546**](奖品为一次优惠200) 迁*[60575358**](奖品为包夜优惠500) 桃花依旧笑春*[62179532**](奖品为两次优惠300) 赤色要塞魂斗*[66615051**](奖品为包夜优惠500) 此地*[67436874**](奖品为两次优惠300) 麦乐鸡*[68612382**](奖品为两次优惠300) 柳叶*[69581389**](奖品为包夜优惠500) 怕热也怕*[71056085**](奖品为两次优惠300) 梦似烟花心似*[72405421**](奖品为两次优惠300) 永远有多*[72735965**](奖品为一次优惠200) 得梦为*[76126826**]…
❤1
艺名:BBW蜜桃🍑女神 已经视频认证 地区:#天河区 联系方式 :@mitao822 双向:@mitao332_bot 课表频道 :@mitao220 课费 :800p 1400pp #🉑上门 👑标签:#BBW 鸳鸯浴 #69 #水中箫 #毒龙 #舌吻 #无套口 #丝袜 #胸推# 剧本杀 #东京浴 🔰【格语 】 垂眸阅读的时刻,周身岁月静好,眉眼柔和安静,专注沉静的模样,赋予了你一种沉静温婉的独特美感。 🔴标签 #已验证上榜
❤1
最近有骗子冒充 骗老师 想盗号 大家注意上面图片是骗子, 下面是我唯一的号 唯一双向号 @ca6688bot 唯一TG号 @ca8866 @baccaratapp #如果有他人联系让你续费都是冒充,有人说你账号有问题都是盗号的,请注意骗子
🎁更多抽奖: https://t.me/cuivd 🎟️ 抽奖标题:老板娘福利上车 📪抽奖说明:中奖者机器人会发送中奖信息 中奖截图联系 @huals88 🎫 参与条件: 🎫 加入-广州认证资源 🎫 加入-广州后宫佳丽 🎫 加入-广州04年花店老板娘38D🌹 🎁 奖品内容: 💰️ 口令红包10 × 1 💰️ 包夜优惠500 × 8 💰️ 两次优惠300 × 8 💰️ 一次优惠200 × 8 📅 开奖时间:2026-11-02 13:00自动开奖 👉 参与抽奖链接: https://t.me/cj888999bot?start=join-L179334472120
🟡昵称: 花都🌺自聊瑶瑶🌸 🕐地区:#花都 🤖双向:@wcm7795bot 🚀电报:@twm2026508 🔴水费:📤课表查看图📤 🔴标签 #可放心出击 #已验证 #车费定金狼友自己随意不超过100 最近有人冒充管理,欺骗老师收¥, 找管理可看群公告或点击下方底部按钮。
圈界NO.1 🟡昵称:媚儿 🕐地区:#白云区 🤖双向: 🚀电报:@aa0806y 🔔频道: 点击浏览频道👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】 你的高贵不在于衣着,而在于那份由内而外散发的修养。 🔰#点击下方查看详情⬇️
😦位置: #广州 #天河区 📱艺名:#花店老板娘 📣标签:#已认证 💸课费:800/P-1500/PP 🚀私聊: @huals88 🙂频道: 频道点击浏览👀 机器人:@qimeng22_bot 报告:@hjdu19 资料: 年龄22 身高172 体重55KG 🐻38D 🎀标签: #口爆 #69 #亲吻 #观音坐莲 #水中潇 #鸳鸯浴 #臂推 #🐻推 #深喉 #SM调教 #舔蛋 #无套口 #丝袜高跟 😄😄😄😄😀😃😄😄😆
Showing the 12 most recent of 59 posts we hold for @shhjh2677. 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.
We recorded 12 posts on @shhjh2677 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.
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.
@shhjh2677 named 1 handle 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.
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.
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 17 November 2026 — this entry's latest reading, not the date you are reading this.
“广州认证资源” (@shhjh2677), 30,359 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/shhjh2677.
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.