🧩榜单番号 0822-1141 菲菲三通 ( 🉑无套) 课费 500p 800pp 标签(点蓝字查看更多): 👉罗湖 👉舌吻🐍 👉毒龙 👉69 👉后花园 ✅已验证,放心出击 私聊 @feifeier68666 频道 https://t.me/feifei5551 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联

Channel
深莞不走寻常路(SM双飞野战特殊资源)
@sztspd
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
7,790subscribers
+145 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001959753451 |
|---|---|
| Type | Channel |
| Username | @sztspd |
| 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 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 3 September 2026 |
| On Telegram | t.me/sztspd |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Sept 2026, 16:17 | 7,790 | -35 |
| 31 Aug 2026, 04:35 | 7,825 | +10 |
| 27 Aug 2026, 23:52 | 7,815 | -39 |
| 25 Aug 2026, 00:27 | 7,854 | +65 |
| 21 Aug 2026, 03:15 | 7,789 | +31 |
| 17 Aug 2026, 19:57 | 7,758 | +44 |
| 14 Aug 2026, 18:23 | 7,714 | +32 |
| 11 Aug 2026, 18:13 | 7,682 | +45 |
| 8 Aug 2026, 10:21 | 7,637 | -8 |
| 7 Aug 2026, 16:31 | 7,645 | first reading |
Engagement
8 posts held, back to 3 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 17 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 3.54%
- avg views ÷ 7,790 subscribers
- Avg views / post
- 276
- 4 posts measured
- Reaction rate
- 0.326%
- reactions ÷ views · ER floor
- Posts in window
- 4
- of 8 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 1 of 4 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 22 August 2026 |
|---|---|
| Posts held | 8 (3 August 2026 – 22 August 2026) |
| Views total | 1,102 |
| Reactions total | 1 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 20:26 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
- Video runtime
- 16s
- Average length
- 16s
Measured directly from 1 video 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
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 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 1 of the 8 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 3 August 2026 to 22 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.
Recent posts
🧩榜单番号 203-1153 沐沐抓龙筋 微信: ZLJ6699ss QQ:2282146374 私聊: @xjz58 双向机器人: @xjz68bot 频道: https://t.me/ZLJ6688ss 标签(点蓝字查看更多): 👉南山 👉抓龙筋 👉毒龙 👉口爆 👉SM ✅已验证,放心出击 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联
🧩榜单番号 0814-56884 #深圳抓龙经 #深圳前列腺高潮 #深圳丝足 #女王调教 #深圳上门按摩 #深圳丝足 #寸止 #女王#龟责 🐲地址:深圳市福田区八卦一路园岭地铁站出口附近 莉莉预约电话:—13613083896 QQ: 421752016 QQ:469744260 莉莉老师频道: @hu124567 备用视频频道: @hu990108 TG: @chen990108 双向机器人: @@chen990108bot 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联
❤1
🧩榜单番号 0302-1144 南山 月月 抓龙筋 标签(点蓝字查看更多): 👉南山 👉抓龙筋 👉毒龙 👉口爆 👉SM ✅已验证,放心出击 QQ:3666506050 与你:20416691k4cp72 私聊: @linken2012 双向机器人: @linken2012bot 频道: https://t.me/mmjayou 频道: https://t.me/lmzzml777 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联
🧩榜单番号 0806-4453 宝安 晓晓 标签(点蓝字查看更多): 👉宝安 👉69 👉毒龙 👉舌吻🐍 👉巨乳D🐻 👉口爆 👉双飞 ✅个人私约已验证,放心出击 92/400 95/500 95双飞/888 私聊: @xiao168999 频道: https://t.me/xiao93888 机器人: @xiaoxiaolove1314_bot 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联
🧩榜单番号 0804-1144 晨晨 宝安 92课费 399元 95课费499元 95双飞998元 标签(点蓝字查看更多): 👉宝安 👉69 👉巨乳D🐻 👉毒龙 👉舌吻🐍 👉双飞 私聊: @hcy2020 双向机器人: @hcy2020bot 频道: https://t.me/hcy20201 ✅个人私约已验证,放心出击 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联
🧩榜单番号 0302-1153 南山林林抓龙筋(大冲新城花园) A套餐 60分钟/468 B套餐 90分钟/698 C套餐 120分钟/888 D套餐 90分钟/999 E套餐 120分钟/1299 SM女王调教 90分钟/899 标签(点蓝字查看更多): 👉南山 👉抓龙筋 👉口爆 👉SM ✅已验证,放心出击 qq: 3505331286 私信 @linzi062004 双向机器人 @linzi062004bot 安卓频道 https://t.me/linzi0620004 苹果频道 https://t.me/dfgas4 点击下面链接查看手法视频(永不失联) https://t.me/gohome?start=L-Cjfo1q 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联
🧩榜单番号 0310-1144 深圳南山抓龙筋依依 标签(点蓝字查看更多): 👉南山 👉抓龙筋 👉口爆 👉SM ✅已验证,放心出击 QQ:3753721520 微信:ABC611475 私聊: @FF3689 双向机器人: @FF368BOT 安卓频道: https://t.me/WYH8901 苹果频道: https://t.me/WYH368999 SM手法视频频道: https://t.me/WYH36899 请大家点下下面的链接,更方便,永不失联 https://t.me/gohome?start=L-m05BYT 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联
Showing the 8 most recent of 8 posts we hold for @sztspd. 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.
Mentions
Named by 11 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.
@lsjddwo · 14,8869 posts南山❤️修车资源
@nshaoche · 10,7949 posts深莞资源总榜
@szddyx · 29,3139 posts深莞可舌吻🐍老师收录
@shwwen666 · 7,7228 posts深圳优选
@DiDiuwoo · 11,8855 posts深圳抓龙筋/会所推荐榜
@xcrgz · 8,6125 posts深莞鲍鱼粉嫩老师收录
@myao170 · 6,9344 posts你就说大不大吧
@njiusdbd · 7,9814 posts深莞可口爆资源
@szgkbang · 7,9354 posts宝安&长安&光明❤️修车资源
@banhche · 10,0271 post罗湖&香港❤️修车资源
@lhhaoche · 8,1091 post
Names
Channels on the register whose handles appear in this channel's posts.
@LM8969 · 17,0718 posts深圳学生会
@SZXSH8 · 16,0398 posts深莞私约资源榜
@lsjddwo · 14,8867 posts深莞可口爆资源
@szgkbang · 7,9355 posts深莞可毒龙&莞式服务老师收录
@xyu5568 · 7,0425 posts南山❤️修车资源
@nshaoche · 10,7944 posts深圳抓龙筋/会所推荐榜
@xcrgz · 8,6124 posts深莞鲍鱼粉嫩老师收录
@myao170 · 6,9343 posts深莞可舌吻🐍老师收录
@shwwen666 · 7,7223 posts宝安&长安&光明❤️修车资源
@banhche · 10,0272 posts你就说大不大吧
@njiusdbd · 7,9812 posts林林抓龙筋备用频道
@dfgas4 · 751 post罗湖三通菲菲
@feifei5551 · 8,4091 post深圳(莉莉)抓龙经前高潮.抚触疗愈.脱敏.龟责,女王调教
@hu124567 · 5,1481 post深圳专业抓龙筋,前高 丝足 龟责 女王(福田莉莉)
@hu990108 · 3421 post罗湖&香港❤️修车资源
@lhhaoche · 8,1091 post深圳南山抓龙筋林林
@linzi0620004 · 5941 post深莞资源总榜
@szddyx · 29,3131 post深圳南山依依2
@WYH368999 · 301 post晓晓个人频道
@xiao93888 · 3,6211 post
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@sztspd 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.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 12 posts, 8 August 2026 – 20 August 2026 · confirmed gone 9 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 3 September 2026 — this entry's latest reading, not the date you are reading this.
“深莞不走寻常路(SM双飞野战特殊资源)” (@sztspd), 7,790 subscribers as measured 3 September 2026. Telegram Register, tgregister.com/channel/sztspd.
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.