Telegram RegisterThe public register of Telegram

Channel

深圳三和修车大队-【嫩妹御姐资源】

@SZ_3hdsbd

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Cite this entry

43,803subscribers

+1,906 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1002528673596
TypeChannel
Username@SZ_3hdsbd
Description✅上榜员 @SZ88330 ✅中转站 @Sz3hZzz ✅交流群 @sz3hds ✅选妃群 @SZ_shcjzl1
CreatedBetween 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live14 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/SZ_3hdsbd

Topic

Adult — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 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 why it has no browse page of its own yet.

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 word for word on 1 other registered channel. 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
@SZ_3hdsbd/19939 · this entry6 Aug 2026, 11:51 UTC@SZ_shcjzl/188876 Aug 2026, 11:51 UTC1.00under a minute
@SZ_3hdsbd/19946 · this entry6 Aug 2026, 13:20 UTC@SZ_shcjzl/188946 Aug 2026, 13:20 UTC1.00under a minute
@SZ_3hdsbd/19951 · this entry6 Aug 2026, 15:27 UTC@SZ_shcjzl/188996 Aug 2026, 15:27 UTC1.00under a minute
@SZ_3hdsbd/19972 · this entry7 Aug 2026, 06:01 UTC@SZ_shcjzl/189227 Aug 2026, 06:01 UTC1.00under a minute
@SZ_3hdsbd/19980 · this entry7 Aug 2026, 06:52 UTC@SZ_shcjzl/189307 Aug 2026, 06:52 UTC1.00under a minute
@SZ_3hdsbd/19986 · this entry7 Aug 2026, 09:59 UTC@SZ_shcjzl/189367 Aug 2026, 09:59 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@SZ_shcjzl7 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (70)

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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 9 comparable posts for this entry, running 6 August 2026 to 7 August 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).

Across the whole group of 2, the earliest publisher we hold is @SZ_3hdsbd — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

41,89743,80342,8506 August 2026 — 41,897 subscribers6 August 2026 — 41,897 subscribers7 August 2026 — 42,048 subscribers8 August 2026 — 42,320 subscribers9 August 2026 — 42,529 subscribers10 August 2026 — 42,581 subscribers11 August 2026 — 42,901 subscribers12 August 2026 — 43,104 subscribers13 August 2026 — 43,380 subscribers14 August 2026 — 43,803 subscribers6 August 202614 August 2026
10 measurements spanning 8 days, net +1,906. 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 41,611–44,089 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 18:2743,803+423
13 Aug 2026, 09:4843,380+276
12 Aug 2026, 10:1643,104+203
11 Aug 2026, 10:1942,901+320
10 Aug 2026, 07:0342,581+52
9 Aug 2026, 10:0142,529+209
8 Aug 2026, 11:5642,320+272
7 Aug 2026, 11:5042,048+151
6 Aug 2026, 22:4541,897no change
6 Aug 2026, 22:3841,897first reading

Engagement

47 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 21 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.826%
avg views ÷ 43,803 subscribers
Avg views / post
362
47 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
47
of 47 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 August 2026
Posts held47 (6 August 202614 August 2026)
Views total17,014
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 00:37 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
1,240
Videos
184
Links
250

Lifetime counters from Telegram’s own channel header, read 15 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
3m 29s
Average length
11s

Measured directly from 19 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.

Recent posts

14 Aug 2026, 10:02 UTC537 viewsread 15 August 2026
Photo

💖龙华/福田/宝安/南山库洛米嫩妹丝足SM抓龙筋 #龙华 #福田 #宝安 #南山 #丝足 #Sm #抓龙筋 深圳独家05后高颜值嫩妹抓龙筋 适合足控 颜值控 SM控 兼顾颜值和手法足艺 本人照片 假一赔十 手法专业 1.全身推油 2.三角区专业抓龙筋 3.丝足足交调情 4.丝足/双手高潮释放 ✅A套餐 598 70分钟 ✅B套餐 698 90分钟 ✅C套餐 998 120分钟 🔥火热聊天抽奖福利群 @szklmgp 南山预约 @szmtxnspm 南山频道 @szmtxpd 龙华预约 @szklmpm 龙华频道 @szkuluomipd 福田预约 @szmldpm 福田频道 @szmldpd 宝安预约 @szjybapm 宝安频道 @szbajypd 半裸店预约 @szyggblpm 频道 @szyggpd qq:1591914964

14 Aug 2026, 09:24 UTC462 viewsread 15 August 2026
Photo

