Telegram RegisterThe public register of Telegram
Telegram profile photo for 月亮与六便士👙

Channel

月亮与六便士👙

@YHB0690

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

1,381subscribers

-33 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002446071082
TypeChannel
Username@YHB0690
CreatedBetween 1 September 2024 and 22 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live22 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/YHB0690

Growth

1,3811,4141,397.57 August 2026 — 1,414 subscribers7 August 2026 — 1,414 subscribers10 August 2026 — 1,407 subscribers13 August 2026 — 1,408 subscribers16 August 2026 — 1,401 subscribers19 August 2026 — 1,391 subscribers22 August 2026 — 1,381 subscribers7 August 202622 August 2026
7 measurements spanning 15 days, net -33. 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 1,376–1,419 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 15:231,381-10
19 Aug 2026, 06:451,391-10
16 Aug 2026, 16:171,401-7
13 Aug 2026, 03:541,408+1
10 Aug 2026, 11:501,407-7
7 Aug 2026, 22:161,414no change
7 Aug 2026, 13:451,414first reading

Engagement

17 posts held, back to 22 September 2024the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 17 posts for this entry, the most recent from 26 March 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
44s
Average length
9s

Measured directly from 5 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,459 reactions across 15 posts, in 16 distinct kinds. The most used accounts for 31.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🥰45531.2%
🤩26318.0%
20814.3%
👏19513.4%
👍17111.7%
🔥15210.4%
👎30.206%
🌭20.137%
💩20.137%
🤮20.137%
🌚10.069%
🍾10.069%
👀10.069%
😈10.069%
😍10.069%
😭10.069%

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 16 of the 17 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,459reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 22 September 2024 to 26 March 2025, 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

26 Mar 2025, 07:17 UTC≈2,700 views0 reactionsread 7 August 2026
Video

【 32º定格 🌿 ✨ 与时光共舞的慵懒美学 】 期待与童鞋们再次相遇,近期正常开课哦~😘😘😘

28 Dec 2024, 14:47 UTC≈3,770 views1 reactionsread 7 August 2026
Photo

好久不见 想你们 明天开课喽~(再不开课我也受不了了呀)😘

1

6 Dec 2024, 13:54 UTC≈3,130 views7 reactionsread 7 August 2026

杭州学生会模板: https://t.me/hangzhou_520 评分标准: 6分-差 7分-及格 8分-良好 9分-优秀 10分-极品 【妹子花名】: #子涵 【联系方式】: @YHB6699 【妹子年龄】: 视觉二十五六吧 姐姐型 【验证留名】: 接班人 【验证时间】:2024.12.6 【大概位置】:金沙湖 【修车水费】:1500pp 【高端服务】:有的打✅ ① 舌吻 ✅ ② 69舔逼 ✅ ③ 情绪价值 ✅ ④ 毒龙 【人照相似】:9分 第一眼有点惊讶 差点以为走错 见面时着便装 很朴素 本人很漂亮 【身高身材】: 条竿蛮好 个人喜欢呢类型 【凶器罩杯】:手握刚好 【湿度紧度】: 老湿挺会夹 里边很暖 喜欢老师上位后入 看的见湿漉漉伴随bj进出的样子 超兴奋 也可能是我大hh 【环境细节】:环境好OK吧 生活痕迹比较明显 老师说她在这住了三四年 总之东西有点多 但

4👍3

26 Nov 2024, 10:29 UTC≈2,670 views2 reactionsread 7 August 2026

降温啦,爱我的宝宝们记得添衣哦! 不爱的别添。hh🎉🎉🎉

1🥰1

18 Nov 2024, 04:11 UTC≈3,190 views3 reactionsread 7 August 2026
Photo

子涵🧚‍♀(个兼川妹儿) ·Height身高 |163cm ·Weight 体重 |48kg ·Age 年龄 |98摩羯 ·Bust 胸围 | 34C ·Occupation 职业 | GFI健身教练&buyer ❤️‍🔥课表:Kiss💋(浅舌吻)6️⃣9️⃣ 臀推胸推 🚿指滑 爱爱👩‍❤️‍💋‍👩浴室调情 🛁环球漫游 🈚️套口 制服诱惑 👙角色扮演 🧼推拿按摩 可纯可欲 💦水多敏感…更多待哥哥Unlock 🔓 温柔体贴原生态 喜欢随和自然的关系 🈲变态低素质 嗑药喝酒 后花园 暴力桩机 皮肤病 课费:1800pp/90min 1000p/40min 2500/3h 私聊:@YHB6699 时间:18-24点前 偶尔中午也可 📣佛系自聊兼职,不常开提前预 🉑外出需提前支付额外产生的房费或路费 介意勿扰

👍21

14 Nov 2024, 04:22 UTC≈3,210 views1 reactionsread 7 August 2026
Photo

宝子们👀👀👀 原计划今日开课的因今日体检项目有一项动态心电 次日才能开课啦 关爱生命 定期体检 健康你我他 哈哈哈 原定今天约课的宝贝 只能明天优先排喽😴😴😴

👍1

13 Nov 2024, 14:09 UTC≈3,130 views3 reactionsread 7 August 2026

评分标准: 9分-优秀 【妹子花名】:#子涵 【联系方式】:@YHB6699 【妹子年龄】:25 【验证留名】:x x 【验证时间】:10月13日 【大概位置】:钱塘 【修车水费】:2500 【高端服务】:有的打✅ ① 舌吻 ② 69舔逼 ✅我自己没整 ③ 情绪价值 ✅拉满那种 很温柔 【人照相似】:人照9分 【身高身材】:身材高挑修长,腿很很长 【凶器罩杯】: C吧 【湿度紧度】:进去暖暖的,非常紧;体验感很好。 【环境细节】:位置不引人注目,但是好找。 【个人卫生】:卫生且温馨,没有任何异味。 【时间管理】秒回消息,不存在时间冲突,没有其他客人干扰。 【服务总结】:服务到位,热情主动,态度非常好,提了几个小要求都能满足;会按摩,很放松。重点强调一下情绪价值,非常会聊天。瑟瑟期间非常投入,会紧紧地和你贴合在一起,除了单纯的肉体交流还能感受到纯粹的欲望交流。 【推荐程度】:9分 【流程小文】

2👍1

26 Sept 2024, 18:23 UTC≈5,530 views1 reactionsread 7 August 2026

有会员的小伙伴们,感谢您的小手帮忙互相点点互推,爱你们~💋💋💋 https://t.me/boost/YHB0690

🔥1

26 Sept 2024, 18:19 UTC≈5,670 views116 reactionsread 7 August 2026

有会员的小伙伴,感谢您的小手帮忙互相点点免费的助推,爱你们~😘😘😘 https://t.me/boost/YHB6009

🔥37👏22🥰19🤩15👍149

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

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

“月亮与六便士👙” (@YHB0690), 1,381 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/YHB0690.

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.