Telegram RegisterThe public register of Telegram
Telegram profile photo for 我和嫩妹有个约会

Channel

我和嫩妹有个约会

@sz_nmyhbg

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

6,373subscribers

-998 since we began measuring on 4 September 2026

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

Register entry

Telegram ID-1004465873249
TypeChannel
Username@sz_nmyhbg
CreatedBetween 1 June 2026 and 30 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live15 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/sz_nmyhbg

Growth

6,3737,3716,8724 September 2026 — 7,371 subscribers4 September 2026 — 7,371 subscribers6 September 2026 — 7,330 subscribers11 September 2026 — 6,944 subscribers15 September 2026 — 6,373 subscribers4 September 202615 September 2026
5 measurements spanning 11 days, net -998. 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 6,223–7,521 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 09:026,373-571
11 Sept 2026, 13:166,944-386
6 Sept 2026, 23:157,330-41
4 Sept 2026, 15:227,371no change
4 Sept 2026, 14:477,371first reading

Engagement

8 posts held, back to 30 August 2026the 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
14.9%
avg views ÷ 6,373 subscribers
Avg views / post
953
8 posts measured
Reaction rate
0.184%
reactions ÷ views · ER floor
Posts in window
8
of 8 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 3 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 2 September 2026
Posts held8 (30 August 20262 September 2026)
Views total7,620
Reactions total10
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken4 Sept 2026, 15: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.

What this channel posts

Video runtime
7s
Average length
7s

Measured directly from 1 video 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

10 reactions across 3 posts, in 1 kind.

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

Measured over the 8 most recent posts we hold, published 30 August 2026 to 2 September 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

2 Sept 2026, 14:48 UTC≈2,210 views3 reactionsread 4 September 2026
Photo

113 世间美人千万种,我却对你情有独钟 福田 初柠 @chuninbb 9/2 ⤴️⤴️福利视频点我 课室环境 想不到初柠一休就休息了这么久,第一次很盼望一个老师回来上课,甚至担心再也不回来了....😩😩开门后还是那个熟悉的小美女,忍不住拥她入怀中,这感觉真好!🥪🥪 整体评价(仅代表个人) 身材(9,5) 年龄目测18实际19,小淡妆脸上挂着小酒窝,很吃这样的颜值,不抽烟无纹身,像是刚上大一大二的小学妹🥰🥰 偏苗条,肤色比黄皮白一丢丢,瘦底下有一对美乳,胸型饱满好看,脖颈锁骨可以养一水缸鱼,非常修长养眼,PP也挺翘有肉~小腿笔直修长,PP两瓣嫩肉雪白嫩滑👅👅 小穴微粉紧致,真的很紧,好像瘦低的妹妹通道都是无比紧致,慢慢的包裹感,水也很多,白汁漫溢~👅👅 服务过程(9) 这次服务,我们更加熟悉彼此了,现在沙发上聊天唠家常,亲亲抱抱抓奶摸屁股,实在忍不住就抱到厕所洗澡,柠妹很自然的蹲下给我做了个水中萧,不错不错~🥪🥪 口活感觉比

3

1 Sept 2026, 07:06 UTC≈2,460 views3 reactionsread 4 September 2026
Photo

112 性格好颜值嫩妹 福田小野 @szxiaoye 9/1 ⤴️⤴️出击验证视频 课室环境 课室福田某地铁口150米,房间稍微小一点,算是比较干净整洁! 进门妹子就捂着脸对我笑。。给我整懵了,别说笑起来还挺好看的,很热情聊起天很舒服~😊😊 整体评价 颜值身材(9) 年龄估摸18身高有160左右,身材纤瘦类型,颜值还挺好看的,有纹身非花臂,瓜子脸小小个~ 肤色比黄皮要白,A乳有肉版本,乳头粉嫩很翘,舔一会妹子就受不了不断呻吟😏😏 腿很直,喜欢瘦的应该会很喜欢,整体比例很完美,人鱼腰,PP小小一个可以抓起来爆糙,总的来说,身材比较纤瘦,喜欢白幼瘦的福音啊!🥳🥳 服务手法(8) 妹子刚下海接的客还有限,服务手法只能说很稚嫩了,还需要狼友多操盘,妹子是属于听话接受调教类型,态度十分友好,可以好好把玩把玩👅👅 有蛇有69,帮亲咪咪后开始口,口齿感稍微重点,那就换我来!妹妹全身很敏感,美乳轻轻含住就嗷嗷停立,这种小奶这样也挺好看的~ 随

