🙋🏻♀️ 小狄 #km1082 ☎️联系方式: @anna2026baofu 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: #7P 所在区域:#官渡,官渡区 🏷️分类标签 #新人榜 💌评价小狄 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
Signed 太乙真人

Channel
@Kmainu95
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
66,094subscribers
+19,998 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002359437575 |
|---|---|
| Type | Channel |
| Username | @Kmainu95 |
| Description | 云南最纯粹的修车群组:https://t.me/Kmainu95111 备用群:https://t.me/yunnankmpyq 公开榜:https://t.me/Kmainu95 报告榜:https://t.me/ynkmsjjyzbgb 新人榜:https://t.me/Ynkmsjjyzzzz 商家榜:https://t.me/jyzgkb002 黑名单:https://t.me/ynkmsjjyzhmd 上榜 合作 解封: @kmyule8888_bot |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/Kmainu95 |
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 49% 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. 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 |
|---|---|---|---|
| @Ynkmsjjyzzzz/26581 Sept 2026, 15:11 UTC | @Kmainu95/3980 · this entry1 Sept 2026, 15:11 UTC | 1.00 | under a minute |
| @Ynkmsjjyzzzz/27507 Sept 2026, 08:54 UTC | @Kmainu95/4058 · this entry7 Sept 2026, 08:54 UTC | 1.00 | under a minute |
| @Ynkmsjjyzzzz/287812 Sept 2026, 12:23 UTC | @Kmainu95/4153 · this entry12 Sept 2026, 12:23 UTC | 1.00 | under a minute |
| @Ynkmsjjyzzzz/351426 Oct 2026, 06:37 UTC | @Kmainu95/4685 · this entry26 Oct 2026, 06:37 UTC | 1.00 | under a minute |
| @Kmainu95/4833 · this entry7 Nov 2026, 06:44 UTC | @Ynkmsjjyzzzz/37117 Nov 2026, 06:44 UTC | 1.00 | under a minute |
| @ynkmsjjyzbgb/586530 Sept 2026, 16:02 UTC | @Kmainu95/4333 · this entry30 Sept 2026, 16:02 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Ynkmsjjyzzzz | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (11–3) |
| @ynkmsjjyzbgb | 6 (6/6 hand-verifiable sample passed) | 0.99 | under a minute | this entry (6–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. 2 of the 2 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 430 comparable posts for this entry, running 6 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.
Recorded under the key clone_source, last confirmed 15 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Nov 2026, 12:58 | 66,094 | +590 |
| 11 Nov 2026, 16:57 | 65,504 | +497 |
| 10 Nov 2026, 00:18 | 65,007 | +76 |
| 8 Nov 2026, 13:59 | 64,931 | -253 |
| 7 Nov 2026, 08:15 | 65,184 | +234 |
| 6 Nov 2026, 08:59 | 64,950 | +295 |
| 5 Nov 2026, 07:15 | 64,655 | +311 |
| 4 Nov 2026, 06:47 | 64,344 | +176 |
| 3 Nov 2026, 03:46 | 64,168 | +432 |
| 2 Nov 2026, 05:01 | 63,736 | +278 |
| 1 Nov 2026, 05:28 | 63,458 | +391 |
| 31 Oct 2026, 01:57 | 63,067 | +343 |
| 30 Oct 2026, 02:08 | 62,724 | +230 |
| 29 Oct 2026, 05:27 | 62,494 | +281 |
| 28 Oct 2026, 03:17 | 62,213 | +284 |
| 27 Oct 2026, 04:26 | 61,929 | +254 |
| 26 Oct 2026, 04:00 | 61,675 | +349 |
| 25 Oct 2026, 00:50 | 61,326 | +352 |
| 24 Oct 2026, 01:27 | 60,974 | +319 |
| 22 Oct 2026, 21:56 | 60,655 | first reading |
438 posts held, back to 6 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 219 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 74 of 142 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 15 November 2026 |
|---|---|
| Posts held | 438 (6 August 2026 – 15 November 2026) |
| Views total | 140,437 |
| Reactions total | 108 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 00:21 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 3 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.
309 reactions across 203 posts, in 8 distinct kinds. The most used accounts for 91.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 283 | 91.6% | |
| 👍 | 17 | 5.50% | |
| 👏 | 2 | 0.647% | |
| 🔥 | 2 | 0.647% | |
| 🤡 | 2 | 0.647% | |
| 🎉 | 1 | 0.324% | |
| 😁 | 1 | 0.324% | |
| 🥰 | 1 | 0.324% |
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 251 of the 438 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 309 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 438 most recent posts we hold, published 6 August 2026 to 15 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: 28 of 142 posts held from the last 30 days (19.7%) 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).
🙋🏻♀️ 小狄 #km1082 ☎️联系方式: @anna2026baofu 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: #7P 所在区域:#官渡,官渡区 🏷️分类标签 #新人榜 💌评价小狄 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
Signed 太乙真人
🙋🏻♀️ ππ #km1097 ☎️联系方式: @Ling_er88 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: #7P 所在区域:#盘龙,盘龙区 🏷️分类标签 #新人榜 💌评价ππ 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
Signed 太乙真人
🙋🏻♀️ 莉丽 #km1095 ☎️联系方式: @hdhbdb3 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: #7P 所在区域:#曲靖 🏷️分类标签 #新人榜 💌评价莉丽 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
Signed 太乙真人
🎟 抽奖标题: 100通用优惠券抽奖--加油站公开榜 欣怡 @aiuy9087 👊重磅推出在榜老师出击优惠券抽奖活动!!! 🥰 老师:欣怡 🌃 区域:#西山 🆔联系方式:@aiuy9087 🏷️分类标签:#5p-9pp,#陪浴,水中萧,胸推,过水漫游,深喉,69,无套口,情趣丝袜,大胸,御姐,公开榜 ‼️优惠券抽奖细则: 1、中奖成功与老师协商出击时间,三天内出击; 2、出击实名提交优质车评报告; 3、中奖却未出击和写报告者将被群拉黑无资格参加群任何活动; 4、本优惠券抽奖活动最终解释权归 欣怡老师。 ‼️‼️‼️最后申明:请认真阅读了解活动内容及规则! 消耗积分: 108 积分 定时开奖 2026-11-17 18:00:00 参与关键词: 欣怡没得说出击就行了 已参与: 0人 🎁 奖品列表: 欣怡 @aiuy9087 100通用优惠券 X 3 参与要求: 💡必须设置用户名 ➕加入 - 云南昆明司机加油站修车…
Signed 太乙真人
🙋🏻♀️ 柠檬 #km1031 ☎️联系方式: @cheyaxin 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: #7P 所在区域:#西山,西山区 🏷️分类标签 #新人榜 💌评价柠檬 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
Signed 太乙真人
🙋🏻♀️ 小碟 #km150 ☎️联系方式: @Qwan15 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: #8P 所在区域:#官渡,大理,官渡区 🏷️分类标签 #嫩妹,兼职,大长腿,无套口,69,足交,陪浴,丝袜,公开榜 💌评价小碟 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
❤2👍1
Signed 太乙真人
🙋🏻♀️ 小呗呗 #km1094 ☎️联系方式: @js_666999 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: #6P 所在区域:#官渡,官渡区 🏷️分类标签 #新人榜 💌评价小呗呗 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
Signed 太乙真人
🙋🏻♀️ 小秋 #km1074 ☎️联系方式: @xq_887435 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: #7P 所在区域:#西山,西山区 🏷️分类标签 #新人榜 💌评价小秋 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
Signed 太乙真人
🎟 抽奖标题: 200通用优惠券抽奖--加油站新人榜 小萌 @xiaome1234 👊重磅推出在榜老师出击优惠券抽奖活动!!! 🥰 老师:小萌 🌃 区域:#官渡 🆔联系方式:@xiaome1234 🏷️分类标签:#7p-14pp,#嫩妹 #无套口 #69 #符文 #兼职 #新人榜 ‼️优惠券抽奖细则: 1、中奖成功与老师协商出击时间,三天内出击; 2、出击实名提交优质车评报告; 3、中奖却未出击和写报告者将被群拉黑无资格参加群任何活动; 4、本优惠券抽奖活动最终解释权归 小萌 老师。 ‼️‼️‼️最后申明:请认真阅读了解活动内容及规则! 消耗积分: 88 积分 定时开奖 2026-11-16 18:00:00 参与关键词: 18岁嫩妹小萌我来了! 已参与: 4人 🎁 奖品列表: 小萌 @xiaome1234 200通用优惠券 X 3 参与要求: 💡必须设置用户名 ➕加入 - 云南昆明司机加油站修车群 └ 💬 …
Signed 太乙真人
🙋🏻♀️ 多多 #km1030 ☎️联系方式: @duoduo162888 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: #7P 所在区域:#官渡,官渡区 🏷️分类标签 #新人榜 💌评价多多 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
Signed 太乙真人
🙋🏻♀️ 向日葵 #km1004 ☎️联系方式: @xrkui1 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: #5P 所在区域:#官渡,官渡区 🏷️分类标签 #新人榜 💌评价向日葵 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
Signed 太乙真人
🙋🏻♀️ 敏敏 #km1056 ☎️联系方式: @minmin78988 📊0条车评 综合评分0 好评0% 中评0%差评0% 身材: 环境: 服务: 态度: 颜值: 人照: 价格: #7P 所在区域:#呈贡,呈贡区 🏷️分类标签 #新人榜 💌评价敏敏 查看全部评价 ✳️云南昆明司机加油站修车群 ✳️云南昆明司机加油站报告榜
Signed 太乙真人
Showing the 12 most recent of 438 posts we hold for @Kmainu95. 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.
@Kmainu95 edited 50 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 23 posts on @Kmainu95 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 43 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“云南昆明司机加油站公开榜” (@Kmainu95), 66,094 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/Kmainu95.
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.