Channel
@szprxdmmk2
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
17subscribers
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003269694426 |
|---|---|
| Type | Channel |
| Username | @szprxdmmk2 |
| Description | 龙华交流群：http://t.me/szprxdmmk 福田交流群：https://t.me/szbygmmk 出勤群：https://t.me/szprxdmmk1 报告馆：https://t.me/szprxdmmk2 wx：futian1155 地址：深圳市龙华区大浪 |
| Created | 25 October 2025 — measured — dated from the channel’s first post |
| First recorded | 18 September 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 1 |
| On Telegram | t.me/szprxdmmk2 |
Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 03:22 | 17 | first reading |
7 posts held, back to 25 October 2025 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 7 posts for this entry, the most recent from 29 October 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 18 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
航线： #白月光 航海员：#多多 船员： 小飒 出海联系 @szbygmmkdz 出航经费 628（积分兑换半价） 出海日期 2025/10/26 适合人群 适合喜欢嫩妹的 优 优点： 配合度高，年轻嫩，颜值不错，可爱 缺点：抽电子烟，龙华店这边有点暗 颜值：7 态度：8 配合型 上路：7.5🐍🈵，长度一般 中路：8 综合: 7.5 （1-3雷 4-7正常 8-10 幻神） 航海历程 换了个白月光卷，发现之前消失的多多又回来了，遂立马约上钟前往。 位置在大浪商业广场这边，很熟悉的地方，很快找到地方。坐下后，店长带多多过来看了下，略暗的灯光下多多确实可爱，我秒回可以，其实上次在福田已经见过了，是有后续上钟打算的，已经在计划中了。 火速用好漱口水，和妹妹熟络了下，骑乘位抱着，继续聊了会天，了解到之前是去罗湖别的美团店待了会，后续又回到大浪这边，离住的地方更近，看来大浪这边住确实是比较…
航线： #白月光 航海员：#纯纯 船员： 大力水手 出海联系 @szbygmmkdz 出航经费 628套餐 出海日期 2025/10/24 适合人群 适合喜欢御姐的，适合喜欢胸大的 优 缺点 优点： 身材修长，腿玩年，五官立体 缺点：性格还是i了一点 颜值：8 态度：7 配合型 上路：我没舌，故不评价 中路：9 综合: 8 （1-3雷 4-7正常 8-10 幻神） 航海历程 我刚从上个妹子下钟，本来打算走，听说纯纯在上钟，我就干脆等下看看真人长啥样。等了十几分钟，纯纯下钟了，人出来，一身白色外套，穿搭挺有气质，看到我还给我递根烟，我婉拒了。第一眼感觉不错，我问店长纯纯后面有么有钟，答案是没有，我决定上钟。纯纯补了个妆进来房间，真人和模卡照片差不多，不笑时候冷冷的，笑的时候很可爱。然后聊天，摸胸胸，胸很大很软，C罩杯，大腿和屁屁也肉肉的，摸起来很舒服，整个人感觉肉肉的，手感很好。补钙和反补也都可以，胸不敏感，胜在大…
#案件发生地 #白月光 #嫌疑人姓名 #身材 纯纯 #日期 10.26 #消费 628*2-200 #颜值 8 瓜子脸，真人比照片好看 #身材 d 168身高，有屁股有胸有腰，腿上肉正好，完美 #性格 小i 聊天可以叭叭一直聊，没有外表看着高冷 #上路 7 舌头短，不太会🐍，喜欢小口小口嘬 #中路 10 胸之大，一只手握不下，手感无敌，又大又挺 #综合评分 9 #详细体验 疯狂星期四中了白月光一个-200的券，挑选妹妹的时候在纯纯和小羊之间纠结了下，为了颜值和身材，还是选了纯纯。和客服约好头钟，沐浴喷香水后，遂驱车前往。准时到达店门口，店长给我开门带我进了房间。环境确实是不错的，因为第一次来，店长便带纯纯过来给我看一眼，见的纯纯的第一眼，就被她俘获了。妹妹进来后，因为这个房间的毯子有点味道再加上沙发床拉不出来，于是换了个房间，废了九牛二虎之力才把沙发床打开，以后就躺了上去。纯纯的性格比我想象中好了太多，因为提前知道了…
#案件发生地 白月光 #嫌疑人姓名 纯纯 #日期 10.18 #消费 899（工兵优惠） #人照符合度 8分 右下角模卡最像 脸会更柔和一点 #颜值 7.5分 人群里比较显眼那种 #身材 头身比很好 匀称有肉 穿鞋172 净身高168 #性格 落落大方 能主动破冰聊天贴贴 聊多了感觉是有点i的 #上路 7 能配合一直🐍 无烟味，技巧尚可。（会问，可以亲你嘛，让我有点意外😂） #中路 7.5分 说是B感觉B+快到C了，手感很不错，摸着又软又滑。（可惜妹妹不咋敏感，说她自己都找不到敏感点） #综合评价 4🌟 #详细体验 可能是比较投缘，聊了好一会小说，没看出来纯纯还有宅女属性。加分up 颜值很OK，喜欢御姐的可能直接就沉船了，肤白貌美大长腿，皮肤又凉又滑，一个字爽。 课表内容积极做，不会水钟，就算聊开心了，也会主动做课表，有合理要求也会配合，舔耳yyc都会试着去做。总体来说，吃这款颜的，新人老手服务党都很建议，操盘党就没那么尽兴。…
Channel name was changed to «深圳怦然心动女仆mmk报告馆»
Channel photo updated
Channel created
Showing the 7 most recent of 7 posts we hold for @szprxdmmk2. 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.
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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“深圳怦然心动女仆mmk报告馆” (@szprxdmmk2), 17 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/szprxdmmk2.
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.