Telegram RegisterThe public register of Telegram
Telegram profile photo for 深圳三和修车大队【宝安区】

Channel

深圳三和修车大队【宝安区】

@Sz3hdsban

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

8,866subscribers

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

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002601445951
TypeChannel
Username@Sz3hdsban
Description上榜推广联系 @SZ88330 报告投稿联系 @SZ_s_h_d_s 选妃榜单 https://t.me/+p350NMfDt-oyYTFl 选妃轮播 https://t.me/+5wLTl8pr7k03MzJl 出击报告 https://t.me/+5Qg0De6sn85iNTU1 老师黑榜 https://t.me/+O-PRLOdYIaY5ZGM9
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 November 2026
Measurements held28
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/Sz3hdsban

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 70% 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 2 other registered channels. This entry also sits inside a group of 44 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
@SZ_3hdsbd/2025214 Aug 2026, 09:24 UTC@Sz3hdsban/3791 · this entry14 Aug 2026, 09:31 UTC1.006 minutes
@SZ_3hdsbd/2027315 Aug 2026, 06:13 UTC@Sz3hdsban/3797 · this entry15 Aug 2026, 06:13 UTC1.00under a minute
@SZ_3hdsbd/2037117 Aug 2026, 09:37 UTC@Sz3hdsban/3808 · this entry17 Aug 2026, 09:37 UTC1.00under a minute
@SZ_3hdsbd/2051721 Aug 2026, 10:30 UTC@Sz3hdsban/3834 · this entry21 Aug 2026, 10:31 UTC1.00under a minute
@SZ_3hdsbd/2056522 Aug 2026, 07:50 UTC@Sz3hdsban/3852 · this entry22 Aug 2026, 07:58 UTC1.008 minutes
@SZ_3hdsbd/2285927 Oct 2026, 06:02 UTC@Sz3hdsban/4344 · this entry27 Oct 2026, 06:03 UTC1.00under a minute
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
@SZ_3hdsbd22 (8/8 hand-verifiable sample passed)1.00under a minute@SZ_3hdsbd (22–0)
@SZ_shcjzl21 (8/8 hand-verifiable sample passed)1.00under a minute@SZ_shcjzl (20–1)

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. 42 of the 42 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 32 comparable posts for this entry, running 6 August 2026 to 11 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 44 channels, the one whose matching posts we hold earliest is @sycjdsjb. 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_copy, last confirmed 17 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 44 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.

LotteryBest抽奖导航
@lotterynav · Channel
199,561 subscribers
LotteryBest精选推荐
@lotterybestnav · Channel
173,698 subscribers
༺ཌༀ成都修车俱乐部•车库ༀད༻
@CD_julebu1 · Channel
74,805 subscribers
深圳三和修车大队-【嫩妹御姐资源】
@SZ_3hdsbd · Channel
64,217 subscribers
深圳修车军团【验证榜单】
@shenzhen_xcjt · Channel
61,095 subscribers
长春烟雨楼修车认证榜
@changchuncj8 · Channel
60,726 subscribers
沈阳修车出击队《出击榜》
@sycjdrzbby1 · Channel
59,804 subscribers
杭师大公开榜
@ffffghjjjjhg · Channel
54,116 subscribers
深圳嫩妹修车团【榜单】
@sz_papapa777 · Channel
49,888 subscribers
深圳三和修车大队-【选妃榜单】
@SZ_shcjzl · Channel
37,534 subscribers
深圳嫩妹茶探府【修车榜单】
@SZ_nmctf9 · Channel
29,263 subscribers
北京【海奥华】反馈频道
@hahbeijing5 · Channel
28,941 subscribers
沈阳出击队spa洗浴抓龙筋
@sycjdsjb · Channel
26,999 subscribers
嫩妹社资源总榜
@shdjuygbb · Channel
26,722 subscribers
大连修车风月楼《认证榜》
@qgdl1 · Channel
24,403 subscribers
深圳修车出击大队【榜单】
@SZxiuchechuji_zy · Channel
22,720 subscribers
嫩妹社报告榜
@hzjzddbgb · Channel
21,020 subscribers
深圳修车社区资源榜
@guangdong95277 · Channel
20,053 subscribers
深圳三和修车大队-【优惠券频道】
@SZ3hdsyhj · Channel
16,752 subscribers
野寻 · 深圳活动公告
@chasesz_hdgg · Channel
15,464 subscribers
辽宁沈阳周边吃瓜资源
@syxwgbcg · Channel
15,242 subscribers
野寻·上海修车档案
@chasesh_lsda · Channel
12,952 subscribers
野寻·北京精选榜单
@chasebj_jxbd · Channel
12,343 subscribers
成都七仙女· 防掉队
@sichuanchengdu398 · Channel
11,972 subscribers
深圳修车出击大队【报告】
@SZxiuchechuji_bg · Channel
11,945 subscribers
野寻·北京作业评价
@chasebj_zypj · Channel
11,395 subscribers
深圳野狼修车公开榜
@SZLXF · Channel
11,080 subscribers
深圳嫩妹茶探府【出击报告】
@SZ_nmctf7 · Channel
11,067 subscribers
野寻·北京活动公告
@chasebj_hdgg · Channel
10,600 subscribers
广州佛山《红袖招》公开榜
@FsxcXh0 · Channel
9,890 subscribers
野寻·上海活动公告
@chasesh_hdgg · Channel
8,650 subscribers
✨小天涯·日记✨
@xtyrj · Channel
7,788 subscribers
深圳三和修车大队【福田区】
@Sz3hdsft · Channel
6,952 subscribers
深圳三和修车大队【龙华区】
@Sz3hdslh · Channel
6,592 subscribers
深圳嫩妹修车团【报告】
@sz_papapa666 · Channel
6,433 subscribers
深圳修车军团【修车报告】
@shenzhen_xcbg · Channel
6,429 subscribers
深圳三和修车大队【龙岗区】
@Sz3hdslg · Channel
6,154 subscribers
深圳三和修车大队【南山区】
@Sz3hdsnsq · Channel
6,071 subscribers
野狼抽奖活动
@cjyhhd · Channel
3,057 subscribers
广州佛山《红袖招》报告榜
@fsxcbg0 · Channel
2,940 subscribers
广州佛山《红袖招》抽奖
@Fsxc6 · Channel
2,101 subscribers
深圳修车出击大队【备用榜】
@szxiuchechuji_bd · Channel
1,528 subscribers
深圳嫩妹修车团【嫩妹榜单】
@shenzehn818 · Channel
360 subscribers

