Channel
@SZDAD666
On this record: Growth · Engagement · Posts · Citations · Cite this entry
4,292subscribers
-1,619 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001571786864 |
|---|---|
| Type | Channel |
| Username | @SZDAD666 |
| Created | Between 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/SZDAD666 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 04:22 | 4,292 | -1,337 |
| 8 Aug 2026, 17:42 | 5,629 | -282 |
| 8 Aug 2026, 02:18 | 5,911 | first reading |
20 posts held, back to 20 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 5 pagesof 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 26 July 2026 |
|---|---|
| Posts held | 20 (20 July 2026 – 26 July 2026) |
| Views total | 5,723 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 04:03 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/SZDAO2/2359 💒位置：#南山 ------------------ 💌出击报告：进门后先没有急着脱，而是靠过来用气音调情，声音又软又黏，说的话从夸我到直接描述她想怎么被碰，眼神还带着笑，气氛很快就被她带偏。 舌吻是她主动凑上来的。吻得很深，舌头灵活地搅在一起，津液交换得又湿又响，亲到两人都有点喘才分开，嘴角还连着丝。黑丝腿在这个过程中一直若有似无地蹭着我的小腿，触感光滑。真正进入69时她把丝袜留着，膝盖分开跪好。上面是她认真吞吐的嘴，下面是已经湿润的私处贴近，我能清楚感觉到她的温度。调情的话在这个姿势里也没停，她会边含边含糊地问“喜欢这样吗”，又色又密。丝袜的视觉、舌吻的深、69的紧密、再加上全程不停的调情，整场被她做得又有氛围又有实质。南山这边能约到这种会穿丝袜、会亲、会做69还一直说话的，体验感确实在线。结束时她坐在床边慢慢卷丝袜，腿上还留着刚才的水光。 报告提…
💃老师：#天爱 🤖链接： https://t.me/SZDAO2/2350 💒位置：#龙岗 ------------------ 💌出击报告：就是嫩妹那一挂，脸干净身子也白。进浴室后她把水温调好，自己先跨进去，再伸手把我拉进来。陪浴的过程她很自然，泡沫从胸口抹到小腹，偶尔用湿滑的身体贴上来轻轻磨，蒸汽里全是她清浅的呼吸声。水中萧是她突然低头开始的。热水里她把整根含进去，口腔和水流一起包裹，吸吮时会有细小的气泡往上冒。因为在水下，她的动作变得更慢更重，每一次深吞都能感觉到喉咙的收缩，退出时带出的水线混着唾液，视觉很有冲击。从浴缸出来后她直接跨上69互舔。上面是她继续用嘴照顾，下面是她已经湿润的地方完全贴过来，主动扭腰把最敏感的位置送到舌尖。互舔的节奏被她掌控得很好，她含得深的时候下面也会夹得更紧，两边同时传来的刺激直接叠在一起。嫩妹的脸和身子、陪浴的亲密、水中萧的独特触感、69互舔的紧密，整场又湿又密又有反差。结束时她头发还在滴水…
💃老师：#芝芝 🤖链接： https://t.me/SZDAO2/2353 💒位置：#南山 ------------------ 💌出击报告： 进门后衣服一脱，三点粉得非常明显。白净的皮肤衬得那三点粉嫩扎眼，胸前的颜色和下面一致，光是看着就让人呼吸重了几分。她先上手做胸推。软肉把整根完全夹住，中间那道沟又热又紧，上下套弄的时候还会故意用力挤压，顶端一次次从乳肉里露出来又被吞没。她自己也看着，偶尔低头用舌尖舔一下，动作又骚又专注。真正坐上来时她选了泰山压顶。整个人的重量压下来，粉嫩的私处把整根一点一点吞进去，直到完全坐实。她不急着大幅动作，先用身体压着慢慢研磨，让人清楚感觉到被她又热又软的内部完全包裹。等适应了才开始有节奏地起伏，每次落下都又深又重，三点粉的视觉在这个姿势里被放大到极致。漫游的方便、三点粉的强烈视觉、胸推的扎实包裹、泰山压顶的重量与深度，整场过程被她做得又色又有冲击力。结束的时候她还保持着坐着的姿势喘了几口气，粉嫩…
💃老师：#红红 🤖链接： https://t.me/SZDAO2/2367 💒位置：#龙岗 ------------------ 💌出击报告：红红一进门就上手做全身漫游，掌心从胸口滑到小腹，再绕到大腿内侧，力道不重却很有存在感，每到敏感处都会多停留几秒。吹箫是她自然跪下开始的，含进去后节奏稳定，舌头配合着吸吮，深浅切换得很顺。真正坐上来时她选了观音坐莲，面对面把整根吞没，双手环着脖子，自己慢慢扭腰。体位又密又深，她里面的温度和收缩都传得很清楚。全身漫游的铺垫、吹箫的细致、观音坐莲的亲密，整场过程连贯又舒服。 报告提交机器人：@BT888866bot 报告提交条件：需要提供约课记录及付款记录验证
💃老师：#小雅 🤖链接： https://t.me/SZDAO2/2363 💒位置：#龙岗 ------------------ 💌出击报告：老师把衣服全脱干净后，先低头专心舔蛋。舌头又软又湿，把两边都照顾到，轻轻吸吮时还会用鼻尖蹭，弄得人又胀又麻。胸推紧接着上，软肉把整根夹住，上下缓慢套弄，中间那道沟还时不时用力收紧。她会低头看自己的动作，偶尔用舌尖舔一下顶端，视觉和触感一起叠加。后来她转身改成臀推，柔软的臀肉紧紧贴住，前后磨动时力道又稳又沉，和胸推完全不同的包裹感。最后是裸吹，什么都没穿直接含到底，喉咙收缩得又深又紧，吸吮的声音在安静里特别清晰。舔蛋的细致、胸推的柔软、臀推的力度、裸吹的直接，整场被她做得又全又色。结束后她靠在旁边喘气，身上还带着刚才的温度。 报告提交机器人：@BT888866bot 报告提交条件：需要提供约课记录及付款记录验证
💃老师：#瑜晴 🤖链接： https://t.me/SZDAO2/2376 💒位置： #南山 ------------------ 💌出击报告：瑜晴是个嫩妹，脸看着就很新。她先凑过来舌吻，吻得又深又湿，舌头主动往里钻，亲到两人都有点喘才分开。接着直接无套口，口腔热乎乎的，含住后认真吞吐，没有一点隔阂。很快她自己就水多得明显，湿意顺着大腿往下走。最后摆成69，上面继续含，下面把最湿的地方送过来，水声响得清楚。舌吻的密、无套口的真实、69时她水多的反应，短短一场又嫩又湿。 报告提交机器人：@BT888866bot 报告提交条件：需要提供约课记录及付款记录验证
💃老师：#陈佳曼 🤖链接：https://t.me/SZDAO2/2395 💒位置： #宝安 ------------------ 💌出击报告：老师踩着细高跟鞋进来，步伐又稳又慢，鞋跟敲在地板上的声音特别清晰。她先让我躺好，自己俯下身专心舔咪咪，舌头又软又湿，绕着乳尖打转，时而轻咬时而吸吮，弄得两边都又红又敏感。 真正进入后各种姿势她都很配合，想侧就侧，想背就背，想让她自己动她就主动扭腰。高跟鞋一直没脱，腿抬高的时候鞋尖在空气中轻轻晃。服务态度明显很好，全程都在根据反应调整，又认真又放开。 高跟鞋的声音、舔咪咪的细致、再加上她各种姿势的高配合，短短一场就很满足。 报告提交机器人：@BT888866bot 报告提交条件：需要提供约课记录及付款记录验证
💃老师：#欧阳楚楚 🤖链接： https://t.me/SZDAO2/2401 💒位置：#南山 ------------------ 💌出击报告：黑丝包裹的腿一迈进来，欧阳楚楚的丝袜诱惑就已经到位。她没多话，直接跪低身子开始花式吹箫。舌头、嘴唇、喉咙轮流切换，时而深吞到底，时而只用舌尖快速弹弄，变化又密又准。因为她本身水多，光是被含着下方就已经湿透，水液顺着丝袜大腿往下淌，视觉和触感一起往上冲。整场吹得又花又湿，结束时丝袜还亮晶晶的。 报告提交机器人：@BT888866bot 报告提交条件：需要提供约课记录及付款记录验
💃老师：#陈一一 🤖链接： https://t.me/SZDAO2/2409 💒位置： #宝安 ------------------ 💌出击报告：老师穿着完整制服推门进来的，裙子短得刚好卡在大腿中段，下面是超薄情趣丝袜，走路时缝隙若隐若现。她没有急着开始，先站在床边慢慢转了一圈，让制服的剪裁和丝袜的光泽完全展示出来，眼神却带着点挑衅。真正进入后她很放开，全套姿势几乎都试了一遍。从背后位时丝袜腿被高高抬起，到侧入时制服衬衫还半挂在身上，再到她自己骑乘时裙子掀到腰间，每一个变化都带着明确的视觉刺激。情趣丝袜全程没脱，布料被水液浸湿后紧紧贴在皮肤上，摩擦感特别明显。她会根据姿势自己调整角度，该主动的时候毫不含糊，该配合的时候也完全放松。制服的束缚感、丝袜的光滑、再加上姿势的连续切换，整场又色又有层次。结束时她靠在床头整理有点乱的衣领，丝袜还留着湿痕。 报告提交机器人：@BT888866bot 报告提交条件：需要提供约课记录及付款记录
💃老师：#曼妮 🤖链接：https://t.me/SZDAO2/2422 💒位置：#龙岗 ------------------ 💌出击报告：浴缸里的水刚调好，曼妮就伸手把我拉了进去。蒸汽升起来的时候她已经贴在身后，双手从腰侧滑上去，边抹泡沫边用气音在耳边调情，说的话又软又直接，很快就让人呼吸乱了。指划是她转身面对面后开始的。手指灵活地探进来，不急不躁地打圈、抽送，专挑最有感觉的位置反复磨。水液混着浴缸里的温水，声音变得很清晰。她一边做一边观察我的表情，时不时问一句“这里可以吗”，语气却带着笑。陪浴的身体贴近、指划的精准力道、全程不停的调情，把人从放松一点点推到完全失控。出来的时候腿都是软的，她还擦着头发看着我笑。 报告提交机器人：@BT888866bot 报告提交条件：需要提供约课记录及付款记录验证
💃老师：#李文君 🤖链接： https://t.me/SZDAO2/2442 💒位置： #宝安 ------------------ 💌出击报告：老师穿着黑丝进来，腿又直又亮，丝袜诱惑直接拉满。她没急着脱，先慢慢走了两步，让丝袜的光泽和脚背的弧度完全展示出来，光是看就已经硬了。口活真的一流。她跪下来含住后，舌头灵活得不像话，先绕着顶端细细舔，再整根吞到底，喉咙有节奏地收缩，吸吮又深又稳。中间还会用舌尖快速弹弄最敏感的地方，变化又多又准，完全不单调。最绝的是回马枪。她突然转身背对我，还是那双黑丝腿，自己把整根坐进去后开始前后扭腰。丝袜摩擦的触感和她里面的紧致混在一起，每一下都又深又狠，还能用手向后撑着控制节奏。口活的细致铺垫加上回马枪的视觉和深度，整场又色又过瘾。 报告提交机器人：@BT888866bot 报告提交条件：需要提供约课记录及付款记录验证
💃老师：#小优 🤖链接：https://t.me/SZDAO2/2455 💒位置：#南山 ------------------ 💌出击报告：小优拉我进浴缸做鸳鸯浴，热水里她主动贴过来，身体湿滑地磨蹭，泡沫顺着胸口和大腿往下淌，亲密感很快拉满。从水里出来她直接跨上69，上面认真吞吐，下面把最湿的地方贴近，两边同时伺候，水声和呼吸混在一起。最后是足交，白净的脚丫柔软灵活，脚心上下摩擦，脚趾还会轻轻夹紧，力道稳又带感。鸳鸯浴的缠绵、69的夹击、足交的技巧，短短一场就很完整。 报告提交机器人：@BT888866bot 报告提交条件：需要提供约课记录及付款记录验证
Showing the 12 most recent of 20 posts we hold for @SZDAD666. 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.
Citation-graph rank — 44,120 of 1,350,102entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“深圳大道出击报告” (@SZDAD666), 4,292 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SZDAD666.
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.