Channel
@yingying123889
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
68subscribers
+7 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003972453514 |
|---|---|
| Type | Channel |
| Username | @yingying123889 |
| Created | 12 August 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/yingying123889 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 06:08 | 68 | +7 |
| 13 Aug 2026, 21:46 | 61 | no change |
| 13 Aug 2026, 21:35 | 61 | first reading |
4 posts held, back to 12 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 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.
| Window | Rolling 30 days · latest post in window 13 August 2026 |
|---|---|
| Posts held | 4 (12 August 2026 – 13 August 2026) |
| Views total | 539 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 21:46 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.
2 reactions across 2 posts, 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 2 of the 4 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 12 August 2026 to 13 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.
艺名：莹莹 年纪：18岁 身高：160 体重：44(kg) 胸围：C 简介： 小妹 刚满十八，刚毕业出来 初次下海😘😘很多服务不懂。哥哥多理解，多多关照 服务项目： 浅吻 口吹 冰两重天 蜻蜓点💦 情趣丝袜诱惑 观音坐莲 配合各种爱爱姿势 。 700p(45分钟) 1400pp(90分钟) 外出pp(10公里内车费一张) 口令先车费 🍃课私聊 温馨提示：个人自聊，回复慢了请多担待 大数据时代尽量备现金 中途改课不退费哟 🈲无🍑 后花园 醉酒 手扣 桩机 特注：变太，阳痿了，不要来服务不了 联系方式：双向 @yueer55_bot 私信：@yingying88l 频道：https://t.me/yingying123889
❤1
【验证留名】：长沙小火泡 【验证时间】：8.月13号 【妹子花名】:莹莹 【联系方式】： 【所在位置】：青秀区，东葛路 【修车水费】：300 【身高身材】：9 【颜值相似】：10 【凶器罩杯】：c 【服务内容】：课表上的都有 【服务详情】：老师遥控进门，进门第一感觉一个字真嫩，老师牵着我的手进门，沙发坐了会，又急忙给我送来了一瓶水，我貌似感觉老师有点很紧张，我就急忙说妹妹别紧张，然后马上掏出水费递给老师，坐了会，老师自己把衣服脱的光光的然后给我脱衣服带我一起洗浴，出击以来这个是我见过最小的妹妹了，进入正题，浴室不是很大，但是也够两个人洗浴了，老师瘦瘦的大概90斤，浴室中我的枪已经硬的出淫水了，老师看我这么，就给我口了一会，口活还行毕竟这么小，那小小👄加上人的体温热度，真实舒服啊，差点缴枪，我一把抱起老师直奔床上🛏️、已经等不及老师其他服务了，直接进入，慢慢的放进去我的有点大，我怕老师疼，先是轻轻的顶进入一半，来回抽查一会，老师的…
❤1
Channel photo updated
Channel created
Showing the 4 most recent of 4 posts we hold for @yingying123889. 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 — 634,270 of 1,480,975entries 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.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“莹莹” (@yingying123889), 68 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/yingying123889.
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.