🟡昵称:小新 🕐地区:#萧山 🤖双向:@xiaoxin518888_bot 🚀电报:@xiaoxin518888 🔔🔔频道: 点击浏览频道👀 🔴标签 #已验证上榜 🔰【格语 】 淡淡的眉眼自带疏离清冷感,安安静静的时候,有种清冷高级的美,一旦展露笑容,又瞬间温暖了时光。
❤1

Channel
@jipin8855
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Cite this entry
29,118subscribers
-5,330 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002354813948 |
|---|---|
| Type | Channel |
| Username | @jipin8855 |
| Description | 【修车老总】 @xiaoji888bot 【修车频道】 https://t.me/jipin8855 【修车老群】https://t.me/MM25458 【全国修车】 @langtianxia 【公用防雷】https://t.me/bikan888 |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 60 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/jipin8855 |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 3 other registered channels. This entry also sits inside a group of 4 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 |
|---|---|---|---|
| @mumbai_tg/20659 Aug 2026, 13:15 UTC | @jipin8855/1319 · this entry9 Aug 2026, 13:15 UTC | 1.00 | under a minute |
| @mumbai_tg/208411 Aug 2026, 11:34 UTC | @jipin8855/1339 · this entry11 Aug 2026, 11:36 UTC | 1.00 | 72 seconds |
| @mumbai_tg/210514 Aug 2026, 13:11 UTC | @jipin8855/1361 · this entry14 Aug 2026, 13:11 UTC | 1.00 | under a minute |
| @mumbai_tg/211518 Aug 2026, 14:05 UTC | @jipin8855/1377 · this entry18 Aug 2026, 14:05 UTC | 1.00 | under a minute |
| @mumbai_tg/217328 Aug 2026, 13:00 UTC | @jipin8855/1424 · this entry28 Aug 2026, 13:00 UTC | 1.00 | under a minute |
| @mumbai_tg/23657 Oct 2026, 13:54 UTC | @jipin8855/1586 · this entry7 Oct 2026, 13:55 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @mumbai_tg | 37 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @mumbai_tg (34–3) |
| @cph997 | 21 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @cph997 (17–4) |
| @hz101101 | 17 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @hz101101 (16–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. 67 of the 67 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 65 comparable posts for this entry, running 9 August 2026 to 14 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 4 channels, the one whose matching posts we hold earliest is @mumbai_tg. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, last confirmed 16 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 4 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 |
|---|---|---|
| 15 Nov 2026, 13:18 | 29,118 | -68 |
| 12 Nov 2026, 03:07 | 29,186 | -72 |
| 10 Nov 2026, 06:41 | 29,258 | -66 |
| 8 Nov 2026, 16:39 | 29,324 | -101 |
| 7 Nov 2026, 07:58 | 29,425 | -42 |
| 6 Nov 2026, 06:26 | 29,467 | -46 |
| 5 Nov 2026, 08:57 | 29,513 | -38 |
| 4 Nov 2026, 10:01 | 29,551 | -34 |
| 3 Nov 2026, 11:34 | 29,585 | +56 |
| 2 Nov 2026, 13:36 | 29,529 | +56 |
| 1 Nov 2026, 10:09 | 29,473 | -104 |
| 31 Oct 2026, 08:46 | 29,577 | -38 |
| 30 Oct 2026, 06:09 | 29,615 | -463 |
| 29 Oct 2026, 03:10 | 30,078 | -281 |
| 28 Oct 2026, 00:09 | 30,359 | +46 |
| 27 Oct 2026, 02:45 | 30,313 | +145 |
| 26 Oct 2026, 04:55 | 30,168 | +264 |
| 25 Oct 2026, 03:38 | 29,904 | +300 |
| 24 Oct 2026, 04:38 | 29,604 | +128 |
| 23 Oct 2026, 06:35 | 29,476 | first reading |
68 posts held, back to 9 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 173 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 15 of 26 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 68 (9 August 2026 – 14 November 2026) |
| Views total | 31,743 |
| Reactions total | 14 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 12:40 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 16 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 44 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.
36 reactions across 27 posts, in 4 distinct kinds. The most used accounts for 86.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 31 | 86.1% | |
| 👍 | 2 | 5.56% | |
| 😍 | 2 | 5.56% | |
| 😁 | 1 | 2.78% |
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 32 of the 68 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 36 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 68 most recent posts we hold, published 9 August 2026 to 14 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 26 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).
🟡昵称:小新 🕐地区:#萧山 🤖双向:@xiaoxin518888_bot 🚀电报:@xiaoxin518888 🔔🔔频道: 点击浏览频道👀 🔴标签 #已验证上榜 🔰【格语 】 淡淡的眉眼自带疏离清冷感,安安静静的时候,有种清冷高级的美,一旦展露笑容,又瞬间温暖了时光。
❤1
圈界NO.1 🟡昵称:小饭同学 🕐地区:#拱墅区 🤖双向:@xiaofanfan23bot 🚀电报:@Jiajia775 🔔频道: 点击浏览频道👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】 姿容端庄,神态自若,自有一种超凡脱俗的气场。 🔰#点击下方查看详情⬇️
业界NO.1 🟡花名:小希 🕐位置:#拱墅 🤖双向:@xiaoxi1818bot 🚀电报:@xiaoxi520666 🔔小窝: 点击浏览频道👀 🔴课费:⬆️课表查看图⬆️ 🔴标签 #已认证上榜 🔰【格言 】 明亮的眼眸当中藏着万千情绪,欢喜温柔沉静,全部都能够从眼神读出,眼睛便是你最美的五官。 🔰#点击下方查看详情⬇️
❤1
圈界NO.1 🟡昵称:欢儿 🕐地区:#余杭 🤖双向:@huaner0899bot 🚀电报:@huaner08 🔔频道: 点击浏览频道👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】 你的美有厚度,岁月沉淀赋予了你别样韵味,历经生活依旧光彩动人,时光没有消磨,反倒加成你的魅力。 🔰#点击下方查看详情⬇️
❤1
👼【花名】 萧萧晴 ⏳【课室】拱墅 💴【双向】 @guoguobuchila_bot ✈️【联系】 @guoguochibupang888 💖【频道】 点击浏览频道👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】 连不经意的回眸都格外动人,一瞬间的神态,足够让人在心底留存很久,很难忘掉这般惊艳的瞬间。 🔰#点击下方查看详情⬇️
❤1
🟡昵称: 糖小雅 🕐地区:#拱墅 🤖双向:@xiaoya_Xbot 🚀电报:@tangyaya789 🔔频道: 频道点击浏览👀 🔴水费:📤课表查看图📤 🔴标签 #可放心出击 #已验证 #车费定金狼友自己随意不超过100 #老师狼友请看下方评论区⬇️
❤1
🟡昵称: 妹怡 🕐地区:#拱墅 🤖双向:@mtsxjqr_bot 🚀电报:@Mm356788 🔔频道: 频道点击浏览👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】 笑起来的时候整个人都闪闪发光,明媚的笑意很有感染力,仿佛可以驱散周遭所有的沉闷,这般鲜活的模样实在让人难忘。 🔰#点击下方查看详情⬇️
❤1
全杭州公寓式【一对一私密空间服务】 高颜值 spa 天花板《换装主题 spa》🥰《百店联盟》《覆盖全区域》 服务内容:🐻胸推 👋手推 👠足推 🐬臀推 🦅音推 细节:🍒果冻 🐉毒龙 💦过水 漫游 👄舌滑 🐻胸滑 👋指滑 丝足 吸皮过水 🫧蚂蚊上树 🍑猴子偷桃 海底捞月🌙可亲亲 可摸摸💥可揉揉 调情🫦百娈換装 丝袜任撕🚗🚕🚙 《便宜没好货,好货不便宜》 《贵的价格 相应的质量 相应的服务》 《👑只做精品💯》 原价:699❌ 预约价只需需要 599✔️ 每天出勤100+ 💕 服务时间60分钟 出水不限💥 想出几次出几次让大哥飘飘欲仙 💕出勤60+😠位美女 现场海选 👍各种款式我们都有 福利地址: 萧山 拱墅 西湖 上城 余杭 滨江 临安 临平 富阳 钱塘 下沙 各区都可以安排 双向客服: @lxtx0011181bot 私信客服:@hzgyzz001 频道 点击预览👀 群组 点击…
🟡昵称: 困困不困 🕐地区:#拱墅,上门比较多 🤖双向:@Maybe02141_bot 🚀电报:@knkun2626 🔔频道: 点击浏览频道👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】 皮相鲜活饱满,气色始终在线,整个人透着蓬勃生机,这份由身体内里透出来的状态,远比修饰更加珍贵。 🔰#点击下方查看详情⬇️
🟡昵称: 美少女小七( 🕐地区:#拱墅区 🤖双向:@zl99632sbot 🚀电报:@xx8899k 🔔频道: 频道点击浏览👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】 你自带气场,走在哪里都是一道无法被忽视的风景。 🔰#点击下方查看详情⬇️
圈界NO.1 🟡昵称:🎀妍妍酱 🕐地区:拱墅# 🤖双向:@yanyan9obot 🚀电报:@yanyan9o 🔔频道: 点击浏览频道👀 🔴水费:📤课表查看图📤 🔴标签 #已验证上榜 🔰【格语 】 热闹人群之中,你安静淡然,不争抢不张扬,可出众的样貌气质,依旧会吸引周遭不少人的目光停留。 🔰#点击下方查看详情⬇️
❤1
杭州全区 杭州全区 杭州全区 【全区95 98莞式全套海选会所】🌸私人定制spa私密会所 😇 海选 😇 油压 😇 莞式 😇 全套 😇 花式 🟢会所介绍 :海选模式 莞式服务, 环境豪华私密安全, 给您至尊享受的高端体验,可依您的喜好和需求为您做专属的私人项目定制。 更多剧本等你来解锁 主题房,制定角色,制定服装,满足你的所有幻想莞式36式 , 🛁皇帝共浴,💆菲式按摩,💪莞式抓龙, 👙制服诱惑, 👯♀️ 双人系列, ⛓️SM, 🍆情趣道具, ㊙️情景互动 全裸艳舞 😃 鸳鸯戏水😄 水磨推拿😄 口舌调情 😄 后口毒龙 😀胯下吞龙 😃手推胸推😄 足推臀推 😊 激情爱爱 😄 制服情趣😀 到店海选 😄【冰火双重天】😃 等三十多种项目。💒 🔥服务流程:皇帝共浴🛁指滑🫳🏻鼻息🗓舌尖漫游🥂-ab面骑士-💋柔式按摩放松-❤️花式调情雄起📞-水漫金山-🎯漫水吹箫💖-深情直入🥂🍀深喉…
❤1
Showing the 12 most recent of 68 posts we hold for @jipin8855. 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 6 posts on @jipin8855 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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“杭州极品公开” (@jipin8855), 29,118 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/jipin8855.
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.