25 Jun 2026, 16:20 UTC≈1,660 viewsread 7 August 2026
Video
Video, posted without a caption
Channel
防骗指南🐼
@fangpianxm
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,462subscribers
+57 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1003656837165 |
|---|---|
| Type | Channel |
| Username | @fangpianxm |
| Created | Between 1 December 2025 and 6 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/fangpianxm |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 09:14 | 1,462 | +21 |
| 10 Aug 2026, 20:51 | 1,441 | +25 |
| 8 Aug 2026, 06:46 | 1,416 | +11 |
| 7 Aug 2026, 10:16 | 1,405 | no change |
| 7 Aug 2026, 10:03 | 1,405 | first reading |
Engagement
18 posts held, back to 6 January 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 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 18 posts for this entry, the most recent from 25 June 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
8 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 6 | 75.0% | |
| ❤🔥 | 2 | 25.0% |
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 8 of the 18 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 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 6 January 2026 to 25 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
6 Jan 2026, 15:17 UTC≈2,580 views1 reactionsread 7 August 2026
因线下交易纠纷多且取证困难，双方交易前务必仔细阅读以下提醒 料方需留存以下证据： 1、完整切客记录 2、取款证明 3、打包视频 4、现场放货视频 5、鱼个人信息 车方需留存以下证据： 1、多角度暗哨视频（各角度的现场监控视频） 2、一镜到底取手拿货验货视频 建议在交易过程中，车方需作出以下预防措施： 1、防止现场监控视频丢失，现场可无人机监控和录制交易过程 2、防止夜间交易导致视频录制不清楚而成为无效证据，摄像头需有夜视功能， 3、防止包裹被第三方拿走，放货地点可加装和固定带锁铁箱 ·鱼放完包裹后要求上锁后离开 ·可在附近隐蔽地点藏一把钥匙，防止特殊情况需让鱼拿走包裹。 ⚠️注：以上仅为参考建议，如双方产生纠纷时，无法提供以上证据导致最终判定结果与预期不符的，自行承担责任。
❤1
6 Jan 2026, 15:17 UTC≈1,810 viewsread 7 August 2026
🔔🔔🔔 请认准以下真熊猫担保用户名： 熊猫供需： @xmgx （熊猫供需首字母） 核心大群： @xmdb （熊猫担保首字母） 新开公群： @xinqunxm （新群拼音全拼+熊猫首拼） 防骗指南: @fangpianxm 担保教程: @zhanshixm 有任何需要请联系客服 @xmkf （2026年6月25更新）
6 Jan 2026, 15:16 UTC≈1,500 views3 reactionsread 7 August 2026
私下交易违规案例 事件经过： 双方私聊对接，双方均未提及报备事宜即开始交易，交易后因公群商户质疑客户做假发生纠纷，因未按平台流程通过报备机器人(@xmbbbbot）报备交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款200U，奖励举报客户100U。 总结经验： 本起为一般类业务私下交易事件，此类公群交易需使用报备机器人报备交易（公群内亦有相关提醒），交易双方未遵守平台交易流程【交易前需报备，请联系商户通过报备机器人（@xmbbbbot）报备，交易方确认后再交易】，导致没有相关报备记录，故判定为私下交易。 ⚠️注意：该事件，由于客户私下交易导致损失165U，商户因违规私下交易罚款200U。 私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程【@gongqunxm】进行交易！
❤🔥2❤1
6 Jan 2026, 15:15 UTC≈1,110 viewsread 7 August 2026
⚠️中介套路一直存在，为避免广大用户被套路导致钱财损失，给予客户以下防骗提醒！ 常见的中介套路分以下3种情况： 1）利用时间差、信息差等等，在负责人不在的时候无法立即拉停的情况下交易，中介卷款跑路导致一方或双方受损失的情况。 2）供需双方正在交易，中介趁机浑水摸鱼发了入款信息，此时即使负责人立即反应并拉停，但是因为双方已开始交易，有时无法立即拉停或者拉不住的情况，也很容易导致一方或双方受损失的情况。 3）其中一方合伙中介套路交易方，通常为无押金方（需方）合伙中介套路押金方（供方），这类纠纷中介准备充足，团队配合默契，专注套路押金。 ❗️针对以上情景，请负责人一定要确认好人员，非己方人员不得给予身份。 ⚠️郑重声明：熊猫平台群内只有供需双方，不担保中介交易，产生纠纷自行负责！
6 Jan 2026, 14:50 UTC925 views2 reactionsread 7 August 2026
私下交易违规案例 事件经过： 客户在公群内报备金额后，双方私群对接交易，因纠纷问题公群方未记账，公群内交易记录不足，该笔交易因是否是P图问题发生纠纷，未按平台公群流程【@gongqunxm】交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款1000U，奖励举报客户500U。 总结经验： 本起私下交易违规事件，客户知晓应在公群内交易，但仅报备了金额，公群为公开的交易，仅有报金其他交易客户无法得知该笔报金是否有成功交易，（根据公群流程，相关交易记录需发到公群内，涉及隐私可以适当打码。）双方没有刻意要私下交易，但未按照公群流程交易，【交易需在群内进行叫卡、贴图、入账记账机器人的流程并保留交易记录。】导致公群内交易记录不足，判定为私下交易。 ⚠️注意：该事件由于客户私下交易导致损失1158U，商户因违规私下交易罚款1000U；私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程【@gongqu…
❤2
6 Jan 2026, 14:49 UTC736 viewsread 7 August 2026
【防骗必看】TG会员隐藏功能！教你用‘分组标签’远离假担保频道，操作简单。 第一步：收藏熊猫担保文件夹 “点击这里 ” 第二步：设置路径： 点击个人TG设置→选择对话文件夹→点击开启标签显示 ✅
6 Jan 2026, 14:48 UTC718 views0 reactionsread 7 August 2026
私下交易违规案例 事件经过： 双方私群对接交易，公群内无相关交易记录，客户入款冻结无法提供切客发生纠纷，因未按平台公群流程交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款1000U，奖励举报客户500U。 总结经验： 本起私下交易违规事件，客户未群内报备，商户因冻结群内未加账（回U群有加账不代表到账提醒），双方没有刻意要私下交易，但未按照公群流程交易，【交易需在群内进行报金、发水单或贴码、贴卡（涉及隐私可部分打码）、商户需要入账记账机器人的流程】导致公群内交易记录不足，判定为私下交易 ⚠️注意：该事件由于客户私下交易导致损失2916U，商户因违规私下交易罚款1000U； 私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程【@gongqunxm】进行交易！
6 Jan 2026, 14:48 UTC603 viewsread 7 August 2026
私下交易违规案例 事件经过： 双方私群对接交易，公群内仅有报金记录且报金金额与实际交易金额不符，私群内交易多笔,交易因料性问题发生纠纷，因未按平台流程交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款1000U，奖励举报客户500U。 总结经验： 本起私下交易事件，双方没有刻意要私下交易，但均未按平台交易流程交易【交易需在群内进行报金、发水单或贴码、贴卡（涉及隐私可部分打码）、商户需要入账记账机器人的流程】，双方私下对接交易，导致公群内交易记录不足，判定为私下交易。 ⚠️注意：该事件，由于客户私下交易导致损失769U，商户因违规私下交易罚款1000U。 私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程【@gongqunxm】进行交易！
6 Jan 2026, 14:48 UTC559 viewsread 7 August 2026
私下交易违规案例 事件经过： 双方私群对接交易，公群内仅有报金记录，交易因料性问题发生纠纷，因未按平台流程交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款1000U，奖励举报客户500U。 总结经验： 本起私下交易事件，双方没有刻意要私下交易，但均未按平台交易流程交易【交易需在群内进行报金、发水单或贴码、贴卡（涉及隐私可部分打码）、商户需要入账记账机器人的流程】，双方私下对接交易，导致公群内交易记录不足，判定为私下交易。 ⚠️注意：该事件，由于客户私下交易导致损失1304U，商户因违规私下交易罚款1000U。 私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程【@gongqunxm】进行交易！
6 Jan 2026, 14:47 UTC526 views0 reactionsread 7 August 2026
私下交易违规案例 事件经过： 双方私群对接交易，公群内仅有前几笔交易商户在公群内加帐，最后一笔交易公群内无相关交易记录，因该笔交易发生退款问题导致纠纷，因未按平台公群流程【@gongqunxm】交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款1000U，奖励举报客户500U。 总结经验： 本起私下交易违规事件，商户前期有在公群内加帐，最后一笔交易因纠纷未加帐，（根据公群流程，贴卡/码同样需要在公群内，涉及隐私可以适当打码。）双方没有刻意要私下交易，但未按照公群流程交易，【交易需在群内进行报金、发水单或贴码、贴卡（涉及隐私可部分打码）、商户需要入账记账机器人的流程】导致公群内交易记录不足，判定为私下交易 ⚠️注意：该事件由于客户私下交易导致损失1320U，商户因违规私下交易罚款1000U；私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程【@gongqunxm】进行交易！
6 Jan 2026, 14:47 UTC468 views1 reactionsread 7 August 2026
私下交易违规案例 事件经过： 双方私群对接交易，公群内无相关交易记录，私群内交易多笔，其中一笔交易超时查账发生纠纷，因未按平台公群流程【@gongqunxm】交易，纠纷不予受理。 处理结果： 商户违规【公群违规罚款须知】第一条，罚款1000U，奖励举报客户500U。 总结经验： 本起私下交易违规事件，商户未及时加账，只有每晚加总账（加总账与实际交易时间间隔过长，且总账无法核实加账对应的哪一位客户），双方没有刻意要私下交易，但未按照公群流程交易，【交易需在群内进行报金、发水单或贴码、贴卡（涉及隐私可部分打码）、商户需要入账记账机器人的流程】导致公群内交易记录不足，判定为私下交易 ⚠️注意：该事件由于客户私下交易导致损失961U，商户因违规私下交易罚款1000U；私下交易有风险，交易双方无保障，为避免不必要的损失，请按公群流程【@gongqunxm】进行交易！
❤1
Showing the 12 most recent of 18 posts we hold for @fangpianxm. 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 — 562,951 of 1,481,217entries 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.
Mentions
Named by 2 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“防骗指南🐼” (@fangpianxm), 1,462 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/fangpianxm.
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.