Telegram RegisterThe public register of Telegram
Telegram profile photo for 玉女 心宝的家🏠

Channel

玉女 心宝的家🏠

@lhkhj6565

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

530subscribers

-1 since we began measuring on 30 August 2026

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

Register entry

Telegram ID-1002714207358
TypeChannel
Username@lhkhj6565
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 August 2026
Last confirmed live31 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/lhkhj6565

Growth

530531530.530 Aug 2026, 16:45 — 531 subscribers31 Aug 2026, 00:23 — 530 subscribers30 Aug 2026, 16:4531 Aug 2026, 00:23
2 measurements taken within a single day, net -1. 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 530–531 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 00:23530-1
30 Aug 2026, 16:45531first reading

Engagement

19 posts held, back to 17 December 2025the 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
1.32%
avg views ÷ 530 subscribers
Avg views / post
7.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 19 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 August 2026
Posts held19 (17 December 202530 August 2026)
Views total7
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken30 Aug 2026, 16:45 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.

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 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 1 reactions 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 17 December 2025 to 30 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

5 Aug 2026, 08:27 UTC13 viewsread 30 August 2026
Forwarded from @SHDD333

💃老师:#心宝 🤖链接: https://t.me/shanghaidadao/11240 💒位置: #浦东 ------------------ 💌出击报告:老师很好看,身材也很好,尤其是皮肤特别光滑,摸起来感觉特别好。ls引导很有耐心,会详细指引如何进入gzs,因为堵车迟到了一会,但是心宝ls依然很耐心,服务态度非常好。进入服务之后ls很温柔,很配合,项目也很舒服,让人欲罢不能。在中间休息期间也不会催促,会聊天,互相玩乐,真的体验非常不错,是非常完美的一次体验!推荐

4 Aug 2026, 12:29 UTC12 viewsread 30 August 2026
Forwarded from @SHDD333

💃老师:#心宝 🤖链接: https://t.me/shanghaidadao/11240 💒位置:#浦东 ------------------ 💌出击报告:老师身材好,人照9分,情绪拉满,口的很绝,差点忍不住。马上戴上小雨伞123被老师秒了,完事聊天不崔钟态度很好,人美心善的小姑娘。是我的菜,会返。

29 Jul 2026, 08:41 UTC14 viewsread 30 August 2026
Forwarded from @SHDD333

💃老师:#心宝 🤖链接: https://t.me/shanghaidadao/11240 💒位置: #浦东 ------------------ 💌出击报告:舌头温热而湿软,顺着身体中线一路往下,经过胸口时故意绕着乳晕打转,再滑过小腹,最后停在最敏感的地方轻轻吸吮。每一下都带着明确的目的,像是在我身上画出一条只有她知道的路线,刺激得人腰眼发麻。还没完全回过神,她已经跨上来摆好69的姿势。上面是她柔软的胸推,软肉把整根紧紧夹住,上下套弄的同时还会用中间那道沟用力收紧;下面是她主动含住,又吸又舔,两边同时进攻,快感直接翻倍。她很会控制节奏,夹到最紧的时候就用嘴深吸一口,吸到最爽的时候又用胸用力挤压,完全不给喘息的机会。蛇纹的前戏铺垫、69的上下夹击、胸推时又夹又磨的技巧,整场服务过程环环相扣。这种身体很会、嘴也很会的,做完只想直接复购。

22 Jul 2026, 02:16 UTC19 viewsread 30 August 2026
Forwarded from @SHDD333

💃老师:#心宝 🤖链接:https://t.me/shanghaidadao/11240 💒位置:#浦东 ------------------ 💌出击报告:舌头温热而湿软,顺着身体中线一路往下,经过胸口时故意绕着乳晕打转,再滑过小腹,最后停在最敏感的地方轻轻吸吮。每一下都带着明确的目的,像是在我身上画出一条只有她知道的路线,刺激得人腰眼发麻。还没回过神,她已经跨上来摆好69的姿势。上面是她柔软的胸推,软肉把整根紧紧夹住,上下套弄的同时还会用中间那道沟用力收紧;下面是她主动含住,又吸又舔,喉咙偶尔收缩,两边同时进攻,快感直接翻倍。她很会控制节奏,夹到最紧的时候就用嘴深吸一口,吸到最爽的时候又用胸用力挤压,完全不给喘息的机会。胸推的时候她还会低头看我的反应,眼神又媚又专注,嘴巴却没停,时而把顶端含进去吮吸,时而用舌尖快速挑逗。会夹会吸这四个字被她诠释得淋漓尽致,每一寸都又会用力又会吸吮,把人伺候得又爽又崩溃。蛇纹的前戏铺垫、69的上

14 Jul 2026, 05:31 UTC35 viewsread 30 August 2026

2 点后🈶️🈳哦,亲爱的我学会毒🐲🐉🐉🐉

26 Mar 2026, 08:51 UTC121 views1 reactionsread 30 August 2026

【出击报告】[https://t.me/shdadao1] 【老师艺名】心宝 【联系方式】 @plplkk887744 【所在位置】浦东 【验证留名】匿名 【验证时间】2026 03 25 【颜值身材】9 【服务内容】看课表 【服务态度】10 【优点缺点】无 【推荐程度】9 【体验细节】老师比较温柔,服务很用心,进门先帮忙冲凉然后一起进房间开始服务,先A面女上,一发比较快就交待了,二发老师做完B面后,很用心的给我口,差点都把持不住出汁,然后老师背面坐上来,看着老师的肥臀,景色太美,有点想视频记录被老师婉拒,然后换了几次体位老师都比较配合,战罢老师帮忙沐浴更衣收队回家!总的来说是一次完美的出击,各位颜值控服务控无脑出击! ♥️温馨提示: 以上仅代表个人体验,报告仅供参考! 报告提交机器人:@BT888865bot 报告提交条件:需要提供约课记录及付款记录验证

1

3 Mar 2026, 05:23 UTC128 viewsread 30 August 2026
Photo

三月你好🥰 愿好运都降临在我的身边……爱你们哦

Showing the 12 most recent of 19 posts we hold for @lhkhj6565. 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.

Forward network

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.

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.

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.

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

“玉女 心宝的家🏠” (@lhkhj6565), 530 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/lhkhj6565.

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.