Channel
@pingan360
On this record: Growth · Engagement · Posts · Citations · Cite this entry
2,263subscribers
-87 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002374635154 |
|---|---|
| Type | Channel |
| Username | @pingan360 |
| 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/pingan360 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 15:07 | 2,263 | -55 |
| 10 Aug 2026, 15:07 | 2,318 | -32 |
| 7 Aug 2026, 13:48 | 2,350 | no change |
| 7 Aug 2026, 12:17 | 2,350 | first reading |
20 posts held, back to 25 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 1 pageof 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 27 July 2026 |
|---|---|
| Posts held | 20 (25 May 2026 – 27 July 2026) |
| Views total | 69 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 13:48 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.
🔔平安担保官方通知 近期小担保频繁跑路，各种假押盛行，特此公告！ 平安担保只有担保业务/专群业务！ 请注意平安担保没有其他任何业务！ “平安海外业务” “平安Trx 业务” “平安承兑业务”等所有业务均与平安担保无关！ 请认准我们的唯一号码与用户名： 平安： @PADB （+888 0000 1111） 神马： @SMDB （+888 1111 0000） 群管： @PPAA ❌其它均为假冒！❌ ❌其它均为假冒！❌ ❌其它均为假冒！❌
关于收款地址余额说明 平安担保采用去中心化钱包及 OKPAY 收款体系，收款地址仅用于收款，资金到账后自动归集管理，因此查询到地址无余额属于正常情况。 为降低公开地址带来的风控、冻结等风险，平台不会长期将资金存放于公开收款地址。单个地址余额仅代表该地址当前状态，无法反映平台整体资金情况。 平安担保已稳定运营6年，无任何跑路、卷款或恶意吞押等不良记录，平台信誉及履约能力均经过长期运营与实际口碑验证。
平安担保返现类公群纠纷处理原则 一、谁收款谁负责 客户直接充值至平台账户，由平台承担责任。 客户将资金转给公群方代充、代存，由公群方承担责任。 二、平台问题处理原则 客户通过公群推广进入第三方平台后，发生充值异常、提现异常、活动奖励未发放等情况，原则上属于客户与平台之间的纠纷。 公群方应积极协助处理。 三、平台跑路处理原则 如公群方推广的平台发生跑路、失联、关闭网站、无法提现等情况： 公群方有义务配合处理并提供相关说明。
【平安担保】 - 公群交易注意事项 进群交易前请认真阅读 【平安担保】 - 公群验群步骤： 点击查看 【平安担保】- 公群交易事项： 点击查看 【平安担保】- 公群防范诈骗： 点击查看 注意： 交易前请查看并遵守公群的置顶业务规则，避免纠纷。 所有交易必须在公群内完成（群内先报备再作业），涉及隐私信息可用*号代替，或联系业务员拉专群作业！ ⤵️联系官方：如有疑问，及时联系 🔵 @smdb 举报
✅公群流程快速导航 ①、公群人员名单 ②、真假群验证技巧 ③、公群老板交易注意事项 ④、公群客户交易注意事项 ⑤、公群收费标准/新开公群福利 ⑧、报备流程 ⑨、窗口群规范 ⑫、报备的重要性 ⑯、平安招租公群 ⑰、查询已上押金的担保公群 18 关于收款地址余额说明 一键收藏平安官方群频道🔥🔥🔥
群老板提供公群押金备用地址以及无法验证押金地址的规定 为了确保公群押金的安全性和透明性，我们在此公告如下： 1. 备用地址和备用账号： - 公群老板在上押时，平安担保建议提供备用下押地址和备用账号，以防止主账号或源地址失联。 - 若公群老板未提供备用地址和备用账号，在账号被注销或丢失的情况下，也可以通过源上押地址验证身份，更换新的账号。 - 若未提供备用地址和备用账号，平安担保将只认原账号和原地址。 2. 押金退还规定： - 公群老板在上押之后，如果出现公群老板被抓捕、无法联系等情况，管理层或任何其他人员均无权退还押金。 - 唯一的押金退还方式是通过录屏用原上押钱包转一笔帐并且记录里能看到上押记录和刚转账的记录。这一措施旨在避免被冒充或盗号的情况出现。 3. 公群老板无法联系时的处理： - 若公群老板无法联系到，平安担保将会留存押金，并在频道内向所有人公开相关押金信息和说明。 …
上押退押规则 1.上押必须是 @padb @smdb 是群管理,私自拉群无效! 2. 平安担保不收人民币只收u,也不帮任何换u! 3.上押三分钟内必须@担保确认押金、修改群名确定押金方可以操作!没有@担保查收和修改群名作业出问题不认! 4.退押-正常作业供需双方确认无纠纷,结算完佣金、方可退押! 5.退押-有些料主长时间不确认退押不回复群作业群内没有明显纠纷会强制退押!若有问题后果需方自负! 6.退押-新上押金群不管是原路退回、双方无纠纷、没有作业、作业没有超过2小时的,一律24小时后方可以退押.
专群退押流程： ①、交易结束后上押方提出退押，交易双方负责人确认交易结束，确认无纠纷， 担保方扣出担保费用后给予退押。 ②、交易过程中若交易方长时间不确认、不回复交易，没有明显纠纷，可向担保组申请公示强制退押时间，若到时间不处理，担保执行供方或者需方下押，有问题后果自行负责，之后如有问题平安概不处理。 ③、新上押金群，双方无纠纷、没有作业、作业没有超过2小时的,一律2小时后方可退押.骗子套路很多,所以不会立马退,一定要两个小时后用原地址才可以退。 ④、做好账户安全防护，退押认账号，掉号凭上押钱包转账核实后更换新账号进群处理 ⑤、退押下发流程一般半小时内完成。
专群上押流程： ①、合作双方恰谈好业务与交易规则后联系 @padb 拉担保群进行担保交易， 上押必须是 @padb @smdb 是群管理,私自拉群无效! ⚠️注意：个人简介和用户名的区别，靓号都有个人简介，用户名＋电话号码 双重防伪。 ②、担保组安排交易群对接后， 一定要认准官方账号，避免被拉假克隆群被骗。 ③、平安担保不会 不收人民币,只收u,也不帮任何人换u。 ④、找担保 上完押金,三分钟之内要找 @padb 核实确认,然后担保组修改群名后方可进行交易,在没改群名,没确认收到押金而且超时没@我们确认押金收到的情况下交易,造成的损失客户自己负责。 ⑤、交易双方进入交易群内说明、协商并确认交易详情，如：商品描述、收货标准、结算账期、收款标准、交易金额、交易数量、佣金金额、手续费等相关内容。 ⑥、交易双谈好业务规则，跟担保客服确认上押地址，客服人员核实收到押金后，确认供需双方以及双方人员给头衔改群名完成上押，供需…
公群违规罚款须知 1、公群交易和沟通必须在群内进行，公群引流群内不交易的群，仅限用于交流对接使用，交易必须联系 平安担保 @padb 拉专群，不允许诱导客户私聊交易或者拖延申报纠纷，公群如诱导客户私下交易，发现一次最低罚款20%押金起，最高视情况没收群押金。 2、跑分类公群，入金后公群业务人员应及时查账、加账、下发、 。料性不符的情况恶劣的将会做出没收押金或者劝退处理
公群交易流程规范 1、进群后请先确认是否为平安官方公群，进群之后联系担保 ：@padb @smdb 进行验证！ 2、验证真群后首先要确认群内管理员身份，认准供方负责人以及供方人员，并了解公群交易规则后，再进行交易。 3、仔细审核公群内置顶的规则，确定规则能接受再开始协商交易。 4、协商完成后公群方有义务主动对客户交易进行报备。必须先报备再交易
开公群和退押须知 ㊀、开群请先关注平安资料库，了解如何管理经营公群，群内提醒客户请勿相信私聊发群链接的，都是骗子，请直接拉黑； ㊁、新开公群会收录到公群导航【@shenmagq】内，如发现未上公群导航，请第一时间联系担保方； ㊂、开群后添加官方人员为联系人并备注信息，防止骗子冒充； ㊃、设置业务员必须是线下认识的才行，网上认识的不行，业务员出现的问题视为公群负责人全责； ㊄、所有管理员账号必须设置二步验证，防止被盗号，若出现账号被盗造成客户损失，公群方全责； ㊅、所有公群交易和沟通必须在群内进行对接，总之您们双方所有的对接记录都要展示在群内，不要乱删客户信息，违规操作罚款20%起起 并且收回所有权限。不允许诱导客户私聊交易或者拖延申报纠纷，公群如诱导客户私下交易，查实会视情况罚款。 ㊆、公群老板和业务员非必要情况下不要修改用户名，如需要修改用户名请第一时间联系群内担保号报备，擅自更改用户名公群内出现一切问题群内老板负全责。 …
Showing the 12 most recent of 20 posts we hold for @pingan360. 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 — 109,200 of 1,189,255entries 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 3 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.
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.
“📢平安资料库‼️” (@pingan360), 2,263 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/pingan360.
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.