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

Channel

深圳三和修车大队【龙岗区】

@Sz3hdslg

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

6,154subscribers

+1,199 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-1002531670559
TypeChannel
Username@Sz3hdslg
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 live16 November 2026
Measurements held29
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/Sz3hdslg

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 84% 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/199807 Aug 2026, 06:52 UTC@Sz3hdslg/2027 · this entry7 Aug 2026, 06:53 UTC1.0072 seconds
@SZ_3hdsbd/200038 Aug 2026, 06:45 UTC@Sz3hdslg/2033 · this entry8 Aug 2026, 06:45 UTC1.00under a minute
@SZ_3hdsbd/200468 Aug 2026, 15:33 UTC@Sz3hdslg/2047 · this entry8 Aug 2026, 15:33 UTC1.00under a minute
@SZ_3hdsbd/2294731 Oct 2026, 07:54 UTC@Sz3hdslg/2355 · this entry31 Oct 2026, 07:55 UTC1.0072 seconds
@SZ_3hdsbd/2296031 Oct 2026, 15:20 UTC@Sz3hdslg/2361 · this entry31 Oct 2026, 15:31 UTC1.0011 minutes
@SZ_3hdsbd/229862 Nov 2026, 06:26 UTC@Sz3hdslg/2367 · this entry2 Nov 2026, 06:27 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_3hdsbd12 (8/8 hand-verifiable sample passed)1.00under a minute@SZ_3hdsbd (12–0)
@SZ_shcjzl10 (8/8 hand-verifiable sample passed)1.00under a minute@SZ_shcjzl (9–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. 21 of the 21 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 16 comparable posts for this entry, running 6 August 2026 to 5 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
深圳三和修车大队【宝安区】
@Sz3hdsban · Channel
8,866 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
深圳三和修车大队【南山区】
@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

4,9556,1545,554.56 August 2026 — 4,955 subscribers6 August 2026 — 4,955 subscribers7 August 2026 — 4,961 subscribers9 August 2026 — 5,049 subscribers12 August 2026 — 5,123 subscribers16 August 2026 — 5,232 subscribers20 August 2026 — 5,290 subscribers23 August 2026 — 5,352 subscribers26 August 2026 — 5,393 subscribers29 August 2026 — 5,458 subscribers1 September 2026 — 5,505 subscribers4 September 2026 — 5,557 subscribers9 September 2026 — 5,668 subscribers13 September 2026 — 5,699 subscribers17 September 2026 — 5,798 subscribers26 September 2026 — 5,855 subscribers5 October 2026 — 5,892 subscribers12 October 2026 — 5,916 subscribers15 October 2026 — 5,957 subscribers18 October 2026 — 5,994 subscribers21 October 2026 — 6,021 subscribers24 October 2026 — 6,055 subscribers27 October 2026 — 6,048 subscribers30 October 2026 — 6,050 subscribers1 November 2026 — 6,082 subscribers4 November 2026 — 6,092 subscribers7 November 2026 — 6,113 subscribers10 November 2026 — 6,132 subscribers16 November 2026 — 6,154 subscribers6 August 202616 November 2026
29 measurements spanning 101 days, net +1,199. 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 4,775–6,334 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
16 Nov 2026, 06:386,154+22
10 Nov 2026, 12:596,132+19
7 Nov 2026, 05:576,113+21
4 Nov 2026, 13:486,092+10
1 Nov 2026, 23:066,082+32
30 Oct 2026, 09:286,050+2
27 Oct 2026, 08:396,048-7
24 Oct 2026, 12:566,055+34
21 Oct 2026, 14:486,021+27
18 Oct 2026, 06:015,994+37
15 Oct 2026, 09:175,957+41
12 Oct 2026, 02:585,916+24
5 Oct 2026, 08:215,892+37
26 Sept 2026, 15:415,855+57
17 Sept 2026, 23:555,798+99
13 Sept 2026, 18:215,699+31
9 Sept 2026, 18:155,668+111
4 Sept 2026, 19:185,557+52
1 Sept 2026, 12:475,505+47
29 Aug 2026, 13:095,458first reading

Engagement

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

ERR · 30 days
4.38%
avg views ÷ 6,154 subscribers
Avg views / post
270
6 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
6
of 17 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 5 November 2026
Posts held17 (6 August 2026 – 5 November 2026)
Views total1,618
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 16:58 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
1m 49s
Average length
11s

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 6 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).

5 Nov 2026, 06:26 UTC110 viewsread 5 November 2026
Photo

#95 #环保 #口爆 #丝袜制服 #角色扮演 #水床 #SM #龙岗 #坂田 #小小 #服务天花板 ♻️专业环保,课表上服务上百种,哥哥喜欢就来哦,没有妹妹做不到,只有哥哥想不到。95专业环保,氺床🛏上, SM ☎️私聊 @xxiao02 ☎️中转链接 @xxiao41 ☎️双向机器人: @xxiao369_bot ☎️电话 :17324499667

