Channel
@SHDD333
On this record: Topic · Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry
11,857subscribers
+2,156 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001482983470 |
|---|---|
| Type | Channel |
| Username | @SHDD333 |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/SHDD333 |
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 61% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 02:36 | 11,857 | -223 |
| 16 Sept 2026, 18:21 | 12,080 | -206 |
| 14 Sept 2026, 21:41 | 12,286 | -70 |
| 13 Sept 2026, 07:16 | 12,356 | -223 |
| 11 Sept 2026, 13:19 | 12,579 | -218 |
| 8 Sept 2026, 20:02 | 12,797 | -201 |
| 5 Sept 2026, 15:40 | 12,998 | -133 |
| 3 Sept 2026, 18:14 | 13,131 | -84 |
| 2 Sept 2026, 12:48 | 13,215 | -65 |
| 1 Sept 2026, 11:13 | 13,280 | -43 |
| 31 Aug 2026, 07:47 | 13,323 | -23 |
| 30 Aug 2026, 10:22 | 13,346 | -121 |
| 29 Aug 2026, 09:14 | 13,467 | -125 |
| 28 Aug 2026, 08:34 | 13,592 | -54 |
| 27 Aug 2026, 08:57 | 13,646 | -57 |
| 26 Aug 2026, 12:12 | 13,703 | -127 |
| 25 Aug 2026, 12:49 | 13,830 | +4,772 |
| 22 Aug 2026, 13:06 | 9,058 | -338 |
| 18 Aug 2026, 20:45 | 9,396 | -238 |
| 15 Aug 2026, 17:48 | 9,634 | first reading |
146 posts held, back to 9 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 30 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 2 September 2026 |
|---|---|
| Posts held | 146 (9 August 2026 – 2 September 2026) |
| Views total | 23,151 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 2 Sept 2026, 20:24 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.
💃老师：#糖糖 🤖链接：https://t.me/shanghaidadao/12256 💒位置：#普陀 ------------------ 💌出击报告：中午开始约糖糖老师，约到2点课。当时也是抱着试试心态，按时到了课室地方，进出方便，课室环境不错。老师人对版说话也温柔，开始洗澡做服务。过程还是非常用心，课表服务全部做了，老师口活好完全没有刮的感觉。毕竟老师说以前在水汇上班几年，因本人喜欢享受服务，反正一点喜欢玩服务享受可以尝试吧！
💃老师：#南希子 🤖链接：https://t.me/shanghaidadao/12358 💒位置：#虹口 ------------------ 💌出击报告：第一次，心里有点担心，小区很安全也很好找，从进门就超级热情，瞬间感觉不紧张了，本来担心的照骗在看到老师后也全部烟消云散，给现金的时候还多给了一张，老师也及时告诉我，感觉很真诚，随后去洗，还主动提出帮我洗，还帮忙口，随后正餐更加牛，该有的都有，女上的时候非常爽，老师非常紧。非常好的一次体验，有女友的感觉，值得回锅！
💃老师：#蛋挞 🤖链接：https://t.me/shanghaidadao/12351 💒位置：#松江 ------------------ 💌出击报告：不记得几刷蛋挞了，最少七八次应该是有的。约好时间不用等，直接到了温存一会洗澡，水中萧管饱，前后洗的都很用心。 到床上前半场真是全自动，指滑🐻滑，边舔边摸，后半场姿势配合，骚话不断，直接缴械。搬砖攒钱冲
💃老师：#希诺 🤖链接：https://t.me/shanghaidadao/12307 💒位置：#浦东 ------------------ 💌出击报告：先跟随老师的指引来到课室，人照一致，之前的种种担心一扫而空。看着老师窈窕的身段的和俏媚的模样，我竟有些不知所措，老师见状主动牵起我的手到沙发上，然后直接骑跨在我身上，一对酥胸直接占据全部视线，再也移不开。 温存片刻兄弟已然坚挺，赶快脱衣洗澡步入主题。洗完出来老师已换好我指定的战袍在浴室外等待，薄纱的睡衣，全透的小内内，处处透露着诱惑。一把搂住老师的细腰抱到床上，顺势压上，小弟弟直接顶到了老师，老师很热情也不冷场，开始服务了，服务只要是课表上的ls都会配合，让腼腆的我一时间都不知道该怎么应对，口活很好无齿感，舌头还会在你龟龟上打转，帮我口的时候我一直看着她的脸庞，这个感觉太巴适了！口了好一会，感觉都要射了，就赶紧叫老师带上雨伞了，ls主动提出女上，很紧很会动，受不了，换传教，嗯…
💃老师：#麦提雅 🤖链接：https://t.me/shanghaidadao/12241 💒位置：#静安 ------------------ 💌出击报告：遥控进门看到老师身穿丝袜高跟，显得身材高挑。胸大，腿长，人比照片漂亮。洗澡仔细，洗完会帮忙擦干。技术很好，任盘，舌吻很通透。骚话不断，事后按摩也很解压，感觉物超所值。 优点：服务热情周到 教室环境好
💃老师：#豆豆 🤖链接：https://t.me/shanghaidadao/11741 💒位置：#普陀 ------------------ 💌出击报告：外地特意坐高铁来找豆豆，一开始担心人照差距大，见到老师觉得太值了 真三上！！进门之后老师主动拥抱贴贴 贴心的问喝什么帮你脱鞋脱袜 非常主动洗澡认真 课间休息还会按摩 舒服到差点睡着 讲多无谓 直接无脑冲就对了
💃老师：#樱樱 🤖链接：https://t.me/shanghaidadao/11747 💒位置：#普陀 ------------------ 💌出击报告：看到一个颜值很高的老师，依旧是遥控上楼，课室位置比较好找，进门看到老师穿着一件白色卡通吊带，纯天然奶子，摸起来很舒适，先是陪浴，动作很温柔洗的很认真，会确认水温合不合适。来到床上先是胸推调情，从上到下的轻舔，慢慢的过度到口，先是舌头挑逗前端再一口吞下，过程还会含情脉脉的盯着你，恨不得直接爆在老师口里，接下来戴好小雨伞开始正戏，女上开始，不过老师体力一般，摇了一会儿换我操盘，后入老师屁股非常大，配合上老师的轻哼，视觉体验拉满，后面换了几个姿势也是刚好足钟出水，这里表演一下老师出水之后也会陪浴，整体来说体验很好，热情活好，以后有空还会返。
💃老师：#大蜜 🤖链接：https://t.me/shanghaidadao/12298 💒位置：#浦东 ------------------ 💌出击报告：虽然走错了路但是老师还是很热情，一个身材苗条，一个大奶少妇，课表上的服务来一遍一边蛇一边做像皇帝一样的服务。养好精神下次包夜才能享受她们的热情。
💃老师：#橙橙 🤖链接：https://t.me/shanghaidadao/12385 💒位置：#闵行 ------------------ 💌出击报告：一个人很无聊，看到橙橙的频道是空的，于是主动约了包夜，言归正传，谈谈我对橙橙妹子的感受吧。 凹凸有致，是属于在一般人群里总是高挑得像是需要被仰望的存在，但这一晚她是属于我的，她慢慢低头，靠近我，安静地变得柔软。 老师看到我也很害羞，我看出来她需要引导，于是我给出了我们俩人熟悉的时间，让她稍微安心一点，她都把主动权交给我，像在说：你怎么安排，我就怎么靠近。 夜深，我们一前一后走进浴室。水声落下，她从浴室走出来，眼睛亮亮的，却带着一种不确定的羞意。我没有急于靠近，只是伸手牵住她，掌心碰到她背部的那一瞬，她微微一颤，呼吸悄悄乱了。 她的身体很敏感，像记住了我的温度。指尖落在她锁骨、腰窝，甚至只是顺着肩线轻轻滑过，她就会下意识缩着肩膀，眼神游移，像想逃，却又没逃。 她的颤抖不是拒绝，…
💃老师：#米朵 🤖链接：https://t.me/shanghaidadao/12365 💒位置：#普陀 ------------------ 💌出击报告：确定好时间开车前往，到了停好车，遥控指挥上楼，进门一看老师穿个高跟，包臀裙，奶子乳沟挤的很深，很大，身材也很火辣性感。一头黑色长发及腰。攀谈两句愉快交了水费洗澡，有陪洗，洗得很认真很干净，体验了鸳鸯浴，水中萧。整完后贴心拿毛巾擦干。然后上床先上下摸索，课表上的服务基本都有。直接开口了，不得不说口技还是了得赶紧叫停。看了看老师的小穴，小蝴蝶毛量少许，外白内粉比较有欲望。戴套女上进入，直接开摇，没喊停感觉要直接交代了。赶紧换个体位，传教士老师闭眼享受。还尝试了侧入，背枪，还是后面有感觉，老师主动下腰头发一撩直接开炮。最后换女上交代，裤裆湿了一片。总的来说服务好身材不错颜值都还算可以。值得出击
💃老师：#kimi 🤖链接：https://t.me/shanghaidadao/12336 💒位置：#闵行 ------------------ 💌出击报告： 约了老师后就马上过去了，进到课室，老师很好看，人照9分吧，和频道照片基本一致。老师身材非常好，没有赘肉，而且非常骚。一起洗澡，有水中萧，来到床上，有漱口水，可以蛇，口技很好，床上骚话不断，详细过程不表，最后后入出水，走人
💃老师：#冰冰 🤖链接：https://t.me/shanghaidadao/12312 💒位置：#宝山 ------------------ 💌出击报告：进门第一眼确定冰冰老师本人无疑，去掉滤镜就是本人，好看的脸，高挑的身材，美美的腿，全程冰冰服务，还是非常不错的。洗完澡擦干身子，主动提出给我口，于是在床上抱着冰冰让她给我口了一会儿，感觉很不错。欲望被点燃，戴套抱着冰冰就开始，插的时候还是比较湿润，在不断的抽插下，冰冰开始抱紧我，双腿也夹住了我的腰，受不了这么性欲爆棚的场景，我最终交货。值得再回锅。颜值身材没得说
Showing the 12 most recent of 146 posts we hold for @SHDD333. 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.
@SHDD333 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 62 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“上海大道出击报告” (@SHDD333), 11,857 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/SHDD333.
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.