Channel
@LinDa66188250
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
661subscribers
+110 since we began measuring on 11 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004335300154 |
|---|---|
| Type | Channel |
| Username | @LinDa66188250 |
| Created | Between 1 June 2026 and 30 September 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 October 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/LinDa66188250 |
Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 27 October 2026 and assigned it the closest of 31 fixed categories, at 91% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 23:45 | 661 | +42 |
| 27 Oct 2026, 21:46 | 619 | +21 |
| 21 Oct 2026, 09:49 | 598 | +36 |
| 13 Oct 2026, 22:15 | 562 | +11 |
| 11 Oct 2026, 05:22 | 551 | no change |
| 11 Oct 2026, 04:47 | 551 | first reading |
20 posts held, back to 4 October 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 page 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 15 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 October 2026 |
|---|---|
| Posts held | 20 (4 October 2026 – 10 October 2026) |
| Views total | 2,550 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Oct 2026, 05:22 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 7 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.
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 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 3 of the 20 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 4 October 2026 to 10 October 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 15 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).
💃艺名：美惠子 ✈️资料：https://t.me/shxyls/36619 ⛳️位置: #普陀区 🙍♂️学生：ZYu ———————————————— 美惠子身材娇小，是混血，真人和照片、视频里一样。她亲切又细心，一开始先带我去浴室，帮我仔细洗了个澡。 她主动帮我口交，感觉很舒服。我轻揉她的阴蒂，她很快就湿了，反应也很真实自然。我慢慢进入，再抱起她换成莲花坐姿，之后转成传教士体位，把她的膝盖抬高。她越夹越紧，舒服得让我忍不住射了。 结束后，她帮我按摩，我们轻松聊了一会儿。她幽默又好聊，就像和朋友相处一样。整体体验很好，非常推荐。
Video, posted without a caption
👍👍👍【艺术展览会福利群】⬇️ 免费拿5折6折7折优惠 和抽奖 白嫖 现金红包🧧福利 本群专属手势认证高质量老师 上海艺术展览会福利群： https://t.me/+nFnE0wANtSRkMjEx 点击进去备用群 上海艺术展览会总榜单：https://t.me/+Bc16na5DQI82MDli 上海艺术展览会人气推荐榜 https://t.me/+vOj1VuT48NE3MDc1 上海艺术展览会中转平台 https://t.me/+-sIwH2NalFw2MzEy 展览会老师广告群 @shanghaiyishu 个人推荐频道88🧧 📡 上榜管理：@yishuja_bot 📡 管理秘书：@Yishujia798_bot 📡 投稿报告：@Yszbgbot
Photo, posted without a caption
露出我的大长腿
Photo, posted without a caption
马上下班了
💃艺名：美惠子 ✈️资料：https://t.me/shxyls/36619 ⛳️位置: #普陀区 🙍♂️学生：SuzannePuccio ———————————————— @meihuizi52066美惠子去接我，不可思议，个子高挑瘦，皮肤白，去放水给我洗澡，去床上。穿了个秘书服，老板今天刚下班啊，老板娘不知道你出来找我吧，我说不知道，问我p要不改pp，我说不要看你表现，结果有点骚，口几下干一会就射了，聊了会天，身材怎么那么好，大长腿，s腰，是混血嘛，老板你好好看我迷人的脸蛋，是混血，很甜美，我直接说改pp吧，又换了一套情趣足球，说是我的足球宝贝，来第二次，直接去化妆台，服务很到位，结束了，
@meihuizi52066普陀区的，p1400朋友找过的菜，叫我去试试，一进来，个子挺高，身材很好，问我哥哥喝水嘛，就去洗澡了，躺着床上，问我喜欢什么制服，拿几十套。让我挑，就挑了个秘书服配个高跟鞋，温水给我口，360度给我口，然后就就去沙发上口，然后就坐上来干我，电动马达真厉害，问老师累不累，说不累，服务真好，身材很好，混血来的，可以看的出来，下次还来二刷 标签： @meihuizi52066 #美惠子 1400p #普陀 点击跳转原始报告【需先加群】 反馈狼友: 不知道叫啥 时间:2026-10-07 16:13:27 报告ID:20089 当前进度:1/5
上课了
Photo, posted without a caption
🎉 本次抽奖由 如果你也听说 发起 🆔 抽奖ID: 894 📢 抽奖信息: 普陀【美惠子】老师福利抽奖 1、资料 https://t.me/jiangnanlu1/22865?single 报告 https://t.me/yujie_feedback_search_bot?start=meihuizi52066 2、中奖后四天内（看清楚时间）使用，若老师休息则顺延，过期作废！ 3、转让规则：中奖者没办法去的私聊退给我，不允许私下转让。 4、与老师的其他优惠活动不叠加使用（如有），开奖后两日内私聊老师领取红包。 🎁 奖品内容: ⤷ @meihuizi52066 美惠子 优惠200（12p21pp） × 3 ⤷ @meihuizi52066 美惠子 优惠100 × 3 ⤷ 红包18.8元 × 4 📌 频道/群组要求: ⤷ 混血美惠子的频道 ⤷ 江南风情录 ⤷ 江南录老师开课群 🎯 抽奖要求: ⤷ 50 天内发言 …
Showing the 12 most recent of 20 posts we hold for @LinDa66188250. 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.
Named by 3 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.
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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“混血美惠子➕二次元模特” (@LinDa66188250), 661 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/LinDa66188250.
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.