Telegram RegisterThe public register of Telegram
Telegram profile photo for 深莞不走寻常路(SM双飞野战特殊资源)

Channel

深莞不走寻常路(SM双飞野战特殊资源)

@sztspd

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

7,284subscribers

-361 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
TypeChannel
Username@sztspd
Description上榜联系: @CN3456 私聊不了联系双向机器人: @CN6789BOT 深圳修车资源榜 https://t.me/LM8969 深圳学生会 https://t.me/SZXSH8 一键快速进深圳所有群 https://t.me/addlist/jxLTSzufnjIwNDE1
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/sztspd

Topic

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 3 other registered channels. This entry also sits inside a group of 15 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@sztspd/553 · this entry3 Aug 2026, 04:21 UTC@szddyx/23253 Aug 2026, 04:21 UTC1.00under a minute
@szddyx/23386 Aug 2026, 06:10 UTC@sztspd/575 · this entry6 Aug 2026, 06:11 UTC1.00under a minute
@sztspd/600 · this entry22 Aug 2026, 10:31 UTC@szddyx/235722 Aug 2026, 11:36 UTC1.0065 minutes
@sztspd/656 · this entry18 Oct 2026, 16:04 UTC@szddyx/241418 Oct 2026, 16:05 UTC1.00under a minute
@szddyx/242018 Oct 2026, 16:07 UTC@sztspd/662 · this entry18 Oct 2026, 16:10 UTC1.002 minutes
@nshaoche/28093 Aug 2026, 04:20 UTC@sztspd/553 · this entry3 Aug 2026, 04:21 UTC1.0072 seconds
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@szddyx5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (3–2)
@nshaoche5 (5/5 hand-verifiable sample passed)1.00under a minute@nshaoche (3–2)
@xcrgz5 (5/5 hand-verifiable sample passed)1.0072 seconds@xcrgz (3–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 6 of the 8 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 12 comparable posts for this entry, running 3 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 15 channels, the one whose matching posts we hold earliest is @lhhche. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 15 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

7,2847,8547,5697 August 2026 — 7,645 subscribers8 August 2026 — 7,637 subscribers11 August 2026 — 7,682 subscribers14 August 2026 — 7,714 subscribers17 August 2026 — 7,758 subscribers21 August 2026 — 7,789 subscribers25 August 2026 — 7,854 subscribers27 August 2026 — 7,815 subscribers31 August 2026 — 7,825 subscribers3 September 2026 — 7,790 subscribers9 September 2026 — 7,741 subscribers13 September 2026 — 7,687 subscribers16 September 2026 — 7,782 subscribers2 October 2026 — 7,664 subscribers8 October 2026 — 7,682 subscribers17 October 2026 — 7,617 subscribers19 October 2026 — 7,661 subscribers22 October 2026 — 7,683 subscribers25 October 2026 — 7,694 subscribers28 October 2026 — 7,617 subscribers31 October 2026 — 7,555 subscribers2 November 2026 — 7,490 subscribers5 November 2026 — 7,461 subscribers8 November 2026 — 7,377 subscribers12 November 2026 — 7,284 subscribers7 August 202612 November 2026
25 measurements spanning 96 days, net -361. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 7,199–7,940 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 25
Measured (UTC)SubscribersChange
12 Nov 2026, 01:477,284-93
8 Nov 2026, 08:497,377-84
5 Nov 2026, 10:177,461-29
2 Nov 2026, 18:387,490-65
31 Oct 2026, 01:317,555-62
28 Oct 2026, 10:567,617-77
25 Oct 2026, 11:377,694+11
22 Oct 2026, 21:077,683+22
19 Oct 2026, 18:057,661+44
17 Oct 2026, 02:097,617-65
8 Oct 2026, 18:587,682+18
2 Oct 2026, 05:007,664-118
16 Sept 2026, 15:397,782+95
13 Sept 2026, 02:217,687-54
9 Sept 2026, 01:017,741-49
3 Sept 2026, 16:177,790-35
31 Aug 2026, 04:357,825+10
27 Aug 2026, 23:527,815-39
25 Aug 2026, 00:277,854+65
21 Aug 2026, 03:157,789first reading

Engagement

12 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 37 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.72%
avg views ÷ 7,284 subscribers
Avg views / post
417
4 posts measured
Reaction rate
0.096%
reactions ÷ views · ER floor
Posts in window
4
of 12 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 2 of 4 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 November 2026
Posts held12 (3 August 2026 – 10 November 2026)
Views total1,666
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Nov 2026, 22:41 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

Photos
131
Videos
17
Links
27

Lifetime counters from Telegram’s own channel header, read 13 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.

Video runtime
23s
Average length
12s

Measured directly from 2 videos 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

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2100.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 3 of the 12 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 3 August 2026 to 10 November 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

Telegram’s own ‘edited’ marker: 0 of 4 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

10 Nov 2026, 11:19 UTC127 viewsread 13 November 2026
Photo

🧩榜单番号 0302-1144 南山 月月 抓龙筋 标签(点蓝字查看更多): 👉南山 👉抓龙筋 👉毒龙 👉口爆 👉SM ✅已验证,放心出击 QQ:3666506050 与你:20416691k4cp72 私聊: @linken2012 双向机器人: @linken2012bot 频道: https://t.me/mmjayou 频道: https://t.me/lmzzml777 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联

18 Oct 2026, 16:10 UTC576 views0 reactionsread 13 November 2026
Photo

🧩榜单番号 0830-1153 艺名:#小白兔🐰 消费:399✈️ 499环保口爆 996双飞环保口爆 标签(点蓝字查看更多): 👉宝安 固戍 👉69 👉舌吻 👉巨乳D🐻 👉毒龙🐲 👉口爆环保♻️ 👉双飞 ✅个人私约已验证,放心出击 私聊: @z151120 双向: @Z151120bot 频道: https://t.me/xbt151120 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联

18 Oct 2026, 16:04 UTC497 viewsread 13 November 2026
Photo

🧩榜单番号 0830-1134 宝安柚子皮 消费:398✈️ 498环保,双飞口爆996 标签(点蓝字查看更多): 👉宝安 固戍 👉69 👉舌吻 👉巨乳D🐻 👉毒龙🐲 👉口爆环保♻️ 👉双飞 ✅个人私约已验证,放心出击 私聊: @l251505 双向: @Y02168BOT 频道: https://t.me/lhddyx 更多: 🔥深圳修车资源榜 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联

18 Oct 2026, 09:32 UTC466 views1 reactionsread 13 November 2026
Photo

🧩榜单番号 203-1153 沐沐抓龙筋 标签(点蓝字查看更多): 👉南山 👉抓龙筋 👉毒龙 👉口爆 👉SM 微信: ZLJ6699ss QQ:2282146374 私聊: @xjz58 双向机器人: @xjz68bot 频道: https://t.me/ZLJ6688ss ✅已验证,放心出击 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联

❤1

22 Aug 2026, 10:31 UTC166 viewsread 28 August 2026
Photo

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

18 Aug 2026, 12:40 UTC250 viewsread 28 August 2026
Photo

🧩榜单番号 203-1153 沐沐抓龙筋 微信: ZLJ6699ss QQ:2282146374 私聊: @xjz58 双向机器人: @xjz68bot 频道: https://t.me/ZLJ6688ss 标签(点蓝字查看更多): 👉南山 👉抓龙筋 👉毒龙 👉口爆 👉SM ✅已验证,放心出击 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联

14 Aug 2026, 05:58 UTC307 views1 reactionsread 28 August 2026
Photo

🧩榜单番号 0814-56884 #深圳抓龙经 #深圳前列腺高潮 #深圳丝足 #女王调教 #深圳上门按摩 #深圳丝足 #寸止 #女王#龟责 🐲地址:深圳市福田区八卦一路园岭地铁站出口附近 莉莉预约电话:—13613083896 QQ: 421752016 QQ:469744260 莉莉老师频道: @hu124567 备用视频频道: @hu990108 TG: @chen990108 双向机器人: @@chen990108bot 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联

❤1

8 Aug 2026, 06:16 UTC379 viewsread 28 August 2026
Photo

🧩榜单番号 0302-1144 南山 月月 抓龙筋 标签(点蓝字查看更多): 👉南山 👉抓龙筋 👉毒龙 👉口爆 👉SM ✅已验证,放心出击 QQ:3666506050 与你:20416691k4cp72 私聊: @linken2012 双向机器人: @linken2012bot 频道: https://t.me/mmjayou 频道: https://t.me/lmzzml777 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联

6 Aug 2026, 06:11 UTC270 viewsread 20 August 2026
Photo

🧩榜单番号 0806-4453 宝安 晓晓 标签(点蓝字查看更多): 👉宝安 👉69 👉毒龙 👉舌吻🐍 👉巨乳D🐻 👉口爆 👉双飞 ✅个人私约已验证,放心出击 92/400 95/500 95双飞/888 私聊: @xiao168999 频道: https://t.me/xiao93888 机器人: @xiaoxiaolove1314_bot 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联

4 Aug 2026, 06:47 UTC247 viewsread 18 August 2026
Photo

🧩榜单番号 0804-1144 晨晨 宝安 92课费 399元 95课费499元 95双飞998元 标签(点蓝字查看更多): 👉宝安 👉69 👉巨乳D🐻 👉毒龙 👉舌吻🐍 👉双飞 私聊: @hcy2020 双向机器人: @hcy2020bot 频道: https://t.me/hcy20201 ✅个人私约已验证,放心出击 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联

4 Aug 2026, 05:46 UTC165 viewsread 12 August 2026
Photo

🧩榜单番号 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 更多: 🌎深圳修车资源导航 资源群:🍀深圳学生会 一键快速进深圳所有群 🔍更多资源福利 👉点我永不失联

3 Aug 2026, 04:21 UTC125 viewsread 8 August 2026
Photo

🧩榜单番号 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 12 most recent of 12 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.

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.

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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“深莞不走寻常路(SM双飞野战特殊资源)” (@sztspd), 7,284 subscribers as measured 12 November 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.