Channel
@xbfpx
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
80,218subscribers
+1,676 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002684528638 |
|---|---|
| Type | Channel |
| Username | @xbfpx |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/xbfpx |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 11:33 | 80,218 | +9,285 |
| 15 Aug 2026, 20:56 | 70,933 | -7,609 |
| 14 Aug 2026, 19:16 | 78,542 | first reading |
17 posts held, back to 9 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 6 pagesof Telegram’s post history, 20 posts per page.
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 16 August 2026 |
|---|---|
| Posts held | 17 (9 September 2025 – 16 August 2026) |
| Views total | 13,100 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Aug 2026, 10: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.
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.
📢 新币担保重要公告 大家注意了，发个安全通知： 🚨 核心风险提示 近期经团队核实和技术摸排发现：有人专门利用第三方恶意机器人（如计算器、发布任务等机器人）在群内进行监听，随后实施抢包、冒领快递、抢劫U商以及“点鱼”诈骗。请大家务必提高警惕！ ⚠️ 紧急排查与防范 1. 立即自查专群：请大家赶紧检查自己群里的非新币机器人，防止其留有后门、泄露隐私。 2. 切勿私下乱拉：在私下对接交易时，千万不要随意邀请任何第三方机器人进群。交易时间、地点等核心信息一旦泄露，极易被有心人盯上。 安全第一，规避风险，请大家互相转告！
近期市面出现很多假担保，这里教大家如何辨别真假担保： 1️⃣公群导航 2️⃣供需频道 3️⃣交流群 首先从以上三个地方查看人数，然后点击客服，查看是否客服为同一个。 ⚠️：一定要核对三处地方，每个担保都必须具备这些频道，并看清订阅人数！
专群组：@xbzq111-@xbzq999 公群组：@xbjy111-@xbjy666 ——————————————— 新币人工客服 验群客服 @xbkf 公群导航 @xbqqg 备用 @xbgq 供需频道 @xbrgx 备用 @xbdh 官方大群 @xbbda 备用 @xbbd 公告频道 @XINBlKEFU 新币搜索🔍中文搜索🔍 @xbss ———————————————
⚠️中介套路一直存在，为避免广大用户被套路导致钱财损失，给予客户以下防骗提醒！ 常见的中介套路分以下3种情况： 1）利用时间差、信息差等等，在负责人不在的时候无法立即拉停的情况下交易，中介卷款跑路导致一方或双方受损失的情况。 2）供需双方正在交易，中介趁机浑水摸鱼发了入款信息，此时即使负责人立即反应并拉停，但是因为双方已开始交易，有时无法立即拉停或者拉不住的情况，也很容易导致一方或双方受损失的情况。 3）其中一方合伙中介套路交易方，通常为无押金方（需方）合伙中介套路押金方（供方），这类纠纷中介准备充足，团队配合默契，专注套路押金。 ❗️针对以上情景，请负责人一定要确认好人员，非己方人员不得给予身份。 ⚠️郑重声明：土豆平台群内只有供需双方，不担保中介交易，产生纠纷自行负责！
私下交易违规案例 事件经过： 双方私聊对接，双方均未提及报备事宜即开始交易，交易后因公群商户质疑客户做假发生纠纷，因未按平台流程通过报备机器人(@XGZbbbot）报备交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款200U，奖励举报客户100U。 总结经验： 本起为一般类业务私下交易事件，此类公群交易需使用报备机器人报备交易（公群内亦有相关提醒），交易双方未遵守平台交易流程【交易前需报备，请联系商户通过报备机器人（@XGZbbbot）报备，交易方确认后再交易】，导致没有相关报备记录，故判定为私下交易。 ⚠️注意：该事件，由于客户私下交易导致损失165U，商户因违规私下交易罚款200U。 私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程进行交易！
私下交易违规案例 事件经过： 双方私群对接交易，公群内仅有报金记录，交易因料性问题发生纠纷，因未按平台流程交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款1000U，奖励举报客户500U。 总结经验： 本起私下交易事件，双方没有刻意要私下交易，但均未按平台交易流程交易【交易需在群内进行报金、发水单或贴码、贴卡（涉及隐私可部分打码）、商户需要入账记账机器人的流程】，双方私下对接交易，导致公群内交易记录不足，判定为私下交易。 ⚠️注意：该事件，由于客户私下交易导致损失1304U，商户因违规私下交易罚款1000U。 私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程进行交易！
私下交易违规案例 事件经过： 双方私群对接交易，公群内仅有前几笔交易商户在公群内加帐，最后一笔交易公群内无相关交易记录，因该笔交易发生退款问题导致纠纷，因未按平台公群流交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款1000U，奖励举报客户500U。 总结经验： 本起私下交易违规事件，商户前期有在公群内加帐，最后一笔交易因纠纷未加帐，（根据公群流程，贴卡/码同样需要在公群内，涉及隐私可以适当打码。）双方没有刻意要私下交易，但未按照公群流程交易，【交易需在群内进行报金、发水单或贴码、贴卡（涉及隐私可部分打码）、商户需要入账记账机器人的流程】导致公群内交易记录不足，判定为私下交易 ⚠️注意：该事件由于客户私下交易导致损失1320U，商户因违规私下交易罚款1000U；私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程进行交易！
私下交易违规案例 事件经过： 开始客户有在公群内正常报备交易，后续交易时商户表示由己方代报备，客户即未报备，双方对于礼品卡是哪一方核销问题发生纠纷，因未按平台流程交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款1000U，奖励举报客户500U。 总结经验： 本起私下交易违规事件是由于商户代报备引起，（因代报备平台无法核实报金对应的是哪一位客户，所以代报备属于无效报备）双方知晓交易流程，但未按照公群流程交易，【交易需在群内进行报金、发水单或贴码、贴卡（涉及隐私可部分打码）、商户需要入账记账机器人的流程】导致公群内交易记录不足，判定为私下交易 ⚠️注意：该事件由于客户私下交易导致损失1493U，商户因违规私下交易罚款1000U；私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程进行交易！
私下交易违规案例 事件经过： 起初交易前双方沟通时客户告知商户报备，商户表示目前人多需等待，晚点报备。后来双方在商户未报备的情况下产生交易，客户也未核实商户有无报备（客户需在群内确认报备），交易后续双方对于粉是否符合要求发生纠纷，因未按平台流程报备交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款200U，奖励举报客户100U。 总结经验： 本起为一般类业务私下交易事件，此类公群交易使用报备机器人报备交易，双方知晓交易前需报备，但都未遵守平台交易流程【交易前需报备，请联系商户通过报备机器人（ @XGZbbbot ）报备，交易方确认后再交易】，导致没有相关报备记录，故判定为私下交易。 ⚠️注意：该事件，由于客户私下交易导致损失153U，商户因违规私下交易罚款200U。 私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程进行交易！
私下交易违规案例 事件经过： 客户在公群内报金后双方私聊对接，拉私群交易多笔，后续因料性问题出现纠纷，公群内无交易记录，未按平台流程交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款1000U，奖励举报客户500U。 总结经验： 本起是较为常见的私下交易事件，双方没有刻意要私下交易，但都未按平台交易流程交易【交易需在群内进行报金、发水单或贴码、贴卡（涉及隐私可部分打码）、商户需要入账记账机器人的流程】，全程私下对接，导致公群内交易记录不足，判定为私下交易。 ⚠️注意：该事件，由于客户私下交易导致损失700U，商户因违规私下交易罚款1000U；私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程进行
经常会有些骗子冒充工作人员发一些名为“财务报表”“工作流程”之类的文件，或者用一些话语诱导你点开一些文件，一定要反复确认对方身份后再做决定，还有说是给后台实则是给了下木马的网站链接的，不要点击陌生人发的文件，上图是一些常见案例。还有一些骗子利用一些舆论哗众取宠，吸引用户点进某个频道，里面通常会有一个病毒文件在等待下载。
TG常见骗术介绍： 1、冒充TG账号发送链接 不要随意点击陌生人发送的任何文件和链接，对方发送的很可能是木马文件或者是自动下载脚本的链接，点击后就会危害到你的电脑，有被盗号甚至其他更严重的风险。即便遇到以飞机官方名义发送的任何文件与链接都不要点击，图中标识处是链接，点进去号就会被盗（图1）。 2、冒充好友让协助解封 有时会遇到一些人假冒好友以帮助解封为由让帮忙收验证码，实则是在登录你的账号，对方会骗取你的验证码或聊天界面的截图，从而盗取你的账号（图2）。切记！登录验证码不要外泄！！ 3、冒充飞机账号的诈骗短信 诈骗短信冒充Telegram 账号，声称该用户的TG 账号违反了账号使用规则将被限制使用，需要登陆网站解除受限。如果用户不慎点击链接，账户就会被盗（图3）。 4、当用户下载使用了带有后门的 TG 程序，会被自动检测聊天中的区块链地址，并且当检测到用户聊天消息中的钱包地址时，会将钱包地址替换成诈骗分子自己的地址，造成…
Showing the 12 most recent of 17 posts we hold for @xbfpx. 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 — 1,205,030 of 1,480,975entries 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.
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.
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.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“新币防骗指南” (@xbfpx), 80,218 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/xbfpx.
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.