Growth

7,4428,8668,1546 August 2026 — 7,442 subscribers6 August 2026 — 7,442 subscribers7 August 2026 — 7,451 subscribers10 August 2026 — 7,543 subscribers13 August 2026 — 7,639 subscribers16 August 2026 — 7,739 subscribers19 August 2026 — 7,815 subscribers24 August 2026 — 7,885 subscribers26 August 2026 — 7,946 subscribers30 August 2026 — 8,014 subscribers1 September 2026 — 8,060 subscribers5 September 2026 — 8,146 subscribers10 September 2026 — 8,272 subscribers14 September 2026 — 8,319 subscribers18 September 2026 — 8,446 subscribers28 September 2026 — 8,503 subscribers5 October 2026 — 8,513 subscribers12 October 2026 — 8,569 subscribers15 October 2026 — 8,624 subscribers18 October 2026 — 8,649 subscribers21 October 2026 — 8,674 subscribers25 October 2026 — 8,711 subscribers28 October 2026 — 8,725 subscribers31 October 2026 — 8,748 subscribers3 November 2026 — 8,778 subscribers6 November 2026 — 8,800 subscribers9 November 2026 — 8,810 subscribers14 November 2026 — 8,866 subscribers6 August 202614 November 2026
28 measurements spanning 100 days, net +1,424. 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,228–9,080 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 28
Measured (UTC)SubscribersChange
14 Nov 2026, 21:478,866+56
9 Nov 2026, 14:058,810+10
6 Nov 2026, 10:368,800+22
3 Nov 2026, 16:358,778+30
31 Oct 2026, 17:488,748+23
28 Oct 2026, 15:368,725+14
25 Oct 2026, 07:518,711+37
21 Oct 2026, 23:288,674+25
18 Oct 2026, 16:198,649+25
15 Oct 2026, 22:288,624+55
12 Oct 2026, 12:568,569+56
5 Oct 2026, 23:178,513+10
28 Sept 2026, 12:208,503+57
18 Sept 2026, 23:408,446+127
14 Sept 2026, 08:588,319+47
10 Sept 2026, 17:388,272+126
5 Sept 2026, 23:598,146+86
1 Sept 2026, 23:288,060+46
30 Aug 2026, 00:158,014+68
26 Aug 2026, 17:177,946first reading

Engagement

36 posts held, back to 6 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 47 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
10.4%
avg views ÷ 8,866 subscribers
Avg views / post
926
11 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
11
of 36 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 11 November 2026
Posts held36 (6 August 2026 – 11 November 2026)
Views total10,182
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 13: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.

What this channel posts

Photos
≈3,010
Videos
≈430
Links
≈423

Lifetime counters from Telegram’s own channel header, read 17 November 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
1m 56s
Average length
12s

Measured directly from 10 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

Telegram’s own ‘edited’ marker: 0 of 11 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).

11 Nov 2026, 07:54 UTC876 viewsread 17 November 2026
Photo

艺名:#乐儿 深圳:#宝安 私聊:@yzmleier 双向:@lhexgsBOtbot 频道:https://t.me/m8214 消费:600p 1100pp 1388两小时 验证:#视频已验证 标签:#六九 #舌吻 #刮痧 #毒龙 #口爆 #深喉 #御姐 #莞式

10 Nov 2026, 08:48 UTC≈1,000 viewsread 17 November 2026
Photo