艺名:#麦麦子 深圳:#宝安 #西乡 私聊:@maimaizibe 双向:@maimaizibe8bot 频道:https://t.me/mai0601 消费:1000p 1600pp 验证:#视频已验证 标签:#舌吻 #六九 #陪浴 #冰火 #胸推 #丝袜 #嫩妹

14 Aug 2026, 09:12 UTC430 viewsread 15 August 2026
Photo

艺名:#小米(抓龙筋) 深圳:#南山 私聊:@ASDP001 双向:@Tbythhdbot 频道:https://t.me/QQQAAC111 消费:498 A套餐 798 B套餐 998C套餐 验证:#视频已验证 标签:#抓龙筋 #精油SPA #胸推 #半裸 #前列腺按摩 #丝足 #制服

13 Aug 2026, 16:12 UTC238 viewsread 14 August 2026
Photo

艺名:#许轻轻 深圳:#宝安 私聊:@xuqingqin99 频道:https://t.me/xuqingqin9999 消费:800p 1500pp 验证:#视频已验证 标签:#kiss #鸳鸯浴 #丝袜制服 #嫩妹 #高跟 #舔蛋蛋

13 Aug 2026, 15:40 UTC258 viewsread 14 August 2026
Photo

艺名:#佳佳 深圳:#福田 私聊:@jiajia52000 双向:@jiajia5200011bot 频道:https://t.me/lanlan520000 消费:1500p 3000pp 验证:#视频已验证 标签:#舌吻 #胸推 #鸳鸯浴 #调情 #丝袜制服 #嫩妹 #啪啪

13 Aug 2026, 15:40 UTC266 viewsread 14 August 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_1960006299

13 Aug 2026, 12:38 UTC424 viewsread 14 August 2026
Photo

艺名:#龙儿 深圳:#宝安 #沙井 私聊:@wqq168168 频道:https://t.me/wwyy58858 消费:400-500-650-800 验证:#视频已验证 标签:#按摩 #莞式 #指滑 #过水 #毒龙 #漫游 #口爆

13 Aug 2026, 10:31 UTC491 viewsread 14 August 2026
Photo

艺名:#柔柔 深圳:#福田 私聊:@pyh10 双向:@rourouer2_bot 频道:https://t.me/+lLzzmZw9FgAzNzI1 消费:1300p 2500pp 验证:#视频已验证 标签:#鸳鸯浴 #丝袜制服 #按摩 #指滑 #深喉 #胸推 #啪啪

13 Aug 2026, 08:03 UTC75 viewsread 13 August 2026
Photo

艺名:#樱桃 深圳:#龙华 私聊:@yingtao342 双向:@yingtao342bot 频道:https://t.me/+UsyctQZ4y3NmNDNl 消费:1300p 2200pp 验证:#视频已验证 标签:#舌吻 #六九 #鸳鸯浴 #丝袜制服 #胸推 #嫩妹

13 Aug 2026, 07:51 UTC77 viewsread 13 August 2026
Photo

艺名:#奶糖 深圳:#光明 私聊:@naitangkk 双向:@aijs22_bot 频道:https://t.me/aijs22 消费:800p 1500pp 验证:#视频已验证 标签:#舌吻 #六九 #舔蛋蛋 #丝袜制服 #调情 #御姐

13 Aug 2026, 05:47 UTC174 viewsread 13 August 2026
Photo

艺名:#木子 深圳:#龙华 私聊:@wwlilili888 双向:@muzijqr_bot 频道:@wwwmmm1919 消费:700p 1300pp 验证:#视频已验证 标签:#鸳鸯浴 #丝袜制服 #胸推 #臀推 #大胸 #嫩妹

12 Aug 2026, 14:04 UTC615 viewsread 13 August 2026
Photo

艺名:#童童 深圳:#福田 私聊:@fttong 双向:@fttongtong123bot 频道:https://t.me/ttzaifutian1 消费:1200p 2000pp 验证:#视频已验证 标签:#舌吻 #六九 #鸳鸯浴 #丝袜制服 #嫩妹 #长腿 #三点粉

Showing the 12 most recent of 47 posts we hold for @SZ_3hdsbd. 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.

Posts edited after publishing

@SZ_3hdsbd 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.

First edit seen
8 August 2026
Most recent edit
8 August 2026

Citation-graph rank

Citation-graph rank — 350,155 of 1,478,351entries 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.

Forward network

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.

Mentions

Named by 2 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“深圳三和修车大队-【嫩妹御姐资源】” (@SZ_3hdsbd), 43,803 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/SZ_3hdsbd.

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.