Channel
@keer_188
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
1,292subscribers
-42 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1004322597140 |
|---|---|
| Type | Channel |
| Username | @keer_188 |
| Created | Between 1 June 2026 and 30 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/keer_188 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 03:19 | 1,292 | -44 |
| 9 Aug 2026, 01:21 | 1,336 | +2 |
| 8 Aug 2026, 12:15 | 1,334 | first reading |
19 posts held, back to 30 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 1 pageof 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 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 19 (30 July 2026 – 8 August 2026) |
| Views total | 7,974 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 12:15 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.
Measured directly from 2 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.
3 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 3 | 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 5 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 3reactions 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 30 July 2026 to 8 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.
郑州楼凤阁修车群专属报告 【妹子花名】：可儿 【老师车牌】：{1} 【验证留名】：匿名 【人照得分】: 8 【颜值得分】: 8 【身材得分】: 8 【服务得分】: 9 【态度得分】: 9 【环境得分】: 9 【综合得分】: 8.5 【验证时间】：2026-08-08 【过程描述】：匆忙和老师约好了时间，让老师的指引找到地方。开门见到老师，一眼惊艳，比照片好看，感觉老师不太会拍照，进门让老师换上经典黑色情趣内衣。小弟一下子就有感觉了，身材慢慢的让人喷血，老师就是一个典型的御姐类型，那双腿，又长又直，直呼受不了，老师招呼进去共浴。老师仔仔细细地给我洗澡，还帮我擦干身子，直接就是非常细致🙊🙊 完事就到正片了，感觉老师还是很敏感的勒，喜欢别人摸她。老师还特别会撩你，会在你的耳边轻轻地舔。老师的口活也是一绝，差点给我整废了，我立马喊停了。后续就是带上🌂，和老师策马奔腾。完事了和老师一直聊天，也不会着急，情绪价值拉满了…
开课啦，宝宝们
下课啦
【时间】：2026-08-07 【老师】：可儿 【留名】：匿名 【人照】：8.8 【颜值】：8.8 【身材】：8.8 【服务】：9 【态度】：9 【环境】：9 【综合】：8.9 【过程】：虽然我约的尾课，但是服务一点不含糊，吸皮，波推，臀推，素股……该有的一样不少。毒龙也超久超卖力，配合着旁边的镜子，景色一览无余。因为今天赶了火车直接来约的课，感觉不是那么容易发射，经过了老师的按摩和口之后戴上套子就开干，老师小穴很紧很烫，加上浑身的润滑液滑溜溜的，抱着操简直爽翻。稍微休息了一下去充了个澡换到房间开始后续服务，依然是很有耐心的做完该做的服务然后提枪上马，老师小穴很敏感，没插几下就湿透了，然后开始呻吟浪叫。遗憾的是今天实在太累了，没有能出货，但是老师丝毫没有催促，反而觉得没有让我尽兴而抱歉，不过我倒是觉得出来玩开心就好了，不一定非要怎么样，不管怎么说，老师的颜值，身材，服务都是相当霸道的，下次休息好了再来约课，奉上自己最好的状态。
❤1
她很乖，那会不会想起我这个坏的，我让你天天做新郎❤️❤️
给哥哥们跳支舞了睡觉吧👩🦰
郑州楼凤阁修车群专属报告 【妹子花名】：可儿 【老师车牌】：{1} 【验证留名】：匿名 【人照得分】: 9 【颜值得分】: 9 【身材得分】: 9 【服务得分】: 10 【态度得分】: 10 【环境得分】: 10 【综合得分】: 9.5 【验证时间】：2026-08-06 【过程描述】：课室还是很好找，到楼下后可儿LS指挥上楼。进门后见面，被惊艳到了，身穿一身短裙，腿好白好嫩，穿着蕾丝透视装，若隐若现，很有视觉感。我受不住直接上手摸很挺弹性十足。我忍不住上去细细摸索老师的丝袜脚，有一股淡淡的体香，腿是又细又长。老二已经饥渴难耐了，随后可儿ls的小嘴帮我口，小嘴包裹温热紧致，口活非常好，十八般武艺齐上阵。老师身体十分敏感，下面水多，一直感受那性感的小嘴包裹感，实在太舒爽了，不过看着老师骚表情和呻吟声，最后在老师一声声的，啊…啊…嗯…嗯…我受不了诱惑的感觉。憋不住交货了。 太爽了，老师颜值和身材，还是气质绝对超值…
郑州师范学院修车群专属报告 【妹子花名】：可儿 【验证留名】：匿名 【人照得分】: 8 【颜值得分】: 9 【身材得分】: 9 【服务得分】: 9 【态度得分】: 10 【环境得分】: 10 【综合得分】: 9.17 【验证时间】：2026-08-06 【过程描述】：上课教室环境很好，见到小姐姐和照片完全相同，真的好看。身材很棒很顶。我觉得小姐姐笑起来很好看。洗澡很仔细，下面洗后会口，我喜欢看别人舔我的jj的样子，洗完后上床，一边口一边深情的看着我，主动把屁股给我玩，看到小姐姐的屁股和bb，很想吃，不管了，直接吃，非常好吃啊，69真的是很爽的感觉。然后开始爱爱，叫的不错，十几分钟后结束第一炮。休息闲聊，很开心，夸人谁不爱听呢。剩半小时时开始第二炮，后入，因为我想看老师屁股和腰臀比。真的很不错，舒服两炮结束
报告来源：郑州烩面馆 【时间】：2026-08-06 【老师】：可儿 【留名】：Loo Jun Weng 【评价】：👍 好评 【人照】：9 【颜值】：9 【身材】：9 【服务】：10 【态度】：10 【环境】：10 【综合】：9.5 【过程】：之前看到可儿老师，一直在出击与否中徘徊。今天终于下定了决心尝试一下。提前跟老师约了时间，准点到达。上楼见到老师第一眼，颜值完全是长到我的心巴上的，身材也很不错，大长腿、很有人妻感，还很热情的邀请进门，在沙发聊了一会天后付了课费，然后就去浴室洗澡，老师很有耐心的给我洗了二弟，搓了身体，擦干上床开🐍，二弟已经起立等着老师的宠幸，一口下去，我靠是真爽啊，嘴巴热热的，毫无齿感，试了试69，逼型很好看毛少没有异味，舔的时候老师会时不时抖动一下，似乎很敏感。忍不住了戴伞开干，插入一瞬间就察觉到了紧度，是真的紧，有种要把我二弟夹断了的错觉。最喜欢传教，上面跟老师🐍下面对着老师的花心猛干，简直上天了。换了…
开课啦！这个姿势宝贝老公们喜欢吗？我屁股大哦⬆️⬆️
郑州师范学院修车群专属报告 【妹子花名】：可儿 【验证留名】：匿名 【人照得分】: 9 【颜值得分】: 9 【身材得分】: 8 【服务得分】: 9 【态度得分】: 9 【环境得分】: 9 【综合得分】: 8.83 【验证时间】：2026-08-05 【过程描述】：提前跟老师约好时间，下班后立即出击。 老师个子不高，165左右，不胖不瘦，浅黄皮。 鸳鸯浴，老师帮忙把上下前后洗干净，然后蹲下开始吃鸡吧，边吃边摸蛋蛋，还是挺舒服的。 擦干上床，老师先舔胸，然后开始吃蛋蛋吃鸡吧。口的时间挺长的，然后又来了69，老师下面是一线天，洞口小小的，没有异味。抱着舔了一会，老师挺敏感的。 最后戴套啪啪，先是传教，边抽插边吃奶。然后换抱🌿，抱起老师开始颠勺。再换后入，老师会下腰，后入可以清晰看到老师的小屁眼。最后换回传教冲刺出货。 休息一会，老师再一次帮洗干净后离开。老师很仔细，值得回锅
红休后第一炮谁来呀❤️❤️❤️
❤1
Showing the 12 most recent of 19 posts we hold for @keer_188. 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.
Citation-graph rank — 947,089 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“可儿的秘密基地” (@keer_188), 1,292 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/keer_188.
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.