Telegram RegisterThe public register of Telegram
Telegram profile photo for 0押金小额口令/高收入/BC一手/项目群

Channel

0押金小额口令/高收入/BC一手/项目群

@zfbddddd

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

5,768subscribers

-4,284 since we began measuring on 27 September 2026

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

Register entry

Telegram ID-1001882720455
TypeChannel
Username@zfbddddd
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live16 November 2026
Measurements held15
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/zfbddddd

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 28 September 2026 and assigned it the closest of 31 fixed categories, at 35% 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 3 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
@zfbzfb888/7712 Sept 2026, 16:14 UTC@zfbddddd/422 · this entry27 Sept 2026, 03:14 UTC1.0014 days
@zfbzfb888/1963 Oct 2026, 06:05 UTC@zfbddddd/766 · this entry15 Oct 2026, 16:14 UTC1.0012 days
@zfbzfb888/2629 Oct 2026, 16:44 UTC@zfbddddd/725 · this entry13 Oct 2026, 16:24 UTC1.004 days
@zfbzfb888/39722 Oct 2026, 17:07 UTC@zfbddddd/925 · this entry24 Oct 2026, 12:37 UTC1.0043 hours
@zfbzfb888/41826 Oct 2026, 04:35 UTC@zfbddddd/956 · this entry26 Oct 2026, 16:04 UTC1.0011 hours
@zfbzfb888/5125 Nov 2026, 04:39 UTC@zfbddddd/1144 · this entry7 Nov 2026, 02:37 UTC1.0046 hours
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
@zfbzfb8887 (7/7 hand-verifiable sample passed)1.002 days@zfbzfb888 (7–0)
@trqqdgjkv7 (7/7 hand-verifiable sample passed)1.00under a minute@trqqdgjkv (4–3)

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. 11 of the 11 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 29 comparable posts for this entry, running 27 September 2026 to 15 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 3 channels, the one whose matching posts we hold earliest is @zfbzfb888. That is a statement about our reading window, not a claim of authorship.

Views per post sit far below this size band

1.7 average views per post against 8,345 subscribers — an engagement rate of 0.02%. Across the 1,160 registered channels in the same cohort — 3,187–9,995 subscribers, posting mainly in Chinese — the middle half sit between 2.60% and 18.1%, with a median of 7.24%.

What this was computed from
Window30 days (6 October 2026 – 5 November 2026)
Posts measured31 of 31 published in the window (31 exact, 0 rounded by Telegram)
Views totalled52
Mature posts only0.025% over 19 posts read at least 24h after publication
Subscribers8,345 measured 3 November 2026
Cohortb3162:zho · 1,160 channels · p10 0.513% · p25 2.60% · p50 7.24% · p75 18.1% · p90 36.9%
Position in cohort0.173th percentile · 1/333 the cohort median
Uncertainty±0% of the figure, from Telegram’s rounding
Post languageChinese · 100.0% of the window’s posts

When this is recorded. A channel is listed here only when its engagement rate sits at or below the 1st percentile of its cohort and is at least 3× away from that cohort’s median — below it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.

This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.

Recorded under the keys clone_copy · clone_mutual · err_low, last confirmed 16 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 3 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

5,76810,0597,913.527 September 2026 — 10,052 subscribers27 September 2026 — 10,052 subscribers4 October 2026 — 10,056 subscribers9 October 2026 — 10,057 subscribers13 October 2026 — 10,059 subscribers22 October 2026 — 10,054 subscribers23 October 2026 — 10,032 subscribers24 October 2026 — 10,001 subscribers25 October 2026 — 9,925 subscribers28 October 2026 — 9,445 subscribers31 October 2026 — 8,748 subscribers3 November 2026 — 8,345 subscribers7 November 2026 — 7,792 subscribers10 November 2026 — 6,832 subscribers16 November 2026 — 5,768 subscribers27 September 202616 November 2026
15 measurements spanning 50 days, net -4,284. 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 5,124–10,703 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Nov 2026, 15:545,768-1,064
10 Nov 2026, 19:266,832-960
7 Nov 2026, 00:177,792-553
3 Nov 2026, 21:158,345-403
31 Oct 2026, 17:568,748-697
28 Oct 2026, 08:569,445-480
25 Oct 2026, 04:579,925-76
24 Oct 2026, 03:1410,001-31
23 Oct 2026, 03:2710,032-22
22 Oct 2026, 01:5110,054-5
13 Oct 2026, 10:5710,059+2
9 Oct 2026, 09:1810,057+1
4 Oct 2026, 20:4110,056+4
27 Sept 2026, 11:2210,052no change
27 Sept 2026, 10:4710,052first reading

Engagement

70 posts held, back to 9 September 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 21 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.023%
avg views ÷ 5,768 subscribers
Avg views / post
1.3
39 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
39
of 70 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 15 November 2026
Posts held70 (9 September 2026 – 15 November 2026)
Views total51
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 11:31 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
19m 38s
Average length
49s

Measured directly from 24 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 39 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).

15 Nov 2026, 07:48 UTC1 viewsread 16 November 2026
Video

