Telegram RegisterThe public register of Telegram

Channel

骗子曝光(骗子查寻)@pzbg6

@pzbg6

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

1,316subscribers

+0 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1003461339921
TypeChannel
Username@pzbg6
Description💬灰产总部 @jmsq9 👩🏼‍💻打造最权威曝光平台 ✅永久保存骗子资料 曝光联系 @bansui9987 📋
Created25 November 2025measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/pzbg6

Growth

1,31611 Aug 2026, 20:02 — 1,316 subscribers11 Aug 2026, 20:15 — 1,316 subscribers11 Aug 2026, 20:0211 Aug 2026, 20:15
2 measurements taken within a single day. 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 1,315–1,317 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 20:151,316no change
11 Aug 2026, 20:021,316first reading

Engagement

9 posts held, back to 25 November 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 9 posts for this entry, the most recent from 24 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
5
Videos
1
Links
5

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

Video runtime
29s
Average length
29s

Measured directly from 1 video 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.

Reaction mix

14 reactions across 3 posts, in 6 distinct kinds. The most used accounts for 35.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍535.7%
428.6%
🔥214.3%
👏17.14%
😁17.14%
🥰17.14%

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

Measured over the 9 most recent posts we hold, published 25 November 2025 to 24 June 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

24 Jun 2026, 02:52 UTC137 viewsread 11 August 2026

大家好 我是半岁 时隔多日 我回来了 还有认识我的吗 https://t.me/TGJM15 我都这个群找我玩😁

10 Feb 2026, 08:02 UTC856 viewsread 11 August 2026
Photo

用户名 @huangwf168 @znnzz11 @qq402619606 不变🆔 https://t.me/@id5699617906 https://t.me/@id8273710395 https://t.me/@id8129705509 避雷兄弟们吃相难看 达利882

28 Jan 2026, 11:11 UTC≈1,030 views2 reactionsread 11 August 2026
Photo

跑路狗 @wuming28 不变🆔https://t.me/@id8020773175 企业v代实名25一个前边做了5个应该结125他说结一半我说结80结了之后又做了5个一直不结账说发代付了第二天双清了

2

28 Jan 2026, 09:27 UTC886 viewsread 11 August 2026
Photo

跑路狗ID:@Xihuan7i 不变🆔 https://t.me/@id8478910886 被骗过程:上了个今日头条 上完之后说找代付找三天了 被骗金额:35 投稿人:张 惜 缘

28 Jan 2026, 09:06 UTC718 viewsread 11 August 2026
Photo

@haitaonb520 永久不变🆔 https://t.me/@id7678526747 这个人是骗子 大家注意 换名字换头像了 之前的ID也换了 大家注意

28 Jan 2026, 08:58 UTC650 viewsread 11 August 2026

本频道今日改为骗子曝光频道,请大家积极来找我曝光,让我们一起改善这个圈子的环境! 发布格式: 点击下方即可复制 跑路狗ID: 被骗过程: 被骗金额: 投稿人: 📣曝光联系:@bansui0 双向联系: @bs9988bot

28 Nov 2025, 10:37 UTC≈2,520 views7 reactionsread 11 August 2026
Forwarded from @bansuinb666

不知不觉已经在灰产圈摸爬滚打了十年,建立这个平台的初衷是希望大家能够抱团取暖、互帮互助来打破灰产行业之间的壁垒,了解到好的项目,在灰产路上不再孤单,由衷的希望大家都能早日赚钱上岸!

👍4👏1🔥1😁1

25 Nov 2025, 01:51 UTC≈2,280 views5 reactionsread 11 August 2026

我是半岁,我回来了、

2👍1🔥1🥰1

Showing the 9 most recent of 9 posts we hold for @pzbg6. 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.

Citation-graph rank

Citation-graph rank — 394,283 of 1,336,469entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“骗子曝光(骗子查寻)@pzbg6” (@pzbg6), 1,316 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/pzbg6.

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.