Telegram RegisterThe public register of Telegram
Telegram profile photo for 查档圈全网免费社工库/脚本分享|开盒|开户 新闻

Channel

查档圈全网免费社工库/脚本分享|开盒|开户 新闻

@cuoguo86

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

18,306subscribers

-1,277 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002732049349
TypeChannel
Username@cuoguo86
Descriptiontelegram顶级团队运营 We follow the rules of the Telegram community to ensure the orderly operation of the channel and support dulov. We dislike pictures of groundhogs. If we have violated any rules, please contact and we will coope
CreatedBetween 1 June 2025 and 31 August 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live10 November 2026
Measurements held55
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/cuoguo86

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 94% 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 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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
@xiaoniangongyi/170131 Oct 2026, 03:33 UTC@cuoguo86/34676 · this entry31 Oct 2026, 03:34 UTC1.00under a minute
@xiaoniangongyi/17127 Nov 2026, 13:31 UTC@cuoguo86/34695 · this entry7 Nov 2026, 13:32 UTC1.00under a minute
@xiaoniangongyi/17138 Nov 2026, 02:54 UTC@cuoguo86/34697 · this entry8 Nov 2026, 02:54 UTC1.00under a minute
@xiaoniangongyi/17148 Nov 2026, 02:54 UTC@cuoguo86/34696 · this entry8 Nov 2026, 02:54 UTC1.00under a minute
@xiaoniangongyi/17168 Nov 2026, 02:56 UTC@cuoguo86/34699 · this entry8 Nov 2026, 02:56 UTC1.00under a minute
@xiaoniangongyi/17208 Nov 2026, 05:11 UTC@cuoguo86/34703 · this entry8 Nov 2026, 05:11 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
@xiaoniangongyi7 (7/7 hand-verifiable sample passed)1.00under a minute@xiaoniangongyi (7–0)

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. 7 of the 7 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 10 comparable posts for this entry, running 28 October 2026 to 8 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 2 channels, the one whose matching posts we hold earliest is @xiaoniangongyi. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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 2 registered channels linked by matching posts. 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

18,30619,58318,944.512 August 2026 — 19,583 subscribers12 August 2026 — 19,571 subscribers13 August 2026 — 19,540 subscribers16 August 2026 — 19,520 subscribers17 August 2026 — 19,500 subscribers18 August 2026 — 19,474 subscribers20 August 2026 — 19,459 subscribers20 August 2026 — 19,449 subscribers22 August 2026 — 19,429 subscribers23 August 2026 — 19,398 subscribers25 August 2026 — 19,385 subscribers26 August 2026 — 19,374 subscribers27 August 2026 — 19,369 subscribers28 August 2026 — 19,368 subscribers29 August 2026 — 19,358 subscribers30 August 2026 — 19,344 subscribers31 August 2026 — 19,338 subscribers1 September 2026 — 19,329 subscribers2 September 2026 — 19,324 subscribers3 September 2026 — 19,312 subscribers4 September 2026 — 19,301 subscribers7 September 2026 — 19,252 subscribers10 September 2026 — 19,213 subscribers12 September 2026 — 19,189 subscribers14 September 2026 — 19,161 subscribers15 September 2026 — 19,132 subscribers17 September 2026 — 19,111 subscribers28 September 2026 — 18,897 subscribers5 October 2026 — 18,816 subscribers9 October 2026 — 18,757 subscribers13 October 2026 — 18,725 subscribers14 October 2026 — 18,709 subscribers15 October 2026 — 18,705 subscribers16 October 2026 — 18,703 subscribers18 October 2026 — 18,705 subscribers18 October 2026 — 18,704 subscribers19 October 2026 — 18,703 subscribers21 October 2026 — 18,697 subscribers23 October 2026 — 18,700 subscribers24 October 2026 — 18,703 subscribers25 October 2026 — 18,697 subscribers26 October 2026 — 18,696 subscribers27 October 2026 — 18,695 subscribers29 October 2026 — 18,688 subscribers30 October 2026 — 18,648 subscribers31 October 2026 — 18,629 subscribers1 November 2026 — 18,630 subscribers2 November 2026 — 18,624 subscribers3 November 2026 — 18,445 subscribers4 November 2026 — 18,383 subscribers5 November 2026 — 18,376 subscribers6 November 2026 — 18,365 subscribers7 November 2026 — 18,342 subscribers9 November 2026 — 18,336 subscribers10 November 2026 — 18,306 subscribers12 August 202610 November 2026
55 measurements spanning 91 days, net -1,277. 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 18,114–19,775 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 55
Measured (UTC)SubscribersChange
10 Nov 2026, 16:4918,306-30
9 Nov 2026, 06:5518,336-6
7 Nov 2026, 20:0618,342-23
6 Nov 2026, 15:4018,365-11
5 Nov 2026, 13:2118,376-7
4 Nov 2026, 15:1618,383-62
3 Nov 2026, 13:1018,445-179
2 Nov 2026, 13:5818,624-6
1 Nov 2026, 12:4618,630+1
31 Oct 2026, 13:0618,629-19
30 Oct 2026, 14:1618,648-40
29 Oct 2026, 14:5118,688-7
27 Oct 2026, 15:5818,695-1
26 Oct 2026, 16:4618,696-1
25 Oct 2026, 13:2018,697-6
24 Oct 2026, 13:4418,703+3
23 Oct 2026, 10:3018,700+3
21 Oct 2026, 02:5918,697-6
19 Oct 2026, 21:4818,703-1
18 Oct 2026, 22:4718,704first reading