艺名:#婷婷 深圳:#宝安 #固戍 私聊:@tingting8896 双向:@tingting8896bot 频道:https://t.me/tingting8898 消费:92/400 花式手推 95/500深喉口爆 验证:#视频已验证 标签:#按摩 #胸推全身 #陪浴 #舌漫游 #毒龙 #口爆 #深喉

10 Nov 2026, 06:02 UTC945 viewsread 17 November 2026
Photo

艺名:#璐璐 深圳:#宝安 私聊:@fjw13688 双向:@lulujw_bot 频道:https://t.me/+Oga-H2jfXQdjNTE9 消费:599(60分钟) 799 (60分钟) 验证:#视频已验证 标签:#抓龙筋 #环保 #龟责 #丝足 #臀部spa #环游 #指滑

10 Nov 2026, 04:47 UTC890 viewsread 17 November 2026
Photo

艺名:#瑶瑶 深圳:#宝安 #西乡 私聊:@yao7200 双向:@yao72006bot 频道:https://t.me/yaoyao4699 消费:1000p 1600pp 验证:#视频已验证 标签:#舌吻 #六九 #陪浴 #胸推 #角色扮演 #丝袜制服 #嫩妹

6 Nov 2026, 14:56 UTC747 viewsread 11 November 2026
Photo

艺名:#安诺 深圳:#宝安 #西乡 私聊:@Ciiu8 双向:@Courri8_bot 频道:https://t.me/Ceeuo2 消费:600p 1200pp 验证:#视频已验证 标签:#Kiss #六九 #胸推 #鸳鸯浴 #漫游 #指滑 #毒龙 #臀推

6 Nov 2026, 04:22 UTC615 viewsread 9 November 2026
Photo

艺名:#雯雯 深圳:#宝安 私聊:@wenwen6696 双向:@wrnwen6698bot 频道:https://t.me/wenwen6669 消费:400(手推50分钟) 500(口爆60分钟) 验证:#视频已验证 标签:#舌吻 #六九 #鸳鸯浴 #丝袜制服 #按摩 #胸推 #臀腿 #长腿 #三点粉

5 Nov 2026, 06:16 UTC688 viewsread 9 November 2026
Photo

艺名:#深圳沙井泰式抓龙筋 深圳:#宝安 #沙井 私聊:@qe698698 双向:@qe698698bot 频道:https://t.me/wer555888 消费:课一:300 课二:400 课三:500 验证:#视频已验证 标签:#全身按摩 #精油开背 #臀部理疗 #海底捞月 #丝足 #前列腺按摩 #抓龙筋

3 Nov 2026, 07:04 UTC893 viewsread 9 November 2026
Photo

#宝安 丽娜个人工作室 #抓龙筋 #全身精油spa #泰式专业抓龙筋,情趣丝足,龟责潮喷,前列腺保养,前列腺高潮,三起三落,丝足诱惑,半裸,胸推,足交,互动挑逗,时间内可多次释放,让您乐在其中,享之不尽,回味无穷哦 全深圳可上门,不偷钟,无套路 课费: 468~899 微信: 14776182731 QQ :1084952348 私聊:@Lzz2225 频道:https://t.me/linazhualongjin8 双向机器人 @Lzz2225_bot

1 Nov 2026, 04:03 UTC878 viewsread 6 November 2026
Photo

艺名:#小梦 深圳:#宝安 #宝体 私聊:@montoya259 频道:https://t.me/xm999xm889 消费:400p 800pp 验证:#视频已验证 标签:#舌吻 #六九 #口爆 #深喉 #波推 #丝袜制服 #高跟鞋

27 Oct 2026, 06:03 UTC≈1,410 viewsread 5 November 2026
Photo

艺名:#希希 深圳:#宝安 私聊:@xiaoxixi118 双向:@xiaoxixiybot 频道:https://t.me/xixidjia 消费:700p 1300pp 验证:#视频已验证 标签:#舌吻 #六九 #鸳鸯浴 #丝袜制服 #高跟 #毒龙 #按摩 #指滑 #长腿

26 Oct 2026, 06:41 UTC≈1,240 viewsread 4 November 2026
Photo

艺名:#悠悠 深圳:#宝安 私聊:@you334425 双向:@youeng_3234bot 频道:https://t.me/you220045 消费:700p 1300pp 验证:视频已验证 服务:#亲嘴 #制服 #道具 #六九 #调情 #丝袜 #E罩杯 #大长腿

27 Aug 2026, 07:44 UTC359 viewsread 28 August 2026
Photo

艺名:#玖柒 深圳:#宝安 #西乡 私聊:@mmpa97 频道:https://t.me/mmpa97mm 消费:550环保 800p 1200环保+啪啪 验证:#视频已验证 标签:#kiss #艳舞 #毒龙 #深喉 #制服 #冰火 #环保 #ABC面

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

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

“深圳三和修车大队【宝安区】” (@Sz3hdsban), 8,866 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/Sz3hdsban.

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.