Channel
@Szdbbgq
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,724subscribers
-26 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002319335976 |
|---|---|
| Type | Channel |
| Username | @Szdbbgq |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/Szdbbgq |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 08:57 | 1,724 | -5 |
| 10 Aug 2026, 00:02 | 1,729 | -20 |
| 7 Aug 2026, 01:46 | 1,749 | -1 |
| 6 Aug 2026, 20:17 | 1,750 | first reading |
21 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 2 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. It is computed over the 6 of 21 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 21 (20 July 2026 – 7 August 2026) |
| Views total | 4,843 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 17:38 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.
6 reactions across 5 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 100.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 6 of the 21 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 21 most recent posts we hold, published 20 July 2026 to 7 August 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.
【深圳电报】： t.me/xnrrc 【时间】：8月6日 【老师】：叶灵儿 @yelinger68 【留名】：陈清泉 【人照】：真人更漂亮 【颜值】：极品巨乳美女 【身材】: 大长腿，模特身材 【过程】：看到灵儿妹妹开双飞一直心痒难耐，刚好今天有空，预约好时间后出发，第一次尝试双飞，怀着激动的心情出发甚至提早半小时到达了，进门就遇到灵儿妹妹热情地打招呼，然后坐下沙发交上水费开始叫如烟姐姐过来左拥右抱，两个老师的奶子是真的好大啊，又大又软还挺，摸着摸着两姐妹也是很自然地开始掏我大吊，我说两位都是骚姐姐，让灵儿笑了好一会，再你侬我侬一会后就被拉去鸳鸯浴了，灵儿水中萧，如烟在后面用她的大奶子胸推我，帝王般的享受，洗浴结束后回到床上开始服务，可以挑自己喜欢的衣服，让如烟选了秘书包臀装，再搭配个眼镜非常有韵味，灵儿则选了黑色蕾丝调皮可爱，接下来服务开始波推，指滑，过水应有尽有，吹箫时冰火两重天，左右舔杆两姐妹也是尽显默契，之后带上小雨伞…
【深圳电报】： https://t.me/Szdbbgq 【时间】：8月6号 【老师】：鱼幼薇 【电报】：@yyw111 【留名】： CF 【人照】：一致 【颜值】：一张顶级御姐爽脸 【身材】: 165左右身材很好纤细 【过程】：符合眼缘，跟鱼幼薇老师约了PP，说实话是因为怕被秒，进门眼前一亮不得不赞叹自己的眼光，高挑修长的身材却长了一张御姐脸，进门就差点沦陷导致我社恐犯了，放下东西交了水费就被引导着去共浴，鱼幼薇老师直奔我的鸡儿里里外面洗了一遍 到了床上，我提出先熟络一下，doi才更有感觉，我们相拥，在耳边窃窃私语，对视后开始亲吻，涵妹的吻湿润、热烈、津液在口腔中交换，舌头不断挑拨我的神经。突然停下，我问到“哪里最敏感” 老师说都还好，我不信便像个侦探逐一开始试探最敏感的地方才哪里，从耳朵、脖子、胸，每探索一处都能明显感觉到身体的颤抖，我笑着挑逗到“这就是都还好呀”，老师说我好坏，那我今天便一坏到底嘿嘿 此处省略一万字 明明是…
【深圳电报】： https://t.me/Szdbbgq 【时间】：2026年8月5日 【老师】：柯美 【电报】：@kemeixa 【留名】： 最初 【人照】：8 【颜值】：9 【身材】: 9 【过程】：和老师约了两个小时包时加sm，老师工具很多，全程骚话执导，在老师面前我就跟菜鸡一样，老师教了很多动作，态度很好，也不嫌烦，从床上换到🪞跟前，换到沙发，第一次被秒了，以为自己不行，老师说很正常，刚开始以为老师只是安慰我，没想到第二次很持久，超级法规，老师科室环境卫生整洁，高档公寓，进出方便，不登记，会泡茶，东西都是一次性，人也高挑有一米七，妥妥御姐范，制服挑选度高，一双黑丝大长腿，足够我回家意淫好久，还拍了色色小视频……你们脑补哈哈……会二返
【深圳电报】： https://t.me/Szdbbgq 【时间】：8.5 【老师】：南南 【电报】：@fe13421 【留名】：drunk 【人照】：9 【颜值】：9 【身材】: 9 【过程】:给了定金，发了位置，等老师上门。打开门，老师那双迷人的大眼睛瞬间锁定我，她穿着一套紧身OL装，黑色吊带丝袜勾勒出修长美腿，脚踩米黄色细跟高跟鞋，性感得让人血脉喷张。小头当场就硬得不行，裤子都快撑爆了。我一屁股坐到沙发上，手忍不住滑向她那光滑的黑丝美腿，柔腻的触感让我心跳加速，边抚摸边交了水费，脑子里已经开始幻想接下来的狂野画面。 先去洗澡，一边帮我洗澡一边挑逗我，十分钟左右到了房间，房间的空调有点冷，我们先在床上紧紧相拥取暖，老师的体香混杂着淡淡的香水味钻进鼻子里，撩得我心痒难耐。她突然抬起头，用那双会说话的大眼睛直勾勾地盯着我，下一秒，主动送上湿热的舌吻。她的小舌头灵活得像条小蛇，在我嘴里肆意缠绕，挑逗着我的每一根神经，吻得我…
❤1
【深圳电报】： https://t.me/Szdbbgq 【时间】：8.4 【老师】：深大学妹 【电报】：@Xx12311111 【留名】： 王兄 【人照】： 9.5 【颜值】：9 【身材】: 9 【过程】：第一次上课，心情既兴奋又紧张，怕踩雷，但总体来说体验很不错，约好老师的头课，按约定的时间到达老师指定的地点，位置很好找，停车也方便，到楼下后老师远程遥控上楼，进门就看见老师穿着一件白色的衬衫，两只奶子一晃一晃的，第一感觉就是真人比照片上要嫩，身材丰满，态度也很热情，在大厅沙发上闲聊了一会交了水费，然后去浴室里洗澡，老师陪浴很仔细，AB面都有认真洗，在厕所明亮的灯光下打量着老师的body，真才实料没得说，两只大白兔很柔软，也很敏感，碰一下奶头就淫叫了起来，果然是敏感肌，屁股有肉，拍起来duangduang的，非常有感觉，洗完后就走了出来，回到客厅，老师全自动帮擦干，服务意识非常到位，擦着擦着突然被老师的大蟒蛇袭击，🐍了一…
【深圳电报】： https://t.me/Szdbbgq 【时间】：7月27号 【老师】：护士 【电报】：@Nshs39 【留名】： 海龙 【人照】：人照一致 【颜值】：嫩妹一枚非常漂亮很爱笑 【身材】: 身高165左右，身材偏瘦，可以说非常瘦了。 【过程】：在群里刷到护士老师的照片，一眼就相中了，一看就是我的菜。今天有时间决定出击一把。提前约好时间，按照指挥走进教室。开门的一瞬间。一个小小的可爱的美女出现在我眼前。感觉和照片没什么两样。真的很漂亮很可爱。天气太热，出了一身汗。所以进屋就想赶紧洗个澡。拉着老师走进浴室，两个人一起洗了起来。洗完澡，给老师换上我买的情趣护士套装。虽然老师很瘦，但是倒也蛮适合她的。拎着老师到镜子前欣赏了下。老师还害羞的说跟自己上班穿的不一样呢，进入正题，抱着老师上床躺下。想进行舌吻。老师还是有一些害羞。有一些放不开。于是我开始主动了起来。终于在我的不解努力下，撬开了老师嘴唇，激情热吻起来。吻了一会。…
【深圳电报】： https://t.me/Szdbbgq 【时间】：9/1 【老师】：福田岚岚 【电报】： @lanlananqq 【留名】：远 【人照】：9 【颜值】：9 【身材】: 9 【过程】：临时约课，有空位去了，本以为是照片，但没想到绝绝子，真的很惊艳。本人超好看。身材也不错。服务也很到位。细节不多描述了，体验过会翻，希望老师不要太火呀。
【深圳电报】： https://t.me/Szdbbgq 【时间】：9.13 【老师】：南山小怡18岁个人兼职 【电报】：@yyy66116 【留名】： lance 【人照】：8 【颜值】：9 【身材】: 5 【过程】：遥控上门，进门没任何迎接，妹子躺床上抬头瞅一眼就继续低头玩手机，去洗澡，洗澡上床，口一分钟就带T，全程无任何情绪价值，近乎死鱼，不给亲就算了，抱都拿膝盖顶着你，不给身体接触。体毛挺重，小臂的毛挺长，身体有斑有疤还不白。看她自己的报告，应该都是别人代写的，千万别信！走的时候都不送一下，就抬头瞅一眼，就维持进门时的玩手机姿势。大家避雷！
【深圳电报】： https://t.me/Szdbbgq 【时间】：8月2号 【老师】：鱼幼薇 【电报】：@yyw111 【留名】： 靓仔 【人照】：认真一致 【颜值】：颜值上等，脸型瓜子脸，黑色紧身衣一套，气质佳。 【身材】: 身高167，很瘦，很御姐 【过程】：群里发了照片很骚很诱人很好看的一位老师，抱着试一试的态度，联系了，马上出击。见面后不是照骗，照片是有化妆，除此之外就是本人了，老师穿着黑色紧身装，黑色蕾丝小内内（事后注意到的），后面细看老师妆容真的好勾人，不得不说，颜值是真的高。交完水费，一起洗浴，浴室挺小的，老师有帮洗，洗完一起进到被窝，我开始主动舌吻，闭眼享受，手也抚摸着老师的小露尖尖，然后继续往下探索。再然后老师开始口活，时间也蛮久的，我也稍微浅尝老师下面的咸甜，没啥味道。差不多就开始正事，传教士起手，趴老师身上舌吻，下面抽插不停，老师呻吟不断，换后入之前，把客厅的镜子搬了进来，对着镜子后入，老师害羞一直不抬…
【深圳电报】t.me/xnrrc 【老师花名】林娇娇 【联系方式】@nen369888 【验证留名】AA 【验证时间】8.1 【所在位置】外出南山 【修车价格】1600 【颜值身材】9 【服务内容】洗吹做，69，kiss 【服务态度】10 【优点缺点】还是那么嫩，一线天 【推荐程度】10 【体验细节】上次找已经是去年的了，今天刚好有空约了娇娇上门，提前发了路费，到达地方，我下楼接，妹妹还是一样的可爱，也比之前瘦了，妆容也比我去年好看一点了。到房间之后交了水费，一起脱衣沐浴，洗完穿上了我买的黑丝，先舔👅🐻再往我二弟慢慢的抚摸和口，口得也挺舒服的，先传教士，再女上，抱在怀里，汗流浃背，低声娇喘，嘤嘤燕燕嘤嘤，激情来临时的颤抖，迷离的眼神，在那一刻沉沦了…，还得是娇娇，舒服极了。 相聚时间如此短暂，几十分钟欢愉，是极大的满足。有时间再返。
【深圳电报】： https://t.me/Szdbbgq 【时间】：7.30 【老师】：南南 【电报】：@fe13421 【留名】： 南南 【人照】：9 【颜值】：9 【身材】: 9 【过程】： 大热天的大中午来上老师的头课，一进门人照一致，老师比照片好看，真的比照片好看，身材比较瘦吧，坐进屋子，老师递来冰的矿泉水，然后去放水洗澡，有陪浴和水中萧，口的很舒服，差点交代在浴室，洗完老师帮忙擦干，趴着，老师的吸皮真的吸力很大，搞得我很痒，还有毒龙我没要，跪着翘起屁股老师从下面钻了过来，口jj和蛋蛋，特别爽，差点交代了，翻身正面，老师继续口，很舒服，多次深喉，差点又交代了，戴套老师坐了上来很紧水很多，老师基本上要求都会满足，我还添加了点剧情绿帽老公（没别的在教室，大家放心）在隔壁，氛围感拉满，真的很推荐，大家可以无脑冲！ 【优点】：配合度高，骚 【缺点】：没有饮料，只有矿泉水
【深圳电报】： https://t.me/Szdbbgq 【时间】：7.29 【老师】：南山伊妍 【电报】： @yiyan235 【留名】： 饼子 【人照】：10 【颜值】：9 【身材】: 9.9 【过程】：上课课室很干净整洁，进门老师就很热情，身材好，胸大，屁股也很翘，是我喜欢的身材类型。给了上课费用后，冲洗干净，就开始上课，仔细看看老师的胸部 胸型真的很完美 ，接着老师开始了服务 先是亲我的胸，吸着然后用舌头舔奶头真是爽，进入状态后老师又开始亲我的二弟，一吞一吐用舌头在二弟上打转，真是受不住 我着急让老师戴上tt，g老师自己坐了上来，前后上下，我实在顶不住，第一次很快就被老师干了出来，结束一次后和老师聊的很投缘，老师很开朗很会找话题，第二次我来干，老师配合的很到位 时不时嘴里两句骚话叫我老公，摸我的胸用手指慢慢滑我的身体，真的很喜欢这种。结束后身体感觉被掏空 老师和我聊了一会才走，很棒的一次约会。
Showing the 12 most recent of 21 posts we hold for @Szdbbgq. 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 — 501,111 of 1,480,944entries 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 3 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.
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.
@Szdbbgq 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“深圳电报报告” (@Szdbbgq), 1,724 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Szdbbgq.
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.