Telegram RegisterThe public register of Telegram
Telegram profile photo for 渝九妹儿的频道

Channel

渝九妹儿的频道

@lhsss21970yyy

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

112subscribers

+89 since we began measuring on 29 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004464630341
TypeChannel
Username@lhsss21970yyy
Created28 August 2026 — measured — dated from the channel’s first post
First recorded29 August 2026
Last confirmed live17 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/lhsss21970yyy

Topic

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 26 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 why it has no browse page of its own yet.

Growth

2311267.529 August 2026 — 23 subscribers29 August 2026 — 25 subscribers8 September 2026 — 105 subscribers17 September 2026 — 112 subscribers29 August 202617 September 2026
4 measurements spanning 19 days, net +89. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 10–125 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 23:36112+7
8 Sept 2026, 23:19105+80
29 Aug 2026, 20:2425+2
29 Aug 2026, 18:0023first reading

Engagement

10 posts held, back to 28 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
127.3%
avg views ÷ 112 subscribers
Avg views / post
143
8 posts measured
Reaction rate
0.469%
reactions ÷ views · ER floor
Posts in window
8
of 10 held

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 1 of 8 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 29 August 2026
Posts held10 (28 August 2026 – 29 August 2026)
Views total1,141
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken29 Aug 2026, 18:00 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.

What this channel posts

Video runtime
28s
Average length
14s

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.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.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 1 of the 10 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 10 most recent posts we hold, published 28 August 2026 to 29 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.

Recent posts

29 Aug 2026, 16:06 UTC53 viewsread 29 August 2026

共享女友修车报告模板 『推荐指数:⭐️⭐️⭐️⭐️⭐️(贱评/差评/中评/中上/好评,)』 【日期】:2026年8月28号 【老师昵称】:渝九妹儿 【验证人】:LeeSin 【地 区 】:#宁波 【联系方式】:https://t.me/lhsss21970yyy 【价格 】:500P(工兵半价) 【安 全 性】:安全 【年龄】:28的样子 【肤色,手感】 :白,软 【人照相似,真人打几分】:8 【整体反馈】:地址安保做得挺到位,电梯必须刷卡才能上去。初见老师时,颜值跟验证时那条素颜视频几乎一模一样,皮肤白得发亮,身材正是我偏爱的微胖型——软软的腰肢、饱满的臀腿,看着就让人想上手揉捏。 进门后直接去洗澡。老师弯腰放水的时候,那双黑色丝袜的吊带深深勒进雪白的大腿根和丰满的臀肉里,勒痕红红的、带着轻微的凹陷,像在白腻的皮肤上刻下暧昧的印记。二弟瞬间硬得发胀,一下一下地跳。 老师主动陪浴,温热的水流里,她跪下来给我做水中深喉。那张…

29 Aug 2026, 15:49 UTC67 viewsread 29 August 2026

【服务过程】: 地址挺安全,电梯要刷卡,初见老师颜值跟验证的素颜视频差不多,身材还是我喜欢的微胖,于是就去洗澡了,看着老师放水时候,这丝袜带子勒出的痕迹在老师白花花的大腿和屁股上,二弟就开始跳动,老师有陪浴有水中萧,这里提下老师的深喉很顶,我感觉真的整根吞在里面的感觉,洗完躺床上老师有背部按摩放松,老师有过水,依旧是深喉,这个深喉真的到位了,然后站着口,蹲着口,这口活,怕是遭不住,戴上小雨伞,看着老师这白花花的的大屁股开始冲击了,这娇喘和叫床声反馈有点顶级,老师还是有技巧的会调动的你的频率,摇的很舒服,还会自己动,全程老师很配合,还会叫你多玩儿,服务态度打满分。我主要难出货,最后手打出货。 【最后点评】:小少妇类型,我感觉挺白的,服务态度好,情绪价值到位,深喉做爱配 合。微胖型,喜欢带点服务的可以一冲。 【Q反省/感悟】:把你完成的成就后面打(成就越多,意味着这技师确 实相当不错了):有的打√ 1.口交√ 2.接吻√ 3.吃奶√…

29 Aug 2026, 15:19 UTC69 viewsread 29 August 2026
Video

哈哈哈哈,没想到哥哥也会叫床🛏️😜😜

29 Aug 2026, 01:40 UTC213 views1 reactionsread 29 August 2026

渝九妹儿的课表 年龄:27岁 身高:165 体重:50 罩杯:大C 水费:快餐3 p5 45分 pp9 90分 包时1300 包夜议价 (连续超过20分钟手打) 服务:颜值较好,温柔妩媚,大🐻御姐 洞小水多还会叫,女友感强,服务之星,配合默契,无套口,水中潇,波推,舔蛋蛋,猴子偷桃,调情,漫游,指划,观音坐莲,情趣诱惑,丝袜👠诱惑,全程配合哥哥任何姿势,助浴 、6️⃣9️⃣、戴套爱爱、丝袜(自带)、🈚️🍑口、配合 🈲🈲🈲:无套、不议价、醉酒、磕💊、后花园、偷拍、 上课请带现金 电报号: @esddsdc 私聊双向时联系: @hhggvvd5bot

❤1

Showing the 10 most recent of 10 posts we hold for @lhsss21970yyy. 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.

Mentions

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.

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.

Cite this entry

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“渝九妹儿的频道” (@lhsss21970yyy), 112 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/lhsss21970yyy.

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.