钻石闪不闪

Channel
深圳—少女鉴赏指南
@szsnzn
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
9,544subscribers
+2,368 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002556586594 |
|---|---|
| Type | Channel |
| Username | @szsnzn |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/szsnzn |
Topic
Adult — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 16:19 | 9,544 | +219 |
| 14 Sept 2026, 22:01 | 9,325 | +387 |
| 11 Sept 2026, 04:59 | 8,938 | +423 |
| 5 Sept 2026, 23:37 | 8,515 | +128 |
| 1 Sept 2026, 23:56 | 8,387 | +173 |
| 29 Aug 2026, 18:57 | 8,214 | +161 |
| 26 Aug 2026, 20:37 | 8,053 | +81 |
| 23 Aug 2026, 17:13 | 7,972 | +196 |
| 20 Aug 2026, 03:14 | 7,776 | +129 |
| 16 Aug 2026, 17:45 | 7,647 | +293 |
| 13 Aug 2026, 05:14 | 7,354 | +114 |
| 10 Aug 2026, 13:45 | 7,240 | +40 |
| 7 Aug 2026, 17:42 | 7,200 | +24 |
| 6 Aug 2026, 20:16 | 7,176 | first reading |
Engagement
83 posts held, back to 1 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 17 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.80%
- avg views ÷ 9,544 subscribers
- Avg views / post
- 363
- 30 posts measured
- Reaction rate
- 0.393%
- reactions ÷ views · ER floor
- Posts in window
- 30
- of 83 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 30 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 83 (1 August 2026 – 28 August 2026) |
| Views total | 10,875 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 19:04 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
- 1m 02s
- Average length
- 10s
Measured directly from 6 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
13 reactions across 12 posts, in 2 distinct kinds. The most used accounts for 84.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 11 | 84.6% | |
| 👍 | 2 | 15.4% |
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 15 of the 83 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 13 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 83 most recent posts we hold, published 1 August 2026 to 28 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
美少女投稿报告模版 留名:ppdppp 老师艺名:#泡泡 位置坐标:#南山 颜值身材:人照像,声甜,嫩妹,胸挺且白 服务内容:课表 出击体验: 久仰大名,cj一次,提前一天约了时间,堵车稍晚到了,带上选好的衣服前往。进门之后先坐下闲聊了一会,泡说前段时间出去玩,手臂晒黑了,果然和衣服遮住的地方有一条明显的分界线,反而显得更有了些情调,闲聊后洗澡开动,口活还真的可以 不像其他嫩妹,堵车堵累了懒得操盘,直接戴套女上,实话说这个熊确实有点意思,白挺,在情趣衣服包裹下很有感觉,呻吟也很诱人,把她上身贴在我的胸前,软软的压住很舒服,随后换了几个姿势,冲刺时呻吟声逐渐变大,中途也会颤抖着夹紧,体验感还是不错的,顺利出水,算质量比较高的嫩妹 总结:比较值,可反 服务内容:p 联系方式:@CHAOJIPAOPAOTANG ( 导航: @SZGYHQG ) 报告提交: @MSNBG_bot
龙华茉莉 @moli641 3张100优惠券 转发至老师领取
🎉 小叶老师 抽奖福利🧧回馈活动 📝 抽奖说明:中奖主动联系老师 @Joy88888 ,兑奖必须写报告 中奖后三天内有效,预期失效并回收 ✅ 参与条件: 1. 加入 南山简悦 & 私享半裸抓龙筋高端SPA 2. 加入 深圳—美少女鉴赏 3. 加入 深圳—少女鉴赏指南 4. 加入 免费抽奖导航 🎁 奖品内容: • 100米BC可用优惠卷 × 5 • 16.8元口令红包🧧 × 3 ⏰ 开奖时间:手动开奖 👇 点击下方按钮参与抽奖
美少女投稿报告模版 留名:hh 老师艺名:#桢桢 位置坐标:#宝安 颜值身材:人照八分,声音甜美,技术好 服务内容:课表上都有 出击体验: 不确定真假,一看便知,见到老师就安了,笑容太好了,所谓微笑服务不过如此,老师绝对是激情倾心服务,对我的笑是发自内心的,真人对比上榜认证视频基本是没什么不同的,长相好看,对比频道照片也有9分像,皮肤超级白,而且很嫩滑,身材绝对值,堪比嫩妹天花板,胸大又挺不下垂,服务过程就不说了,脑补吧,水多,可喷水,服务用心听话配合,角色扮演太到位了,好会演戏,也很入戏,舌吻有女友感,主动!重要笑容太突出了,会笑的人总是给人带出好运哈哈,一定要再来 总结:值得二反 联系方式: @zhenzhen31 ( 导航: @SZGYHQG ) 报告提交: @MSNBG_bot
美少女投稿报告模版 留名:koop 老师艺名:#Marina 法国 位置坐标:#宝安 颜值身材:人照九分,声音甜美,身材很顶 服务内容:pp 出击体验: 约好时间,准时到达,进门看到老师,身材真好,腰细屁股大,一眼就沉沦了,付了课费,我们有说有笑的一起沐浴,来到床上老师看着我直直挺立的老二,坏笑着含入,灵活的舌头细致的舔吸、吞吐,好爽!一阵享受后老二有些扛不住了,翻身探索老师芬芳的身体,从上至下,我贪婪抚摸着老师曼妙的身材,热烈亲吻着老师的酥胸,情到深处,带帽开始艾艾,老师挺着双峰蹲坐在我身上,一直顶到最深处,太舒服了,差点被秒,翻身后入,视觉真是绝了,触觉是紧致、湿滑与一阵阵情不自禁的收缩,让人欲罢不能,实在令人把控不住加快节奏进入高潮,小蝌蚪犹如山洪暴发般一泻千里!老师各方面我都非常满意,必回! 总结:服务十分热情,值得二反 联系方式: @Marina6415 ( 导航: @SZGYHQG ) 报告…
❤1
投稿报告模版 留名:gg 老师艺名:茉莉 位置坐标:#龙华 颜值身材:9 服务内容:频道有的都有,老司机都懂 出击体验: 下午没事看群 看到路上照片对味于是约好时间就迫不及待的出发了到了约定地点指引上楼开门第一眼看到一双雪白的大长腿就迫不及待的付了水费、随后坐在床上闲聊调情然后就拉着我去共浴擦干身体看到老师雪白的酮体真不亏是嫩妹三点粉嫩二弟直接起来站岗了于是抱着老师上床然后老师开始了他的服务过一会扔不住了带上雨伞传教士体位、一顿123、321然后老师喷了出来随后二弟也喷涌而出然后就趴在老师身上休息了一会、起身把战利品丢进厕所冲走洗完澡后休息了一会出门老师给了一个拥抱体验和好下次必返! 联系方式: @moli641 ( 导航: @SZGYHQG ) 报告提交: @MSNBG_bot
投稿报告模版 留名:路人 老师艺名:星星 位置坐标:#龙华 颜值身材:9 服务内容:频道有的都有,老司机都懂 出击体验: 闲来无事刷下电报,看到电报名字星星很有感觉,就随意聊起来,妹子聊天很有耐心,于是联系妹子视频后是本人后果断出击,见面妹子个子小小的,邻家女孩既视感,也不认生,教完水费开始运动起来。过程妹子很配合,服务超好,也很健谈,情绪价值给足,各种细节在此不表,总之不虚此行。值得出击…… 联系方式:@ingopo ( 导航: @SZGYHQG ) 报告提交: @MSNBG_bot
美少女投稿报告模版 留名:hg 老师艺名:#Marina 法国 位置坐标:#宝安 颜值身材:人照九分,声音甜美,身材很顶 服务内容:pp 出击体验: 人照一致,异域风情,流连忘返,洋妹的颜值和身材都在线,身材看着前凸后翘真人更性感可爱,见面笑脸相迎主动搭话,给人一种非常自然的感觉,让人很放松,陪浴的时候就身体贴的很紧,前后游动各种调情抚摸,服务比较认真意思,不是那种过过场让快速出水那种,课表有的都细节地体验到了,体验感拉满,啪啪时候水很多,妍妍呻吟的很给力,各种姿势随意切换耐心配合,后入臂浪很大让人兴奋,几分钟后交出牛奶,真的是被她征服了 总结:服务十分热情,值得二反 联系方式: @Marina6415 ( 导航: @SZGYHQG ) 报告提交: @MSNBG_bot
❤1
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_954209868
心里空空的,总感觉有什么没得到😃😃
宝安甜甜 @tiantainu 3张100优惠券 转发至老师领取
Showing the 12 most recent of 83 posts we hold for @szsnzn. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@Paopaozainanshan · 7,0264 posts素素的快乐小窝
@Susu007x · 1012 posts小怡的温馨小窝
@dododoya123 · 2652 postsCoco Elva Tia
@sweetcoco520 · 2472 posts开课中 深圳福田双胞胎06 子玉的神秘嘉宾
@ziyu769 · 5,2342 posts福田 糖宝小屋
@isTangbao · 1881 post暖暖咪的朋友圈
@nnm36d · 971 postMarry you💍
@szmerry · 2041 post福田极品,十八男大
@szmnsjs · 1011 post深圳·鉴赏录
@tiantianriji2 · 7,2041 post宝安 18岁晚晚的小窝
@wanwan3272 · 1,1851 post龙华小小小樱的频道
@xiaoyingyyiy · 2131 post优米妙妙屋
@zz000xiao · 3,1411 post
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 6 registered channels — 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳—少女鉴赏指南” (@szsnzn), 9,544 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/szsnzn.
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.