3

30 Aug 2026, 08:36 UTC778 views4 reactionsread 4 September 2026
Photo

111 乖巧巨乳小嫩妹 福田 @yinanqq166 吟吟 8/29 ⤴️⤴️福利视频点我 课室环境 课室福田某不太著名景点,地铁口150米,小区稍微比较老旧了点😊 开门震惊😱😱,妹妹已经穿好了性感的内衣漏出两个大巨乳迎着我,我一瞬间没反应过来,都没敢上手摸😩😩 整体评价 身材(9) 年龄估摸18身高158左右,肤色不太黄的黄皮,人照8.5乖巧安静类型,木有纹身🥪🥪 妹子本身不胖不瘦刚好,一对巨乳太吸人眼球了,由于年纪小不会下垂,全脂肪胸摸起来超软超舒服的,而且乳晕也不大,不会像25-30岁的巨乳那么哈人,胸控福音胸控福音~👅👅 小穴户型发量正常,小短腿搭配有肉的PP,屌感是不错💟💟 技巧(8.5) 主打听话配合类型,口技可圈可点,难得小妹妹能吞的比较深,而且口好久好久,服务态度也很好,69舌吻都有,让舔蛋蛋跪着口也一一照做💌💌 面对这对大乳,DO的时候总是忍不住抓两下,特别是女上的时候可以直接埋在你头上~ 边洗面奶边抓住

4

30 Aug 2026, 08:36 UTC694 viewsread 4 September 2026
Photo

110 弥补遗憾,心心念念的玉儿终于回来了! 福田 小玉儿 @hlm4nhun 8/27 课室环境 位置满分!!!新小区住宅非公寓,房间很大很干净整洁,地铁口200米很方便! 上次出击完玉儿,爱笑的面庞一直在我脑海盘转,无奈妹子回去了,听到玉儿回来短开几天,立马出动!!!🎉🎉 服务过程 身材(8.5) 身材引用上次内容~ 年龄18身高163左右肤色比黄皮白,没有纹身颜值耐看,很喜欢笑,甜美的笑容把我融化~🤗🤗 脱掉衣服玉儿美丽的娇躯一览无遗,胸前一对小椒乳(A+),乳头内陷摸一下傲然挺立,小腿雪白修长腿型极美,PP浑圆Q弹,小穴外唇黑里面一片通红,看着很是诱人~😏😏 总的来说颜值能打,穿衣打扮有审美无纹身非精神妹,胸再大点就好了🤗🤗 服务手法(8.5) 这次出击把玉儿当女朋友来对待!全程我操盘!👅👅 先洗澡,洗澡的时候贴在一起,在浴室就忍不住吻了玉儿,玉儿好像不太记得我了,妈的有点难过啊。。😩😩 上床后给玉儿做了前戏,舔耳

30 Aug 2026, 08:36 UTC506 viewsread 4 September 2026
Photo

109 背心与超短裤!青春靓丽小嫩妹~ 桃夭夭 @taoyysz 8/22 课室环境 地点龙华某地铁口700米,小区里面感觉安全一点,刚开的房卫生条件还可以! 约的头课,到小区里面后看到一个小嫩妹拖着行李箱在等门禁!我猜这B不会是我今天要凿的人吧,长得还挺好看啊,结果还真是。。。😱😱 整体评价 身材(9) 年龄撑死18身高163左右,肤色白皮皮肤紧致状态好,腿部有一个花花纹身,颜值挺耐看的小妹妹形象🤗🤗 身材苗条型,胸对A(有肉版),葡萄棕色粉嫩PP小小个,小穴正常颜色,小嫩穴又紧水又多👅👅 总的来说,苗条邻家小妹妹,颜值耐看皮肤状态不错😋😋 服务手法(8) 嫩妹服务就比较弱了,就常规陪洗后开始做,服务还算比较认真,上床后会先帮忙舔咪咪,有69没有蛇,喜欢蛇的注意~ 口技算是还不错了,按着头吞深一点也没反对意见,69姿势抓着两坨嫩肉边被口还是挺有感觉的😍😍 DO的时候小穴紧致头课也很水润,常规换着各个姿势开凿,后面抬起腿猛凿缴械

