Telegram RegisterThe public register of Telegram
Telegram profile photo for 深圳名师天团锐评

Channel

深圳名师天团锐评

@SZMSTTRP

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

9,360subscribers

-2,583 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-1002185787285
TypeChannel
Username@SZMSTTRP
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held59
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/SZMSTTRP

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 49% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 5 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@SZMSTTPD/64629 Aug 2026, 03:00 UTC@SZMSTTRP/1724 · this entry9 Aug 2026, 03:00 UTC1.00under a minute
@SZMSTTPD/64809 Aug 2026, 10:24 UTC@SZMSTTRP/1728 · this entry9 Aug 2026, 10:24 UTC1.00under a minute
@SZMSTTPD/649411 Aug 2026, 03:00 UTC@SZMSTTRP/1730 · this entry11 Aug 2026, 03:00 UTC1.00under a minute
@SZMSTTPD/656215 Aug 2026, 03:00 UTC@SZMSTTRP/1740 · this entry15 Aug 2026, 03:00 UTC1.00under a minute
@SZMSTTPD/659717 Aug 2026, 08:50 UTC@SZMSTTRP/1745 · this entry17 Aug 2026, 08:50 UTC1.00under a minute
@SZMSTTPD/661018 Aug 2026, 08:16 UTC@SZMSTTRP/1747 · this entry18 Aug 2026, 08:16 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@SZMSTTPD32 (8/8 hand-verifiable sample passed)1.00under a minute@SZMSTTPD (25–7)
@hmflzx14 (8/8 hand-verifiable sample passed)1.00under a minute@hmflzx (14–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 35 of the 39 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 113 comparable posts for this entry, running 29 July 2026 to 11 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 5 channels, the one whose matching posts we hold earliest is @hmflzx. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 12 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 5 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

9,36012,53910,949.56 August 2026 — 11,943 subscribers7 August 2026 — 11,944 subscribers8 August 2026 — 12,328 subscribers9 August 2026 — 12,539 subscribers10 August 2026 — 12,512 subscribers11 August 2026 — 12,274 subscribers12 August 2026 — 12,271 subscribers13 August 2026 — 11,847 subscribers14 August 2026 — 11,817 subscribers16 August 2026 — 11,785 subscribers17 August 2026 — 11,727 subscribers19 August 2026 — 11,703 subscribers20 August 2026 — 11,683 subscribers22 August 2026 — 11,648 subscribers23 August 2026 — 11,626 subscribers25 August 2026 — 11,594 subscribers25 August 2026 — 11,604 subscribers26 August 2026 — 11,603 subscribers27 August 2026 — 11,534 subscribers28 August 2026 — 11,507 subscribers29 August 2026 — 11,443 subscribers31 August 2026 — 11,326 subscribers1 September 2026 — 11,194 subscribers2 September 2026 — 11,113 subscribers3 September 2026 — 11,107 subscribers5 September 2026 — 11,118 subscribers8 September 2026 — 11,275 subscribers11 September 2026 — 10,972 subscribers13 September 2026 — 10,876 subscribers14 September 2026 — 10,816 subscribers16 September 2026 — 10,741 subscribers18 September 2026 — 10,689 subscribers25 September 2026 — 10,610 subscribers4 October 2026 — 10,585 subscribers8 October 2026 — 10,543 subscribers12 October 2026 — 10,534 subscribers14 October 2026 — 10,509 subscribers15 October 2026 — 10,504 subscribers16 October 2026 — 10,501 subscribers17 October 2026 — 10,498 subscribers18 October 2026 — 10,496 subscribers19 October 2026 — 10,491 subscribers20 October 2026 — 10,489 subscribers21 October 2026 — 12,488 subscribers22 October 2026 — 12,486 subscribers23 October 2026 — 12,405 subscribers24 October 2026 — 12,401 subscribers25 October 2026 — 12,394 subscribers26 October 2026 — 12,390 subscribers27 October 2026 — 12,388 subscribers28 October 2026 — 12,389 subscribers29 October 2026 — 12,387 subscribers30 October 2026 — 12,370 subscribers31 October 2026 — 12,368 subscribers1 November 2026 — 11,404 subscribers2 November 2026 — 9,385 subscribers5 November 2026 — 9,375 subscribers8 November 2026 — 9,365 subscribers12 November 2026 — 9,360 subscribers6 August 202612 November 2026
59 measurements spanning 98 days, net -2,583. 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 8,883–13,016 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 59
Measured (UTC)SubscribersChange
12 Nov 2026, 17:599,360-5
8 Nov 2026, 12:009,365-10
5 Nov 2026, 00:179,375-10
2 Nov 2026, 06:079,385-2,019
1 Nov 2026, 08:5611,404-964
31 Oct 2026, 10:5912,368-2
30 Oct 2026, 12:3712,370-17
29 Oct 2026, 14:3912,387-2
28 Oct 2026, 16:1112,389+1
27 Oct 2026, 17:3212,388-2
26 Oct 2026, 18:5812,390-4
25 Oct 2026, 16:5012,394-7
24 Oct 2026, 13:4612,401-4
23 Oct 2026, 13:4412,405-81
22 Oct 2026, 15:2812,486-2
21 Oct 2026, 08:4812,488+1,999
20 Oct 2026, 04:4010,489-2
19 Oct 2026, 02:3910,491-5
18 Oct 2026, 05:5610,496-2
17 Oct 2026, 08:0010,498first reading

Engagement

115 posts held, back to 29 July 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 64 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.60%
avg views ÷ 9,360 subscribers
Avg views / post
525
18 posts measured
Reaction rate
0.109%
reactions ÷ views · ER floor
Posts in window
18
of 115 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 18 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 11 November 2026
Posts held115 (29 July 2026 – 11 November 2026)
Views total9,442
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 00:00 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

Photos
5
Links
916

Lifetime counters from Telegram’s own channel header, read 13 November 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.

Video runtime
38s
Average length
19s

Measured directly from 2 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

8 reactions across 8 posts, in 1 kind.

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

Measured over the 115 most recent posts we hold, published 29 July 2026 to 11 November 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

Telegram’s own ‘edited’ marker: 0 of 18 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 02:48 UTC357 viewsread 13 November 2026

深圳名师天团锐评:https://t.me/SZMSTTRP 【所在位置】:广州天河 【老师艺名】: #巨乳紫苏 【联系方式】: @zisu6969 【验证留名】:匿名 【验证时间】:11.9号 【课程打赏】:3000 【颜值身材】:9.5分,屁股好大,胸好大,长的好看。很美。 【推荐程度】: (10分)没想到有这么好的服务 【服务内容】:荡妇剧本杀 【体验细节】: 在中国很好玩,,没想到有这么好的服务。角色扮演很接近。剧情丰富。我喜欢,我要的都满足了,做爱不累,全自动,很舒服。下次要玩双人的,紫苏说徒弟下个月就可以约双人了。不想回国了,要等玩双人再回去。 温馨提示: 报告仅供参考 注:(提交报告要提供相关证明,如聊天记录,付款记录等)

9 Nov 2026, 05:17 UTC453 viewsread 13 November 2026

深圳名师天团锐评:https://t.me/SZMSTTRP 【所在位置】:广州天河 【老师艺名】: #巨乳紫苏 【联系方式】: @zisu6969 【验证留名】:匿名 【验证时间】:11.7号 【课程打赏】:6000(破处,夜课) 【颜值身材】:9.5分,丰乳肥臀,手法强劲,重点胸部手感很好 【推荐程度】: (10分)对男人的把握是很绝对的,尤其东京浴强烈好评 【服务内容】:母子剧本杀 【体验细节】: 一上来就很入戏,对原剧本的把握度很深,从被抓包后的惊讶到找回掌权者姿态,跟着剧本走让人心甘情愿的臣服,前面的挑逗完了后就是沐浴环节,各种挑逗玩弄放松身体疲劳的同时对精神上的满足是更多的。沐浴挑逗完了就是东京浴了,那种滑溜溜的感觉让人欲罢不能,特别是“挤奶”的手法真的强烈刺激,生平第一次叫的那样狼狈,随后就是进房间捆绑中出后入......之类的,老师都会在规则内配合并最大程度去贴合我来制造爽感,四个小时眨眼过去,但对我这个第一回…

8 Nov 2026, 17:31 UTC377 viewsread 13 November 2026

深圳名师天团锐评:https://t.me/SZMSTTRP 【所在位置】:广州天河 【老师艺名】: #巨乳紫苏 【联系方式】: @zisu6969 【验证留名】:匿名 【验证时间】:11.6号 【课程打赏】:6000(破处) 【颜值身材】:9.5分,好看,大胸,很有弹性 【推荐程度】: (10分)温柔耐心,知性姐姐 【服务内容】:姐弟剧本杀 【体验细节】: 十月份就想要约苏苏姐姐的课了,奈何整个十月都没空,硬是拖到了十一月份。不过这等待都是值得的,各种服务一应俱全,爽到头皮发麻,推荐 温馨提示: 报告仅供参考 注:(提交报告要提供相关证明,如聊天记录,付款记录等)

8 Nov 2026, 08:48 UTC877 viewsread 13 November 2026

深圳名师天团锐评:https://t.me/SZMSTTRP 【所在位置】:福田车公庙地铁站旁 【老师艺名】:沐惋 【联系方式】:@fei02Z 【验证留名】:modafoker 【验证时间】:11月8号 【课程打赏】:10 【颜值身材】:9.8 【推荐程度】:9.9 (10分为满分) 【体验细节】:170 大高个,盘靓条顺,态度和服务都一级棒。老师靠着就很爱干净,课室高档整洁,交通也便利。力荐! 温馨提示: 报告仅供参考

1 Nov 2026, 06:26 UTC548 viewsread 13 November 2026

深圳名师天团锐评:https://t.me/SZMSTTRP #小小 #龙岗坂田 出击体验:第一次体验水床,姐姐的手法太厉害了,足交腿推胸推,太爽了,全身油滑溜溜的,姐姐的胸和屁股软软的,在身上滑来滑去,说话很有意思,终于体验了一把做av男主的感觉 联系方式: @xxiao02 中转频道: @xxiao41 温馨提示: 报告仅供参考

25 Oct 2026, 11:58 UTC≈1,040 views1 reactionsread 13 November 2026
Photo

深圳名师天团锐评:https://t.me/SZMSTTRP 【所在位置】: #深圳 #宝安 【老师艺名】: 小鱼 【联系方式】: @xiaoyu1085878956 【验证留名】:华强 【验证时间】: 10.25 【课程打赏】:350p 【颜值身材】:人照一致(照片美颜),娇小女友身材,嫩妹容颜 【推荐程度】: 9 .5(10分为满分) 【体验细节】:很早就中了半价券,因为老师期间休了一直没用,询问老师后发现还可以用,果断约好时间,出行碰到高峰期耽误了老师接近一个小时,见面后老师态度也很好,也没抱怨,进门看到老师很年轻,小屋子布置的也很温馨,是自己长住的地方,聊了一会就水费了,然后就去鸳鸯浴,老师说话也很温柔,床上也乖巧听话,姿势也非常配合,让做什么就做什么,身材小小的,整个人软软的压在身上抱着真的舒服,之后还会再来的(无kiss,🐍) 温馨提示: 报告仅供参考 注:(提交报告要提供相关证明,如聊天记录,付款记录等)

❤1

22 Oct 2026, 08:09 UTC541 viewsread 13 November 2026

深圳名师天团锐评:https://t.me/SZMSTTRP 【妹子花名】:雨珂 【联系方式】:@keke6645 【所在位置】:宝安 【修车水费】:p900 【照片相似】: 9成 【验证留名】:@h 8 【验证时间】:10.22 【服务内容】: 课表一致,69舌吻 【优点缺点】: 服务态度好,皮肤滑嫩嫩,身材标致,导师级别手法 【服务态度】: 10分 【颜值身材】: 9分 【推荐程度】: 10分 【体验细节】:9 【体验过程】: 颜值身材:高颜值,少女身材,和高中生一样 服务内容:课表都有,舌吻69都有 出击体验:进门初见,妹妹看着很幼嫩,妆容精致,颜值挺高,肤白貌美,客观来说,比频道视频更精致漂亮。坐下闲聊抽烟,再一次细看妹妹,娇小玲珑,长相幼态,眼妆很魅。那双眼睛真的很吸引我。遂交水费,拥抱,抚摸,袭胸,摸腿,宽衣解带,脱衣共浴,妹妹全身细皮嫩肉,皮光肉滑,全身走肥,比例也好,但很瘦,胸部不大,很粉嫩,乳头小小的粉粉…

21 Oct 2026, 03:01 UTC498 viewsread 13 November 2026

深圳名师天团锐评:https://t.me/SZMSTTRP 【所在位置】:宝安 【老师艺名】:地头蛇 【联系方式】: @dnydits52 【验证留名】: 液来丰乳腥(地头🐍🐹一窝版)@chu991022 【验证时间】:2026-10-19 【课程打赏】:900p(半价) 【颜值身材】:身材丰满,胸C/D,跟福利频道一样,颜值不错,看着嫩嫩,肤色正常偏白 【推荐程度】:9分 (10分为满分) 【体验细节】: 先说总结:深喉水多嫩妹,声音好听,情绪价值满满,主动话唠,喜欢丰满的完全可以试试,还有猫可撸🐱 然后就说点废话,一进门口初见蛇蛇,跟频道相差无几,人十分热情,没几句就把我哄成胚胎,然后拉我到床上直接让我上手,双手直接一手一个,左揉揉右搓搓,看着那双雪白的奶子变形,小鼠鼠不自觉地抬头,(是我出击少有的,一般情况下都是口的时候才硬,这次完全是由头硬到尾,)接下来交水费洗澡,幫洗的很徹底,大PP都拿出来帮洗能不干净吗嘻嘻,抹…

21 Oct 2026, 03:00 UTC595 viewsread 13 November 2026

深圳名师天团锐评:https://t.me/SZMSTTRP 【妹子花名】:雨珂 【联系方式】:@keke6645 【所在位置】:宝安 【修车水费】:p900 【照片相似】:9成 【验证留名】:@jjpp 【验证时间】:10月20号 【服务内容】: 课表一致,69舌吻 【优点缺点】: 服务态度好,皮肤滑嫩嫩,身材标致,导师级别手法 【服务态度】: 10分 【颜值身材】: 9分 【推荐程度】: 10分 【体验细节】:9 【体验过程】:人照约9成吧,标致嫩妹,肤色正常黄皮偏白点,身材苗条无赘肉,热情主动,健谈不冷场,乖巧听话姿势配合度高,口活女上优秀。 定位准确,准时到达目的地后遥控上楼,老师有提前留门,找到科室后轻推而入在客厅见到了老师,标致嫩妹,哈哈哈,一身性感衣服显得十分可爱又性感,目测身高162左右,打了声招呼后浅浅聊了会便赶紧交了水费一起洗浴,皮肤滑嫩,胸胸的手感棉花一样舒服,身材苗条无赘肉,待水温调好还会贴心的询问水温…

20 Oct 2026, 03:55 UTC542 viewsread 13 November 2026

深圳名师天团锐评:https://t.me/SZMSTTRP 【所在位置】:广州天河 【老师艺名】: #巨乳紫苏 【联系方式】: @zisu6969 【验证留名】:匿名 【验证时间】:10.17号 【课程打赏】:6000(包时) 【颜值身材】:9.5分,前凸后翘,爱笑,热情 【推荐程度】: (10分)演技真实,定制剧本内容斜街流畅,很会接戏,3小时剧本完全入戏,很过瘾。爱了爱了。 【服务内容】:按摩技师剧本杀+sm反转切换 【体验细节】: 我扮演男技师上门给女老板按摩(真实按摩),在按摩过程中,女老板一步步引诱男技师,抚摸胸部和私密部位,男技师为了得到五星好评,只好顺从,未曾想,女老板根本不满足,稍有不满意就对男技师罚跪,辱骂,踩踏,明知我有女朋友的情况下还妄想吃男技师鸡吧。哼,当然不从,眼见男技师不服从,女老板居然突变成骚母狗,祈求男技师为主人,勾引挑逗男技师,鸳鸯浴,东京浴,卑躬屈膝服侍男技师,乳交,魔棒,前列腺高潮,龟头…

20 Oct 2026, 03:54 UTC385 views1 reactionsread 13 November 2026

深圳名师天团锐评:https://t.me/SZMSTTRP 【妹子花名】:雨珂 【联系方式】:@keke6645 【所在位置】:宝安 【修车水费】:p900 【照片相似】:9成 【验证留名】:@jiangjun 【验证时间】:10月19号 【服务内容】: 课表一致,69舌吻 【优点缺点】: 服务态度好,皮肤滑嫩嫩,身材标致,导师级别手法 【服务态度】: 10分 【颜值身材】: 9分 【推荐程度】: 10分 【体验细节】:9 【体验过程】:进门洗漱不写了,咱们直接写重点,老师的口活是真好,光在口的时候就有点扛不住,稍微缓了一下以后就开始女上位,老师那里是真的紧,舒服的我连连叫停,老师很会迎合人,不管哪个姿势,感觉老师那里都在夹,太舒服了,好多姿势还没试,就被迫缴械投降了,必须二刷,下次再战三百回合。 优点缺点 :身材好 性格好 推荐程度 :10 老师联系 :@keke6645 优点缺点:无缺点。! 温馨提示: 报告仅供参考 …

❤1

19 Oct 2026, 08:13 UTC414 views0 reactionsread 13 November 2026

深圳名师天团锐评:https://t.me/SZMSTTRP 【妹子花名】:雨珂 【联系方式】:@keke6645 【所在位置】:宝安 【修车水费】:p900 【照片相似】:9成 【验证留名】:@ai 【验证时间】:10月19号 【服务内容】: 课表一致,69舌吻 【优点缺点】: 服务态度好,皮肤滑嫩嫩,身材标致,导师级别手法 【服务态度】: 10分 【颜值身材】: 9分 【推荐程度】: 10分 【体验细节】:9 【体验过程】:老师遥控上楼,进门后看到老师就知道是她了,她也认出我来了。第三次出击了🤣,本人和照片一样的,9成。浅谈一会交了修车费。直接一起洗澡了,洗完开始服务,老师🐻有个B也够用,毕竟年纪还小,需要大神去开发🤓,先舌吻,在口硬了就戴小雨伞步入正题了,进去后挺紧的,女上女后女下姿势都试了,老师全程都很配合,临走还抱抱。最后下楼吃个饭就回了,喜欢嫩妹可以冲,服务的话可以给老师提,能满足都会满足 优点缺点 :身材好 性格…

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

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 8 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.

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

“深圳名师天团锐评” (@SZMSTTRP), 9,360 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/SZMSTTRP.

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.