Engagement

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

ERR · 30 days
2.82%
avg views ÷ 18,306 subscribers
Avg views / post
517
49 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
49
of 82 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 10 November 2026
Posts held82 (22 July 2026 – 10 November 2026)
Views total25,323
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 04:49 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
112
Videos
1
Links
334

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

Recent posts

Telegram’s own ‘edited’ marker: 4 of 49 posts held from the last 30 days (8.16%) 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, 16:58 UTC272 viewsread 12 November 2026

🚩DeepSeek https://t.me/DeepSeekNB_bot?start=ref_aeBBPhlVGEn7UMFGwAK2AA

10 Nov 2026, 15:12 UTC296 viewsread 12 November 2026

🚩查档王社工库 https://t.me/cd777?start=ODAzMTYxODI5NQ==

10 Nov 2026, 15:11 UTC299 viewsread 12 November 2026

🚩核武器社工库 https://t.me/hewuqi?start=ref_6278447143

10 Nov 2026, 15:11 UTC298 viewsread 12 November 2026

🚩太极社工库 https://t.me/mfsgktjbot?start=8031618295

10 Nov 2026, 15:09 UTC292 viewsread 12 November 2026

🚩巨人社工库 https://t.me/jrsgk?start=ODAzMTYxODI5NQ==

8 Nov 2026, 06:17 UTC560 viewsread 12 November 2026
Photo

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

8 Nov 2026, 06:17 UTC508 viewsread 12 November 2026

✅医疗假地址全部公益不用签到不限制次数 /yljl /jdz https://t.me/taijijiaoliu

8 Nov 2026, 05:13 UTC464 viewsread 12 November 2026
File

河南参保,只能出河南入 ——热心网友 来自 @qwe_poi_action 搬运自 python_fenx频道 📮 点我投稿

8 Nov 2026, 05:12 UTC425 viewsread 12 November 2026
File

7.30-7.30 银行 批量二要素 无遗漏 @jiu_ren ——热心网友 来自 @qwe_poi_action 搬运自 python_fenx频道 📮 点我投稿

8 Nov 2026, 05:12 UTC363 viewsread 12 November 2026
File

二要素验证.py 微信小程序 #木鸟民宿订酒店 来自_ @jiu_ren 一个账号大概200头 切换手机号换账号 可更换 账号凭证 支持存储 自动切换 只要你储备的号多 就代表是无限线程 来自_ @jiu_ren 单 次 核 验 脚 本 二要 素 核 验 无 限 制 非 库 CK永远不过期 目前里面已备一个CK ——热心网友 来自 @qwe_poi_action 搬运自 python_fenx频道 📮 点我投稿

8 Nov 2026, 05:11 UTC310 viewsread 12 November 2026
File

猪逼自己改 ——@LoveYingHua 来自 @qwe_poi_action 搬运自 python_fenx频道 📮 点我投稿

8 Nov 2026, 05:11 UTC286 viewsread 12 November 2026
File

公网手机实名人核验纯野狗接口赶紧操死 token去喵走出行抓 ——@henhaiyuqing 来自 @qwe_poi_action 搬运自 python_fenx频道 📮 点我投稿

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

“查档圈全网免费社工库/脚本分享|开盒|开户 新闻” (@cuoguo86), 18,306 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/cuoguo86.

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.