Channel
@fangpianzc
On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
6,846subscribers
+204 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002392537703 |
|---|---|
| Type | Channel |
| Username | @fangpianzc |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/fangpianzc |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 15:08 | 6,846 | +99 |
| 10 Aug 2026, 08:01 | 6,747 | +78 |
| 7 Aug 2026, 16:32 | 6,669 | +27 |
| 7 Aug 2026, 12:17 | 6,642 | first reading |
5 posts held, back to 27 May 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 9 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 24 July 2026 |
|---|---|
| Posts held | 5 (27 May 2026 – 24 July 2026) |
| Views total | 941 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 02: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.
12 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 91.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 11 | 91.7% | |
| 😍 | 1 | 8.33% |
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 4 of the 5 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 12reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 27 May 2026 to 24 July 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.
🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰 🔈近期，天成担保接获客户举报，骗子冒充天成担保二组业务员「天权」身份，在其他担保平台及拍卖群内发布不实言论，恶意混淆视听，诋毁天成担保，并伪造官方资料及频道信息，疑似企图误导用户，严重损害天成担保官方形象。 经天成担保官方核实，该账号并非天成担保任何官方工作人员，与天成担保无任何关联。其行为已严重影响天成担保声誉，并容易误导广大用户，在此郑重声明并提醒各位提高警惕，谨防受骗！ 📌 骗子曝光：冒充官方身份，散布不实言论📌 📌 骗子账号： 账号：@tc22l ID：8522051145 📌 骗子伪造 Bio 内容： 🚫 天成担保官方大群：@TCGFDQ 🚫 天成担保供需频道：@TCGXL 🚫 天成担保公群频道：@TCXQL 🚫 天成官方公告频道：@JDTCD 以上频道均非天成担保官方频道，请勿相信或加入，以免遭受诈骗或误导。 📌安全提醒： ⚠天成担保官方业务员仅以官方公布账号为准，请勿仅凭用户名、…
🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰 🤓天成担保防骗提醒🤓 💡通报日：2026年6月25日 📌 案件类型：利用小数点金额混淆实施诈骗 📌 诈骗手法摘要： 经核查，某用户拟与公群方开展交易。在公群方尚未完成报价及确认交易细节前，该用户主动发送转账截图，并声称已支付1,088U。 公群方随后对转账记录进行核实，发现实际到账金额仅为1.088U，与其所声称的1,088U相差近千倍。 该用户利用转账金额中的小数点差异，刻意通过截图视觉误导，试图使交易对方误认为已收到1,088U，从而达到骗取货物或服务的目的，具有明显欺诈意图。 因公群方及时核对实际到账金额及链上记录，成功识别异常，未造成实际资金损失。 📌 骗子用户名： 骗子 哈喽 ID：@GG5268 📌 骗子转帐地址： TXe6R92hGv6XTfGZDuvQUP6rjjDkZ5KKFW ❗️ 注意事项（请务必遵守） 天成担保提醒所有用户： 任何交易均应以实际到账金额及链…
❤4😍1
🤓【天成担保 @TCDB 官方大群防骗重要公告】🤓 📌诈骗案例通报 📌 案件类型：天成担保公群1102 群老板，准备以【天成担保】名义开设假群欺诈平台客户，损害平台声誉、破坏用户权益。 📌骗子相关信息： 公群1102 押金2000u 华天盘口贴纸直营 用户名 @Niuniu7741（妞妞收一线中介量大可上浮） ID: 7353453603 骗子地址：TAtzxzoymtsjpE44xnQCVFLCJK77Gv1WSG 处罚结果： 1、罚没公群1102 押金2000U 2、奖励举报客户 200U 3、在平台【防骗曝光频道】给予曝光，平台对一切损害平台声誉、破坏用户权益、实施欺诈行为的个人或团体坚决零容忍。无论采取何种方式或手段，一经发现，平台将严肃追责，维护所有客户的合法权益。 ⚠️ 该公群情节恶劣罚并针对平台客户实施欺诈行为罚没公群押金该账号已被担保方第一时间标注为骗子，并已全频道曝光，请所有用户务必提高警惕，切勿上…
❤3
🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰 🤓【天成担保 @TCDB 官方大群防骗重要公告】🤓 2026年5月31日，骗子以购买供需为由，利用转小额p图，进行行骗。已成功被担保业务员成功识别。骗子已被担保方标记为骗子，在此曝光，并提醒大家！注意防骗！ 📌骗子曝光：转小额p图📌 🔈转账3.188 usdt，p图3,188 usdt，利用小数点“.”跟英文逗号“,”不仔细看容易混淆的漏洞来行骗 📌骗子用户名： 骗子 王涛(资金来往语音确认) ID：@wangtao138 📌骗子地址：TYo3mSLZeYB8ZvA22zyR3ktpheeAPsqm2r 📌安全提醒：收款时候要仔细甄别，认真核对到底是小数点还是逗号‼‼‼ 📞 官方联系方式： 🇸🇰 天成一组业务员：@tc00 🇸🇰天成二组业务员： @tc22 🇸🇰仲裁组 瑶光：@tczc 🇸🇰 天成担保客服机器人：@tiankf_bot
❤3
🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰 🤓【天成担保 @TCDB 官方大群防骗重要公告】🤓 📌诈骗案例通报 📌 案件类型：假上押公群，假频道，假机器人，假业务员 📌骗子相关信息： 假公群：公群1352押金3668u小雪集团高价租各种账号 假频道： @TCDQ @TETE @TCGlX 骗子账号：@xue966 @ruan65 假机器人：@ltcqgbot @tian_xbot 假业务员：@fofo @Itczc @tcdbg26 @tcdbjqh66 @tcoo 冒用天成担保，冒用天成担保业务员头像，冒用天成机器人，模仿业务员UID&电话号码,模仿开群设置，开设假群。 💙公群验群，私聊成担保机器人 @tian_rbot发送需要验证的公群编；输出假编号或错误编号，机器人会提示你：❌无编号xxx公群，千万不要交易！ 💙专群验群，我们官方公告 @JDTC 以及其他公开频道中都有置顶我们的官方信息，请注意与群内成员进行比对： 1…
❤1
Showing the 5 most recent of 5 posts we hold for @fangpianzc. 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 — 192,045 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.
Named by 15 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.
@fangpianzc named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“防骗曝光频道” (@fangpianzc), 6,846 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/fangpianzc.
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.