Telegram RegisterThe public register of Telegram
Telegram profile photo for 大帅查档开户交流群

Channel

大帅查档开户交流群

@sfddd

On this record: Topic · Previous handles · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Cite this entry

20,494subscribers

-1,641 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003845323182
TypeChannel
Username@sfddd
CreatedBetween 1 February 2026 and 30 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 November 2026
Measurements held92
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/sfddd

Topic

Hacking & security — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.

Previous handles

@sfddd was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@dscd5555
held 7 August 2026 – 25 August 2026

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 7 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
@jscd88/90422 Aug 2026, 08:27 UTC@sfddd/644 · this entry22 Aug 2026, 09:06 UTC1.0039 minutes
@sfddd/671 · this entry28 Aug 2026, 14:29 UTC@jscd88/93628 Aug 2026, 14:34 UTC1.005 minutes
@sfddd/784 · this entry22 Sept 2026, 08:11 UTC@jscd88/106522 Sept 2026, 08:14 UTC1.004 minutes
@jscd88/107323 Sept 2026, 12:14 UTC@sfddd/788 · this entry23 Sept 2026, 15:34 UTC1.003.3 hours
@jscd88/9693 Sept 2026, 11:30 UTC@sfddd/798 · this entry28 Sept 2026, 07:57 UTC1.0025 days
@sfddd/815 · this entry5 Oct 2026, 04:23 UTC@jscd88/11135 Oct 2026, 05:22 UTC1.0059 minutes
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
@jscd889 (8/8 hand-verifiable sample passed)1.0052 minutesthis entry (6–3)
@tbxggg5 (5/5 hand-verifiable sample passed)1.0061 minutesthis entry (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. 5 of the 5 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 45 comparable posts for this entry, running 1 August 2026 to 12 October 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 7 channels, the one whose matching posts we hold earliest is @bgshark03. 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 keys clone_mutual · clone_source, 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 7 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

20,49422,79421,6447 August 202614 November 2026
92 measurements spanning 99 days, net -1,641. 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 20,149–23,139 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 92
Measured (UTC)SubscribersChange
14 Nov 2026, 06:5520,494-87
11 Nov 2026, 09:0620,581-99
9 Nov 2026, 12:4820,680-107
8 Nov 2026, 01:5120,787-82
6 Nov 2026, 22:1020,869-32
6 Nov 2026, 00:3020,901-48
5 Nov 2026, 03:2020,949-418
4 Nov 2026, 00:4621,367-162
2 Nov 2026, 22:4221,529-42
1 Nov 2026, 22:4921,571-37
31 Oct 2026, 22:2121,608-27
30 Oct 2026, 22:2921,635-38
29 Oct 2026, 20:5721,673-34
28 Oct 2026, 22:2021,707-62
27 Oct 2026, 18:0921,769-44
27 Oct 2026, 04:0121,813-9
26 Oct 2026, 20:0021,822-25
26 Oct 2026, 02:2621,847no change
25 Oct 2026, 18:0521,847-16
24 Oct 2026, 23:2721,863first reading

Engagement

170 posts held, back to 30 July 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 114 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 170 posts for this entry, the most recent from 12 October 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
261
Videos
2
Links
18

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. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

332 reactions across 134 posts, in 7 distinct kinds. The most used accounts for 78.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍26078.3%
❤5917.8%
🤓41.20%
🤡30.904%
😍20.602%
😨20.602%
🤣20.602%

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 137 of the 170 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 332 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 170 most recent posts we hold, published 30 July 2026 to 12 October 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

12 Oct 2026, 11:27 UTC≈1,120 views2 reactionsread 12 October 2026

立案详情 立案侦查 😃😃😃😀 只出最新一条 当天隔天回单 空收一半 私聊拿版 工作日18.00前当天回单 今天已经稳定回一批单子

👍2

12 Oct 2026, 09:49 UTC≈1,150 views3 reactionsread 12 October 2026

支付宝带id 微信不带id 一月😀😀😃😀三月😃😀😃😀 半年😀😃😃😀一年😀😃😃😃😀 两年😀😀😃😃😀三年😃😃😃😃😀 保真不保漏 ❗️当天回❗️当天回 上限8888 保真不保漏~ —————————————— 快线反诈流水❗️当天回单 一月 😃😃😃😀三月 😃😃😃😀 半年😃😃😃😀一年😀😀😃😀 利息收费 出单收费 保真不保漏上限1000

👍3

12 Oct 2026, 08:40 UTC≈1,190 views1 reactionsread 12 October 2026

公网机主 周五开 公网名下手机号 周四开 独家!条出!给原图! 部分号码注销 或者人已经在国外,过不了三要素 不接受扯皮

👍1

12 Oct 2026, 08:00 UTC≈1,150 views2 reactionsread 12 October 2026

名下资产 福利 😀😃😃😀 法院直出,附法院拍照回单 1. 名下全部银行卡卡号 + 账户余额(剔除:不活跃账户、睡眠卡、已注销卡) 2. 名下全部实名微信账户余额 3. 名下全部实名支付宝账户余额 4. 名下股票、证券、保险资产信息 敏感别报 扣费不给单 3-7天回 板子私聊

👍2

12 Oct 2026, 07:04 UTC≈1,170 views2 reactionsread 12 October 2026
Photo

名下卡不带余 😃😃😃😀 保真不保漏 回单周期:3个工作日! ————————————————- 名下所有卡号带余额 😀😀😃😀 保真不保漏 敏感人物 扣单 敏感包括 公检法 各大人物 回单时间:报单日开始3-7天回单 余额有失败的(反馈不出来)介意勿报!

👍2

11 Oct 2026, 12:24 UTC≈1,220 views3 reactionsread 12 October 2026
Photo

【名下资产查询】 提供身份证号码姓名报单 (北京、上海户籍不要) 反馈: 💰名下支付宝微信账户余额 💰名下银行卡账户余额 💰名下房,名下车辆,民政婚姻,名下保险、证券(系统反馈多少给多少) 回单时间3-5天左右 😃😀😃😀 只做源头业务,所有业务均经过埋雷测试,支持一切售后,欢迎打假,可放心下单

👍3

11 Oct 2026, 11:12 UTC≈1,220 views6 reactionsread 12 October 2026
Photo

我不想做任何不认识的春江公群业务员 老板的单子 说起来也是干查档的 基本的常识都没有,单子少,事特别多 订单号都不会验证,神人

👍6

11 Oct 2026, 09:45 UTC≈1,210 views4 reactionsread 12 October 2026
Photo

美团最新地址 😀😃😃😀 一年内最新十条 一条也收费 文件回单 已测试 真正的美团 提供:手机号报单 3-5天回 ————————————————— 淘宝闪购外卖地址 😃😃😀 订单收货地址 无遗漏 一年最新1-10条 当天的也能出来 找人首选 用的人多 基本都是外卖 提供:手机号 当天回

👍4

10 Oct 2026, 14:22 UTC≈1,270 views4 reactionsread 12 October 2026
Photo

一年内美团饿了么😀😀😃😀 目前空车 来的明天回⚡️ 目前不止外卖还有很多电商购物一体‼️ 1-2天回单 基本上无遗漏 私聊拿模板 带订单编号 下单人手机号 收货人手机号 收货地址 商家名称 商家地址 商家id 商品详情 提供:手机号 无需身份证

👍4

10 Oct 2026, 07:38 UTC≈1,280 views3 reactionsread 12 October 2026

公网微信两件套 开 😀😀😃😀 1-2天左右回

👍3

9 Oct 2026, 15:34 UTC≈1,300 views2 reactionsread 12 October 2026

真地址 个户 😃😀 人在秒 人在秒 人在秒 24小时个户带头 批量可谈 19:30以后出头唯一线路

👍2

9 Oct 2026, 05:06 UTC≈1,330 views2 reactionsread 12 October 2026

司法冻结 😃😃😃😀 反炸出单 原图出单 有流水 有经办 晚上回 晚上回

❤1👍1

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

@sfddd edited 2 posts 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
25 August 2026
Most recent edit
2 September 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @sfddd as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
21 August 2026
Most recent seen missing
11 October 2026
Median time before seen missing
31 hours
Seen missing in the last 30 days
0

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

15 Aug 2026, 11:02 UTCAnonymous Poll37 voters

需不需要助理

  1. 需要84%
  2. 不需要22%

The shares total 106%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 170 most recent posts we hold, published 30 July 2026 to 12 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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.

“大帅查档开户交流群” (@sfddd), 20,494 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/dscd5555.

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.