😠😠😠😠😠😠😠😠😠😠 2026年11月18日—19日中國APEC峰會 😠😠😠😠😠😠😠😠😠😠
❤3😱2

Channel
@shenzhenreport
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
10,700subscribers
+479 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001964749673 |
|---|---|
| Type | Channel |
| Username | @shenzhenreport |
| Description | 深圳會所tg 資訊群:https://t.me/shenzhenfreenewtalk 免費資訊:https://t.me/shenzhenfreenew 技師報告:https://t.me/shenzhenreport 張飛報告:https://t.me/shenzhenzhangfeireport 懶人包:https://t.me/addlist/tW3VOUD27Vw1YWM1 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 55 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/shenzhenreport |
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 74% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 07:59 | 10,700 | +1 |
| 1 Nov 2026, 08:45 | 10,699 | +1 |
| 31 Oct 2026, 10:26 | 10,698 | +1 |
| 30 Oct 2026, 08:09 | 10,697 | -4 |
| 29 Oct 2026, 05:08 | 10,701 | +6 |
| 28 Oct 2026, 06:07 | 10,695 | +1 |
| 27 Oct 2026, 04:31 | 10,694 | +3 |
| 26 Oct 2026, 00:58 | 10,691 | +1 |
| 24 Oct 2026, 23:09 | 10,690 | +2 |
| 23 Oct 2026, 21:50 | 10,688 | +1 |
| 22 Oct 2026, 20:30 | 10,687 | -5 |
| 21 Oct 2026, 13:27 | 10,692 | -6 |
| 20 Oct 2026, 13:44 | 10,698 | +5 |
| 19 Oct 2026, 14:06 | 10,693 | +10 |
| 18 Oct 2026, 12:05 | 10,683 | +2 |
| 17 Oct 2026, 11:14 | 10,681 | +2 |
| 16 Oct 2026, 14:00 | 10,679 | +4 |
| 15 Oct 2026, 10:30 | 10,675 | +4 |
| 14 Oct 2026, 10:59 | 10,671 | +6 |
| 12 Oct 2026, 20:07 | 10,665 | first reading |
45 posts held, back to 22 May 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 39 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 29 October 2026 |
|---|---|
| Posts held | 45 (22 May 2026 – 29 October 2026) |
| Views total | 25,090 |
| Reactions total | 66 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Nov 2026, 19:37 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.
Lifetime counters from Telegram’s own channel header, read 3 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.
624 reactions across 45 posts, in 5 distinct kinds. The most used accounts for 51.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 323 | 51.8% | |
| 💩 | 295 | 47.3% | |
| 👍 | 3 | 0.481% | |
| 😱 | 2 | 0.321% | |
| 👎 | 1 | 0.16% |
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 45 of the 45 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 624 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 45 most recent posts we hold, published 22 May 2026 to 29 October 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.
😠😠😠😠😠😠😠😠😠😠 2026年11月18日—19日中國APEC峰會 😠😠😠😠😠😠😠😠😠😠
❤3😱2
@Luo_JiaJia_Jason 報告 #皇家国际 555555 報告:第一次寫真實體驗:指数668;照片8成似; 服務拉滿;大车,DL🐍很舒服;各种姿势配合,各种服务应有尽有,舌头👅和🐻很软;體驗非常好,兩次返食; #Luo_JiaJia_Jason報告
💩5❤2
@kk1231861 報告 #尚泉时代 555 福田区 身高 162 身材 9 配合 9 反馈 9 指数 667 水费 538 服务:骚舞秀,sm,丝袜秀,角色扮演,果冻,按摩,调情,漫游,舔背,69,舌吻,有调0011, 上班时间:晚班上班时间21点到6点 服务内容:骚,是真的骚!!水多,是真的超多水!!体验感完全不一样的技师,很会玩,去体验了一下,果然不一样!妹子进门第一感觉和照片8.9分似吧,其实本人还更漂亮些,很热情,颜值很在线,身材很好,经常健身的女的就是不一样,而且下面很紧,进门就给弟弟马上硬了起来,接着就是一系列的调情:丝袜秀,漫游,舔背,69,珍珠等,只能说真的好骚好会,,穿着丝袜好性感,让人欲罢不能,主要是这妹子服务很耐心,甜美可爱,跟她聊天,聊的很舒服, 特别有女友感,玩起来就像自己的女朋友,是我见过最会玩的技师了!推荐!! #kk1231861報告
❤15💩5
@hugo6644 報告 #皇家国际 1111111 淼淼 指數:667 身材:C+、皮膚白滑 樣貌:7-8 / 10 消費:550 看到師兄說她是毒龍之鬼,約起來一試究竟。一進來直接用她嬌滴滴的娃娃音邀我摸她綿軟的C胸。雙方都全身解甲,開始調情0011,好舒服。之後到毒龍,用她舌頭的綿軟玩毒龍真沒得輸,直達最深處。隨後向小妹妹進攻,摸兩下便濕透,然後她主動轉身 69互舔,稀毛鮑魚無異味,挺好吃。最後出水還不小心餵她吃了一點😅 #hugo6644報告
💩12❤2
@AALL20066 報告 #皇家国际 88888 小情人 类型:御姐 价格:530 态度:活泼开朗 环境:会所,舒适 位置:深圳罗湖区 服务:指数668,调情,按摩,漫游,bt,十指谈琴,全身漫游,调情0011,69 最近新发掘的一个会所红牌资源,颜值中上非常年轻,前面的大胸很大,纯天然很有弹性,真胸摸得很有手感,目测24出头的样子,一激动就摸着大波舌吻,妹子放的很开,没想到那么配合。全程全果FW,蛇稳非常给力小舌头很软,可大车特车、69舔鲍鱼小试了一会无异味,基础服务,mb,过s,调q,漫游,胸t,都有,特别是胸推简直不要太舒服,很滑,又有弹性,把老二包裹的刚刚好,美女的屁股也非常翘,捏着屁股亲嘴也很有感觉,整体668的服务还是很刺激的,最后选择熊出水全程下来让人流连忘返,服务指数是668,出水在胸上。值得返食,喜欢特色罗湖服雾的老哥们不容错过。 #AALL20066報告
💩13❤7
@hugo6644 報告 #皇家国际 早班 222222 西西 年紀 30左右 顏值 8 相似度 80% 身高 165-168 指数 668 可94 服務時長不偷鐘 水費 530 成熟御姐一枚,身材很頂,有C,屁股圓肉感足。皮膚超滑超嫩,保養得沒話說。口活技巧純熟到位,每一下都頂到最深,態度又好,完全不敷衍。 #hugo6644報告
💩20❤5👍2
@AS4645789 報告 #港都 555 指数 668 服务时长 足钟 水费 520💰 今天打算去找个高指的试下之前 有群有推荐一个港都水会的555指数有668,跟技师约的19:30 ,今天下班下的早就直接打车到海外联谊大厦了技师告诉我电梯上3楼就是水会了 出了电梯就看到了 拿了手牌直接进去了 冲完凉进房跟部长说约的555 房间的环境是按摩床的 那种 不是榻榻米 技师进来跟我打了招呼叫了一声亲爱的宝贝 直接抱着我 坐在我的腿上 跟我亲了几口 态度不错 然后就说起钟了 然后就给我脱了上衣服 问亲爱的宝贝 要不要给我放松按一下 还是直接做服务 我想了想 好多天没有出水了 就直接做服务吧 然后技师给我脱了裤子 她也脱光了 直接就给我开始做波推了 大概34C左右 然后就开始环游过水了 然后就开始做毒龙舔蛋 舔棍棍 口活还可以 感觉有点舒麻的样子 然后就开始做了69…
💩9❤6
@kk1231861 報告 #尚泉时代 晚班 520 颜值:8 身材:皮肤白滑 D胸 身高:160+ 态度:配合度高 騷 指數:92 水費:538 類型:年轻嫩妹04年的 女友感觉 服務:过福田玩看到个水会随便进去体验下,没想到有惊喜,晚班还能遇到嫩妹,总结全身漫遊,調0011,过水 有大车 态度很好,温柔 声音好听 叫床也很销魂 足钟 值得反 #kk1231861報告
❤7💩4
@tyrewq1210 報告 #富源 9999 指数:668 费用:550 人照相似度:90% 年龄:27左右 皮肤:滑 熊🐻:C+ 详情:今天预约了9999,看奶子挺大的,我喜欢,,这颜值和🐻还是很稳的。见面后先聊了会天,然后便被她其在了身下,深喉推到底,来了波蛇纹,品尝了一番洗面奶,然后便翻身向上继续亲,手在🐻和下面间来回轻抚。本人喜欢吃鲍鱼,69操作8分钟,在来个0011,然后便是常规的一些🐻推,手指漫游服务,最后在668和大车期间成功出水。 总结:颜值不错,🐻純天然的,喜欢🐻的值得推荐, 返食率:95% #tyrewq1210報告
💩9❤2
@kk1231861 報告 #富源 晚班 166 颜值:8 身材:皮肤白滑 D胸 身高:160+ 态度:配合度高 騷 指數:667 水費:530 類型:性感御姐 女友感觉 服務:全身漫遊,毒龙,調0011,过水 大车舒服 态度很好,温柔 叫床好销魂 足钟 值得反 #kk1231861報告
❤6💩3
@AALL20066 報告 #富源 555555 价格:550 指数:668 颜值:8分【热情女友】 和照片相似度:80% 年龄:26 车灯:36C灯原装 服务:指数668,按摩,漫游,舔背,调情,有调0011,舌吻 配合度高 性格:风趣幽默脾气好 今天放假无聊想着去出击玩一玩,然后朋友推荐的这个美女,跟美女微信上简单问了一下内容,随后约好时间就直接出发,到了地方在房间等了几分钟,美女就来了,进门直接跟她舌吻,颜值跟身材都不错,随后简单按摩进入主题,我比较喜欢躺着享受,躺尸就可以了,美女很主动,服务过程中很认真,服务也到位,还可以跟美女69,水很多而且还骚的一批,最后直接磨棒起飞,躺了一下买单550,服务不错,后续还可以继续返食,服务也是比较开放 #AALL20066報告
❤6💩4
@BGB_66 報告 #心怡 222 身材高挑大长腿,净身高168,舌吻😘很舒服,吃🐟很敏感一直在颤抖,指数667,水费500,性价比高。 #BGB_66報告
💩5❤2
Showing the 12 most recent of 45 posts we hold for @shenzhenreport. 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.
We recorded 1 post on @shenzhenreport as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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.
@shenzhenreport named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“深圳會所技師報告” (@shenzhenreport), 10,700 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/shenzhenreport.
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.