新系统商户代充接单教程🥇🀄️😖⚡️ 系统接收到帐号订单收录后正常下发订单😀🀄️😖 有问题咨询客服😀 @zfb8888887 😀支付宝口令😀 纯博彩盘口线上供料 ↓24小时自助下单↓ 自助下单地址:http://ng667.top 24小时备用链接http://ag668.top ❕如打不开平台链接复制到浏览器打开 ❕如支付风控可退回订单页面重新发起支付或选其他支付通道进行支付❕ 😀双向客户:@zfb8888887_bot

14 Nov 2026, 07:48 UTC1 viewsread 14 November 2026
Video

TG必备的索引机器人!超级索引帮您精准找到:群组、频道、音乐、视频等 👇点击下方按钮,开启搜索把!👇

14 Nov 2026, 04:10 UTC1 viewsread 16 November 2026
Video

新系统商户代充接单教程🥇🀄️😖⚡️ 系统接收到帐号订单收录后正常下发订单😀🀄️😖 有问题咨询客服😀 @zfb8888887 😀支付宝口令😀 纯博彩盘口线上供料 ↓24小时自助下单↓ 自助下单地址:http://ng667.top 24小时备用链接http://ag668.top ❕如打不开平台链接复制到浏览器打开 ❕如支付风控可退回订单页面重新发起支付或选其他支付通道进行支付❕ 😀双向客户:@zfb8888887_bot

12 Nov 2026, 16:05 UTC1 viewsread 16 November 2026
Video

新系统商户代充接单教程🥇🀄️😖⚡️ 系统接收到帐号订单收录后正常下发订单😀🀄️😖 有问题咨询客服😀 @zfb8888887 😀支付宝口令😀 纯博彩盘口线上供料 ↓24小时自助下单↓ 自助下单地址:http://ng667.top 24小时备用链接http://ag668.top ❕如打不开平台链接复制到浏览器打开 ❕如支付风控可退回订单页面重新发起支付或选其他支付通道进行支付❕ 😀双向客户:@zfb8888887_bot

12 Nov 2026, 04:01 UTC1 viewsread 16 November 2026
Video

新系统商户代充接单教程🥇🀄️😖⚡️ 系统接收到帐号订单收录后正常下发订单😀🀄️😖 有问题咨询客服😀 @zfb8888887 😀支付宝口令😀 纯博彩盘口线上供料 ↓24小时自助下单↓ 自助下单地址:http://ng667.top 24小时备用链接http://ag668.top ❕如打不开平台链接复制到浏览器打开 ❕如支付风控可退回订单页面重新发起支付或选其他支付通道进行支付❕ 😀双向客户:@zfb8888887_bot

11 Nov 2026, 05:14 UTC1 viewsread 16 November 2026
Video

新系统商户代充接单教程🥇🀄️😖⚡️ 系统接收到帐号订单收录后正常下发订单😀🀄️😖 有问题咨询客服😀 @zfb8888887 😀支付宝口令😀 纯博彩盘口线上供料 ↓24小时自助下单↓ 自助下单地址:http://ng667.top 24小时备用链接http://ag668.top ❕如打不开平台链接复制到浏览器打开 ❕如支付风控可退回订单页面重新发起支付或选其他支付通道进行支付❕ 😀双向客户:@zfb8888887_bot

10 Nov 2026, 05:09 UTC1 viewsread 16 November 2026
Video

新系统商户代充接单教程🥇🀄️😖⚡️ 系统接收到帐号订单收录后正常下发订单😀🀄️😖 有问题咨询客服😀 @zfb8888887 😀支付宝口令😀 纯博彩盘口线上供料 ↓24小时自助下单↓ 自助下单地址:http://ng667.top 24小时备用链接http://ag668.top ❕如打不开平台链接复制到浏览器打开 ❕如支付风控可退回订单页面重新发起支付或选其他支付通道进行支付❕ 😀双向客户:@zfb8888887_bot

10 Nov 2026, 00:24 UTC1 viewsread 10 November 2026
Photo

🔥 找资源、搜资讯,就来瞬搜! 🔍 搜索、🎵 音乐、📰 新闻、🛠 工具 一站整合,想用什么快速直达! 告别繁琐查找,少走弯路更省心 👇 点击下方,马上开启精选导航

9 Nov 2026, 19:20 UTC1 viewsread 10 November 2026

— 专业索引工具 · 整合海量信息资源 — 索引机器 @SUOBOT|@SYJQ 专业的信息索引与搜索平台,能帮你快速发现、重要资讯,出海推广营销助手!telegram频道、群组、视频等内容收录检索。

9 Nov 2026, 18:37 UTC1 viewsread 10 November 2026

— 专业索引工具 · 整合海量信息资源 — 索引机器 @SUOBOT|@SYJQ 专业的信息索引与搜索平台,能帮你快速发现、重要资讯,出海推广营销助手!telegram频道、群组、视频等内容收录检索。

9 Nov 2026, 18:26 UTC1 viewsread 10 November 2026

— 专业索引工具 · 整合海量信息资源 — 索引机器 @SUOBOT|@SYJQ 专业的信息索引与搜索平台,能帮你快速发现、重要资讯,出海推广营销助手!telegram频道、群组、视频等内容收录检索。

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

“0押金小额口令/高收入/BC一手/项目群” (@zfbddddd), 5,768 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/zfbddddd.

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.