4 Nov 2026, 10:08 UTC211 viewsread 5 November 2026
Photo

艺名:#佳佳 深圳:#龙岗 私聊:@jiajia00568 双向:@jiajia00568bot 频道:https://t.me/jiajia00568xiaowo 消费:1300p 2300pp 验证:#视频已验证 标签:#舌吻 #长腿 #鸳鸯浴 #丝袜制服 #嫩妹 #三点粉

2 Nov 2026, 11:41 UTC315 viewsread 5 November 2026
Photo

艺名:#露露 深圳:#福田 私聊:@Luyy8788 双向:@Lutt9335Bot 频道:https://t.me/Luyy5566 消费:800p 1500pp 验证:#视频已验证 标签:#亲吻 #六九 #调情 #鸳鸯浴 #丝袜 #高跟 #嫩妹

2 Nov 2026, 06:27 UTC274 viewsread 5 November 2026
Photo

艺名:#西柚 深圳:#龙岗 私聊:@xiyou345 双向:@xiyou345bot 频道:https://t.me/+5UqcZBkHAsI3ODhl 消费:1300p 2300pp 验证:#视频已验证 标签:#亲吻 #六九 #调情 #鸳鸯浴 #丝袜 #高跟 #嫩妹

31 Oct 2026, 15:31 UTC389 viewsread 5 November 2026
Photo

艺名:#小雅 深圳:#龙岗 私聊:@COM000111 双向:@COM000333bot 频道:https://t.me/COM000222 消费:750p 1400pp 验证:#视频已验证 标签:#舌吻 #六九 #鸳鸯浴 #丝袜制服 #嫩妹 #长腿 #胸推 #三点粉

31 Oct 2026, 07:55 UTC319 viewsread 4 November 2026
Photo

艺名:#瞌睡虫 深圳:#龙岗 私聊:@ksc1314520 双向:@ksc492993_bot 频道:https://t.me/ksc492993 消费:500p 1000pp 验证:#视频已验证 标签:#六九 #鸳鸯浴 #口爆 #波推 #制服 #啪啪

11 Aug 2026, 08:23 UTC141 viewsread 12 August 2026
Photo

艺名:#诺诺 深圳:#龙岗 #坂田 私聊:@nuonu99 双向:@nuonuo8898_bot 频道:https://t.me/fuancai 消费:799p 1399pp 验证:#视频已验证 标签:#kiss #六九 #调情 #鸳鸯浴 #丝袜制服 #嫩妹 #啪啪

9 Aug 2026, 07:14 UTC315 viewsread 12 August 2026
Photo

艺名:#小虎牙 深圳:#龙岗 #坂田 私聊:@XiaOYYUO 双向:@ttsdkb_bot 频道:https://t.me/jsnsiise1 消费:900p 1500pp 验证:#视频已验证 标签:#舌吻 #六九 #鸳鸯浴 #调情 #丝袜制服 #嫩妹 #啪啪

8 Aug 2026, 15:33 UTC355 viewsread 12 August 2026
Photo

艺名:#小尤 深圳:#龙岗 私聊:@xiaoyoubaoba 双向:@kjiskjgh23367_bot 频道:https://t.me/gggghft 消费:800p 1200pp 验证:#视频已验证 标签:#亲嘴 #鸳鸯浴 #丝袜制服 #嫩妹 #长腿 #三点粉 #紧致

8 Aug 2026, 14:41 UTC341 viewsread 12 August 2026

龙华丢丢骗定金 @diudiu1121 不要信,妹子估计跑路了,中介骗定金。

8 Aug 2026, 09:20 UTC363 viewsread 12 August 2026
Photo

艺名:#思思 深圳:#龙岗 #龙岗中心城 私聊:@sisi_888 双向:@si520_bot 频道:https://t.me/sisi_8188 消费:700p 1300pp 验证:#视频已验证 标签:#舌吻 #六九 #鸳鸯浴 #丝袜制服 #长腿 #高跟鞋

8 Aug 2026, 06:45 UTC129 viewsread 9 August 2026
Photo

艺名:#妮妮 深圳:#龙岗 #坂田 私聊:@nini8981 双向:@nini8885bot 频道:https://t.me/ninini7733 消费:800p 1500pp 验证:#视频已验证 标签:#舌吻 #六九 #鸳鸯浴 #丝袜制服 #嫩妹 #长腿 #三点粉

Showing the 12 most recent of 17 posts we hold for @Sz3hdslg. 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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“深圳三和修车大队【龙岗区】” (@Sz3hdslg), 6,154 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/Sz3hdslg.

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.