🎁 推荐关注 🎁

Channel
骗子公布
@dxpzbgq
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
484subscribers
+188 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003261318297 |
|---|---|
| Type | Channel |
| Username | @dxpzbgq |
| Created | Between 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 1 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 1 October 2026 |
| On Telegram | t.me/dxpzbgq |
Topic
Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 07:01 | 484 | +13 |
| 16 Sept 2026, 02:21 | 471 | +32 |
| 13 Sept 2026, 05:22 | 439 | no change |
| 8 Sept 2026, 09:00 | 439 | +51 |
| 29 Aug 2026, 06:04 | 388 | +49 |
| 23 Aug 2026, 01:06 | 339 | +40 |
| 15 Aug 2026, 02:54 | 299 | +3 |
| 14 Aug 2026, 05:01 | 296 | first reading |
Engagement
8 posts held, back to 2 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 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 20.0%
- avg views ÷ 484 subscribers
- Avg views / post
- 97.0
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 8 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.
| Window | Rolling 30 days · latest post in window 11 September 2026 |
|---|---|
| Posts held | 8 (2 September 2026 – 11 September 2026) |
| Views total | 194 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Sept 2026, 05:22 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.
Recent posts
🚨 骗子警告通知 🚨 类型: 👤 用户账号 用户名: @Ru768 用户ID: @Ru768 诈骗类型: 其他骗子 举报次数: 1 风险等级: 🔴 高风险 描述: 9596\.vip 一群死狗,三万多条106,充值八个人头,三个绑定验证,说我通道有问题,六百多u不结算。天天被曝光的臭狗。恶心死人。用户名:@Ru768 @dlrb888999 @ap0002 @cuicui8801 @AS188866 @ting15 @ppmy258 @ws00007 举报时间: 2026-09-11 17:31:51 --- ⚠️ 防范提示: • 请勿向此账户/地址转账 • 不要点击可疑链接 • 遇到类似情况请及时举报 • 保护好个人信息和资产 💡 如有误报,可通过机器人申诉功能提交申诉。
🎁 推荐关注 🎁
关联上一条 https://t.me/dxpzbgq/739 🚨 骗子警告通知 🚨 类型: 👤 用户账号 用户名: @Xiangfeng88889999 用户ID: @Xiangfeng88889999 诈骗类型: 短信骗子 举报次数: 1 风险等级: 🔴 高风险 描述: 注意合兴三个跑路狗, 骗子tg:@pk9888888 @Xiangfeng88889999 @Laok918888888 合兴跑路4万u,不想结账说你上水,给出的上水证据搞笑道离谱,给的手机号码自己不知道在哪里编的号码,盘口也没有这些号码注册,还找盘口客服确认过,如果号码存在是可以找回密码的 💰 关联钱包地址: TEf2tXfuT7DcrHMTZy5hjC5ztjdDpBU6jf 举报时间: 2026-09-05 07:09:47 --- ⚠️ 防范提示: • 请勿向此账户/地址转账 • 不要点击可疑链接 • 遇到类似情况请及时举报 • 保护好…
🎁 推荐关注 🎁
🚨 骗子警告通知 🚨 类型: 👤 用户账号 用户名: @Als1888888 用户ID: @Als1888888 诈骗类型: 短信骗子 举报次数: 1 风险等级: 🔴 高风险 描述: 前面跟他合作过,给我介绍机房后就跟失踪了一样,他介绍的机房也是,预付过去了,今天是第三天,还没有消息,真的是贱逼来的吧 @Yy91918 这是他介绍的机房,大家注意了 TB42uuRZaCYpFQNaQXLLqEp36e2fjugFTY TWk1JQ6Jk498Cf72Yxm7kmSpKRxhGceybV **💰 钱包地址:** • `TB42uuRZaCYpFQNaQXLLqEp36e2fjugFTY` • `TWk1JQ6Jk498Cf72Yxm7kmSpKRxhGceybV` 举报时间: 2026-09-02 07:46:29 --- ⚠️ 防范提示: • 请勿向此账户/地址转账 • 不要点击可疑链接 • 遇到类似情况请及时举报…
🎁 推荐关注 🎁
🚨 骗子警告通知 🚨 类型: 👤 用户账号 用户名: @HG66656 用户ID: 7659921745 诈骗类型: 其他骗子 举报次数: 1 风险等级: 🔴 高风险 描述: 在tg上找卖抖音直播号的,找到这一家有公群担保的,欧易公群,还能验群是不是真群,上压了多少u,以为是正儿八经做生意的卖家,确认好了价格50u,也在公群报备好了,结果就是u转过去了,对方要付款截图也发过去了,然后就发过来一个手机号,再给了一个0\.1u的假链接,要授权的钱包合约,实际无限大的权限,钱包有多少钱都能给你转走,我意识到被骗之后,去找公群仲裁,结果仲裁告诉我要再交40u,完了仲裁完了之后一并返还,我说谁家仲裁还要再交钱啊?搞笑呢?仲裁人员直接给我消息清除记录,然后我找另一个公群工作人员,跟我说让你他妈的交40u你不交,然后就给我消息记录清除了。 💰 关联钱包地址: TWmDqtW9SunT5yvMLYvKPziosd4cJb9GS2 举…
Showing the 8 most recent of 8 posts we hold for @dxpzbgq. 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.
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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“骗子公布” (@dxpzbgq), 484 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/dxpzbgq.
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.