🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰 🤓【天成担保 @TCDB 官方大群防骗重要公告】🤓 📌诈骗案例通报 📌 案件类型:骗子冒充BC料入款其他欺诈料。出现问题后失联不处理 📌骗子相关信息: 骗子账号: @jn1997888 8776290748 @aj202677 6362551730 📌安全提醒 交易前请务必核实盘口料性 对于保料性双方协商双押 所有资金操作必须在担保流程内完成
❤3

Channel
@fangpianzc
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry
9,080subscribers
+2,438 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 |
| Description | 供需频道 @tcgx 公群频道 @tcgq 招商频道 @tczs 官方大群 @tcdb 每日公群 @tcxq 官方公告 @tiancheng 担保负责人 @tctc 出海负责人 @bcbc 仲 裁 组 @tczc 24小时客服机器人 @tckf 免费记账机器人 :@tcjz |
| 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 | 15 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/fangpianzc |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Nov 2026, 16:45 | 9,080 | +210 |
| 10 Nov 2026, 03:18 | 8,870 | +130 |
| 6 Nov 2026, 07:46 | 8,740 | +162 |
| 2 Nov 2026, 21:36 | 8,578 | +160 |
| 30 Oct 2026, 21:59 | 8,418 | +119 |
| 28 Oct 2026, 03:16 | 8,299 | +102 |
| 25 Oct 2026, 00:27 | 8,197 | +110 |
| 22 Oct 2026, 11:10 | 8,087 | +153 |
| 18 Oct 2026, 18:25 | 7,934 | +123 |
| 16 Oct 2026, 00:06 | 7,811 | +113 |
| 12 Oct 2026, 14:06 | 7,698 | +207 |
| 6 Oct 2026, 07:20 | 7,491 | +29 |
| 29 Sept 2026, 13:41 | 7,462 | +127 |
| 19 Sept 2026, 18:00 | 7,335 | +76 |
| 15 Sept 2026, 11:19 | 7,259 | -49 |
| 11 Sept 2026, 16:18 | 7,308 | +203 |
| 6 Sept 2026, 22:18 | 7,105 | +52 |
| 2 Sept 2026, 01:43 | 7,053 | +100 |
| 29 Aug 2026, 17:39 | 6,953 | -76 |
| 26 Aug 2026, 17:04 | 7,029 | first reading |
8 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 40 pages of 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 23 October 2026 |
|---|---|
| Posts held | 8 (27 May 2026 – 23 October 2026) |
| Views total | 1,710 |
| Reactions total | 3 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 17 Nov 2026, 02:35 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.
Lifetime counters from Telegram’s own channel header, read 17 November 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.
30 reactions across 7 posts, in 4 distinct kinds. The most used accounts for 90.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 27 | 90.0% | |
| 👎 | 1 | 3.33% | |
| 😁 | 1 | 3.33% | |
| 😍 | 1 | 3.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 8 of the 8 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 30 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 27 May 2026 to 23 October 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.
Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰 🤓【天成担保 @TCDB 官方大群防骗重要公告】🤓 📌诈骗案例通报 📌 案件类型:骗子冒充BC料入款其他欺诈料。出现问题后失联不处理 📌骗子相关信息: 骗子账号: @jn1997888 8776290748 @aj202677 6362551730 📌安全提醒 交易前请务必核实盘口料性 对于保料性双方协商双押 所有资金操作必须在担保流程内完成
❤3
【天成担保 @TCDB 官方大群防骗重要公告】 📌诈骗案例通报 【公群2899 阴阳群套路欺诈客户】 一、纠纷描述 客户申报纠纷反馈,称公群2899存在使用“阴阳群”方式对接客户并实施欺诈交易的情况。 根据客户提供的录屏、聊天记录、公群报备记录及相关截图核实: 客户前期由冒充公群业务员的账号进行交易对接。当客户提出需要在公群内进行报备时,客户对应的交易信息随后由公群2899真实业务员在真实公群内完成报备。 报备完成后,冒充业务员账号随即取得真实公群内的报备截图,并将截图发送至客户所在的对接群,以此取得客户信任。 同时,在相关对接过程中,还存在使用真实业务员账号拉群、使用与真实交易客户相似的用户名进行报备及对接等情况。 客户在确认公群内存在真实报备记录,并收到公群2899真实进群链接后,基于上述信息完成交易。交易完成后出现款项未下发、对接业务员失联的情况。 二、客户1核实时间线 10月4日 客户被拉入对接群,与冒充业务员账号进…
❤6👎1😁1
【天成担保 @TCDB 官方大群防骗重要公告】 📌诈骗案例通报 【公群2053 阴阳群套路欺诈客户】 一、纠纷情况说明 客户申报纠纷反馈称:其前期曾与公群方建立真实对接群,但双方并未在该群内发生实际交易。后续,客户被拉入假冒业务员所在的对接群,并在该群内进行交易。期间,客户的真实报备信息却同步出现在公群内,且由公群真实业务员完成相关报备。 根据客户提供的录屏、聊天记录、切客记录、公群报备记录,以及公群方自述等材料,对本次纠纷进行核实,具体情况如下: 1、关于报备信息: 公群方称,群内相关报备信息已被客户删除,但现有证据显示,客户在假对接群内提交的报备信息,随后出现在公群内,并存在公群业务员代为报备的情况。 2、关于交易回款: 公群方反馈,涉事交易已向客户下发回款。但经核对公群方提供的收款地址及相关记录,发现其中有两笔收款未见对应的回款下发记录,公群方的说法与现有记录存在不一致。 3、关于交易去向及鱼的核销情况: 公群方后…
❤3
📣 天成担保|品牌形象焕新公告 为进一步提升【天成担保】的品牌形象与辨识度,天成担保此前举办了品牌设计大赛,从众多优秀设计作品中筛选出最符合天成担保品牌理念与形象定位的设计方案,并结合品牌整体设计方向进行优化与调整,最终呈现出全新的品牌视觉形象。 现【天成担保】全新品牌视觉形象正式公布: ✨ 全新官方头像 —— 展现更加鲜明的品牌形象 🎭 专属 Emoji —— 打造更具辨识度的天成专属符号 🎬 品牌动态图 —— 让天成形象更加生动、更具活力 即日起,天成担保各官方平台将陆续更换并启用全新的品牌视觉形象,敬请大家关注与留意! 🚀 全新形象,全新面貌;初心不变,服务升级! 🗓 发布日期|2026年8月31日
🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰 🤓天成担保防骗提醒🤓 💡通报日:2026年6月25日 📌 案件类型:利用小数点金额混淆实施诈骗 📌 诈骗手法摘要: 经核查,某用户拟与公群方开展交易。在公群方尚未完成报价及确认交易细节前,该用户主动发送转账截图,并声称已支付1,088U。 公群方随后对转账记录进行核实,发现实际到账金额仅为1.088U,与其所声称的1,088U相差近千倍。 该用户利用转账金额中的小数点差异,刻意通过截图视觉误导,试图使交易对方误认为已收到1,088U,从而达到骗取货物或服务的目的,具有明显欺诈意图。 因公群方及时核对实际到账金额及链上记录,成功识别异常,未造成实际资金损失。 📌 骗子用户名: 骗子 哈喽 ID:@GG5268 📌 骗子转帐地址: TXe6R92hGv6XTfGZDuvQUP6rjjDkZ5KKFW ❗️ 注意事项(请务必遵守) 天成担保提醒所有用户: 任何交易均应以实际到账金额及链…
❤6😍1
🤓【天成担保 @TCDB 官方大群防骗重要公告】🤓 📌诈骗案例通报 📌 案件类型:天成担保公群1102 群老板,准备以【天成担保】名义开设假群欺诈平台客户,损害平台声誉、破坏用户权益。 📌骗子相关信息: 公群1102 押金2000u 华天盘口贴纸直营 用户名 @Niuniu7741(妞妞收一线中介量大可上浮) ID: 7353453603 骗子地址:TAtzxzoymtsjpE44xnQCVFLCJK77Gv1WSG 处罚结果: 1、罚没公群1102 押金2000U 2、奖励举报客户 200U 3、在平台【防骗曝光频道】给予曝光,平台对一切损害平台声誉、破坏用户权益、实施欺诈行为的个人或团体坚决零容忍。无论采取何种方式或手段,一经发现,平台将严肃追责,维护所有客户的合法权益。 ⚠️ 该公群情节恶劣罚并针对平台客户实施欺诈行为罚没公群押金该账号已被担保方第一时间标注为骗子,并已全频道曝光,请所有用户务必提高警惕,切勿上…
❤5
🇸🇰🇸🇰🇸🇰🇸🇰🇸🇰 🤓【天成担保 @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 8 most recent of 8 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.
We recorded 2 posts on @fangpianzc as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
Named by 14 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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“防骗曝光频道” (@fangpianzc), 9,080 subscribers as measured 15 November 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.