30 Aug 2026, 08:35 UTC397 viewsread 4 September 2026
Photo

108 可爱有趣的小甜妹 南山 莹莹 @Yingying7897 8/21 ⤴️⤴️ 出击验证视频 课室环境 南山某地铁口附近200米,出地铁口就是课室,课室高端安全卫生做的也好,不错不错~ 开门迎来一个可爱妹妹,开口甜糯糯的,声音能俘获我的心,一进来拉我到沙发递水给我喝,很热情的聊天,快速破冰🤗🤗 整体评价 身材(9) 年龄22身高有160左右,脸蛋小巧精致没有纹身,傲娇小妹妹类型,聊天很讨人喜欢~🥪🥪 肤色比黄皮白一点,皮肤稍微有点干燥,不瘦不胖刚刚好,PP两瓣嫩形状Q弹饱满,胸胸型饱满好看(B),两点棕褐色高高凸起非科技,穿上白色情趣内衣,挺拔的美乳搭配锁骨雪白的脖颈,超美超好看! 小穴水润的很,屌感也很不错👅👅 服务过程(9.5) 莹莹的服务挺强的,特别是口活示意深喉没抗拒就往里面顶,结果真接住了,于是按着头不断抽插,感觉能直接射...😏😏 我操作完后莹莹又自己爬上来舔全身,用胸蹭你,眼神拉丝直勾勾看着你,再用口给你

30 Aug 2026, 08:35 UTC304 viewsread 4 September 2026
Photo

107 服务一流巨乳姐姐 南山 蓝汐 @lanxisz1 8/4(补) 课室环境 南山某著名点地铁口附近500米,课室环境卫生还不错~ 进门一个大姐姐拉我进来,人照8.5左右,比较热情招呼喝水聊天~🙏🙏 整体评价 身材(9) 年龄30左右身高160左右人照9, 姐姐少妇类型~ 身材丰腴肤色黄皮,脱掉衣服两个硕大的巨乳在罩罩包裹下呼之欲出,很难得有这样纯天然的美乳,胸型手感都极佳👅👅 臀部饱满PP硕大,小穴毛发正常水润,屌感很不错🚲 服务过程(9.5) 老师从澳门会所出来的,服务很夯!水中萧一点不含糊,直接上冰火,从洗澡水中萧的强度就知道这次服务差不了👅👅 洗完澡选战袍,随后服务从按摩全身放松,放松完胸推,这样的巨乳全身过个遍很爽,然后全身过水,舔咪咪,开始口,口活也很不错~👍👍 DO的时候重点全在玩奶了,各个体位都忍不住攻击双乳,完事还让老师帮忙乳交,爽的一批~🥰🥰 服务情绪(9): 服务类型技师,服务很认真专业不催钟,要求也都

30 Aug 2026, 08:35 UTC271 viewsread 4 September 2026
Photo

105 青春无敌!性格好大长腿嫩妹 福田 婉月 @szwanyue 8/14 ⤴️⤴️出击验证视频 课室环境 课室福田某地铁口300米,新装修不久的课室,干净整洁位置感觉比较安全~ 进门一个大长腿妹妹,眼睛一眨一眨的盯着我看很害羞,做下来聊了一会后妹妹瞬间放开了好多,可能是第一次下海确实紧张💌💌 整体评价 身材(9) 18嫩妹净身高有168,人比频道要瘦一些,小脸蛋精致没有纹身,属于气质款~ 肤色黄皮A胸,看我在盯着胸看,妹妹搞笑的去拿了聚拢胸贴穿上,说这样就显得大了哈哈😅😅 妹妹腿很长比例不错,小穴湿润刚进入有点紧张说好几个月没做了,脸看着挺气质的,聊起天来很逗比啊哈哈,完全没刚进来那个拘谨的模样~🤗🤗 服务手法(8) 这刚下海的妹妹服务只能从顺从、听话角度来描述了,确实啥都不会,还需要狼友们多调教一下~😏😏 性格很好,陪洗完教她要帮忙擦背,口的时候让要先舔胸都很配合在学,看来以后服务不会差啊! 口也是提出多角度的要求,跪

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

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

“我和嫩妹有个约会” (@sz_nmyhbg), 6,373 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/sz_nmyhbg.

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.