Channel
@danbaoquan
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
26,458subscribers
-2,374 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001688767640 |
|---|---|
| Type | Channel |
| Username | @danbaoquan |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/danbaoquan |
Crypto & trading — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 12:58 | 26,458 | -111 |
| 16 Sept 2026, 22:18 | 26,569 | -75 |
| 14 Sept 2026, 22:19 | 26,644 | -97 |
| 13 Sept 2026, 05:37 | 26,741 | -136 |
| 11 Sept 2026, 06:56 | 26,877 | -103 |
| 8 Sept 2026, 07:59 | 26,980 | -375 |
| 5 Sept 2026, 02:17 | 27,355 | -134 |
| 3 Sept 2026, 09:06 | 27,489 | -183 |
| 2 Sept 2026, 02:22 | 27,672 | -174 |
| 1 Sept 2026, 00:36 | 27,846 | -94 |
| 30 Aug 2026, 22:53 | 27,940 | -164 |
| 29 Aug 2026, 22:36 | 28,104 | -159 |
| 28 Aug 2026, 23:14 | 28,263 | -185 |
| 27 Aug 2026, 20:45 | 28,448 | -2 |
| 26 Aug 2026, 22:39 | 28,450 | -55 |
| 26 Aug 2026, 01:04 | 28,505 | -82 |
| 25 Aug 2026, 03:45 | 28,587 | -119 |
| 23 Aug 2026, 21:35 | 28,706 | -88 |
| 22 Aug 2026, 06:05 | 28,794 | -36 |
| 20 Aug 2026, 23:34 | 28,830 | first reading |
16 posts held, back to 13 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 59 pages of 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 16 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
93 reactions across 16 posts, in 4 distinct kinds. The most used accounts for 96.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 90 | 96.8% | |
| 👏 | 1 | 1.08% | |
| 😁 | 1 | 1.08% | |
| 🤡 | 1 | 1.08% |
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 16 of the 16 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 93 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 13 May 2026 to 19 August 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.
浪漫七夕💘我与币总有个约会 一年一度七夕佳节，感谢大家一路以来对必安的陪伴与支持。 今天不谈业务，只请大家吃顿饭。也让大家体验一次属于必安家人的七夕浪漫。🌹 今天是必安形象代言人 币总 @BiLL 第一次正式和大家见面。 币总说： “第一次见面，总不能空着手来。” 所以今晚—— 🍚 777份猪脚饭，全部币总买单！ 不需要消费， 不需要做任务， 进群等开饭就行。 ⏰ 今晚20:00 正式开饭 📺 唯一活动现场：茶余饭后 @TTTV 有对象的，陪对象。 没对象的，今晚币总有约。 先进群占个座，晚上见～ 🤞 浪漫七夕 · 币总有约 今晚八点 · 不见不散
❤5
担保圈内实时新闻 ⚠️高度跑路嫌疑 担保平台“顶尖担保”疑似跑路，地址转出26wu 8月5日，有用户在社群中反映，担保平台“顶尖担保”关联地址已转出26wu，平台疑似已跑路。 据了解，顶尖担保所有客服及负责人账号已失联超过一周。早前已有知情者指出，顶尖担保所有客服及负责人的Telegram账号从一周前开始集体在线，但未发布任何通知便彻底失联。链上NFT钱包资金此前未动，圈内对其是“被端”还是“跑路”讨论激烈。此次地址出现26wu资金转出，进一步加剧了用户对其已跑路的担忧。 担保圈再次提醒： ❗️ 短时间接连出现担保平台资金出逃、停摆，近期入驻务必谨慎上押 ❗️ 无提前公告、私自大额转出押金资金的平台，跑路风险极高 ❗️ 负责人长期失联、回避押金兑付问题，不要抱有回款侥幸心理 📢 担保圈 @DanBaoQuan 将持续跟进顶尖担保资金转移及用户维权后续动态。 ⬅️返回首页
❤3
担保圈内实时新闻 2026年7月26日 当“危言耸听”成为现实：担保行业真正进入“剩者为王”的时代 早在行业最热闹、各种新担保疯狂涌现的时候，行业大佬必安担保就已经公开发表：《浅谈担保平台的选择之道》 【浅谈担保行业的选择之道：选对平台，赢定未来】 新小担保如雨后春笋，层出不穷，近期市场上更是涌现大量担保，纷纷打着“0月租、免费开群、仅收押金和退押手续费”的旗号，甚至提供流量扶持、红包奖励等各种诱人条件。然而，看似低门槛、高回报的承诺，背后往往隐藏着不可预知的风险。 流量稳定、信誉保障、收费合理，才是长期合作的关键！ 过去两年，必安已成功收购多个担保项目，并对市场动向进行了深入研究和观察。在此郑重提醒各位： 🔸 警惕资金盘骗局！ 许多担保的核心目的并非运营盈利，而是收取押金，圈押金的做盘套路，有很大的跑路风险。 🔸 担保行业并非慈善！ 任何正规经营模式都需要合理的盈利支撑，若担保仅靠押金存活，不考虑盈利模式，背后…
❤18😁1
担保圈内实时新闻 2026年7月24日 ⚠️高度跑路嫌疑 柬埔寨担保平台今日突发异常 平台核心上押钱包地址余额清零，目前未发布任何公告、未作出任何解释， TXFdekFzM2mVRRh6L36PPob8PPeo3vvvZm 担保圈再次提醒： ❗️ 短时间接连出现担保平台资金出逃、停摆，近期入驻务必谨慎上押 ❗️ 无提前公告、私自大额转出押金资金的平台，跑路风险极高 ❗️ 负责人长期失联、回避押金兑付问题，不要抱有回款侥幸心理 📢 担保圈 @DanBaoQuan 将持续跟进柬埔寨担保资金转移及用户维权后续动态。 ⬅️ 返回首页
❤4
担保圈内实时新闻 2026年7月24日 风险预警 担保平台索隆担保停业，被指变相跑路 今日，索隆担保公告即日起全面停业，称因运营压力及成本上升无法继续经营。但公告未提用户押金赔付及债务清算方案，引发圈内对其“跑路”的质疑。 疑点如下： · 停业即卖盘，未提用户赔付：按行业惯例，平台清退应优先公示用户上押资金赔付方案。索隆担保仅宣布终止运营，未就资金处置作任何说明。 · 社群出现“跑路”讨论：公告发布后，相关群组内用户反映联系不上客服、资金无法提现，官方至今无回应。 业内人士提醒，若平台已失联或拒不履行兑付义务，即属实质性跑路。 ⬅️ 返回首页
❤5
担保圈内实时新闻 2026年7月21日 风险预警 担保平台@wwdb 今日突发停运及资产打包转让公告，原文公告：https://t.me/wwdbgx/5274 操作模式与过往“海外担保”等平台跑路清退高度相似，圈内对其是否“变相跑路”、用户资金能否兑付疑虑陡增。 核心疑点如下： · 停运即卖盘，未提押金赔付：公告宣布停止运营后，未优先公示用户上押资金对应的赔付方案，第一时间放出完整资产售卖清单。按行业惯例，平台若真实清退，通常会先登记用户损失、给出资金兜底方案。 📢 担保圈 @DanBaoQuan 将持续跟进旺旺担保资产拍卖及用户资金兑付后续动态。 ⬅️ 返回首页
❤2
担保圈内实时新闻 2026年7月16日 海外担保㊙️辛揭露：从精聊出身，以身入局做担保客服，然后另起炉灶，最终还是走向爆雷！ 据超级索引官方公示及部分业内人士披露，海外担保操盘人员系精聊出身，后混入超级索引、钻石担保担任运营客服，其后因涉嫌滥用权限、卷走超级索引跟钻石担保公款，被公司开除。离开后另起炉灶，成立海外担保，并低价接手被封禁的@hwdb 账号，以近似“汇旺担保”的品牌包装重新入场。继续了精聊做盘之路！ 如今，海外担保宣称财务电脑被控制，多个地址内近30万U被盗，商户押金无法正常退回，并开始公示拍卖资产。 无论资金究竟因何失控，结果已经说明： 没有风控、没有资金隔离、没有赔付能力的小担保，本质上只是披着担保外衣的资金盘。 👍值得一提的是，超级索引 @cjsy 及其集团旗下钻石担保，由该人员引发资金风险时，展现出了非凡的魄力和担当，超级索引与钻石担保第一时间收回权限，注入资金，优先保障钻石担保公群老板及商户押金…
❤10
担保圈内实时新闻 2026年7月15日 风险预警 海外TG担保平台@hwdb突发异常公告，声称海外运营遭遇设备入侵、30多万U资产失窃，宣布打包处置全部TG资产，平台经营状态存大量疑点，资金离场风险需重点留意。 该海外担保平台近期对外发布停业变卖通知，多处操作逻辑反常，存在较高不确定性。 相关疑点证据如下： 平台自称财务电脑遭远程控制、三十余万U全部被盗，暂未对外公示链上被盗转账记录等有效佐证材料； 发布停业通知后，未优先公示用户上押资金对应的赔付方案，第一时间放出完整资产售卖清单； 待售资产包含导航频道@hwdbNB、供需频道@hwdbAF、16个群组频道、22个TG用户名NFT、合计100个公私社群、全套运营机器人所有权； 平台开放整体打包收购渠道，剩余零散资产计划电报群公开拍卖，负责人极少回应商家关于押金兑付的咨询。 常规平台若真实遭遇盗U事故，一般会优先留存证据、登记用户损失、给出资金兜底方案，极少出现事发直接批…
❤2
担保市场再添新品牌-熊猫担保 担保圈发现，近日一家名为 熊猫担保 的机构悄然上线，正式启动运营。 据熊猫担保方面介绍，该品牌由行业头部担保机构（多家龙头集团集合体）拆分设立。母公司长期承接高净值交易，因业务体量扩张，现成立独立品牌“熊猫担保”，专注精细化服务！ 熊猫担保方面称，其团队由原头部担保体系核心成员带队，均具备上万群以上的实操经验！一切流程标准化、简洁化，绝不拖泥带水。并集成最新技术与全新架构机器人，全面覆盖验群、拉群、转账核验等核心环节，体验丝滑顺畅。 在当前担保行业持续洗牌、商户更加重视平台稳定性的背景下，熊猫担保的上线，也为市场增加了一个新的选择。为防止假冒，特此公示官方通道： 开群联系：@xmkf 供求频道：@xmgx 公群导航：@xmgq 入驻流程频道：@peixunxm 作为第三方中立资讯频道的担保圈，我们也提醒各位老板：选择任何担保平台时，都应综合考察平台背景、资金安全、处理规则、赔付机制及实际口…
❤15👏1
担保圈内实时新闻 2026年7月1日 风险预警 继君赢担保出事之后，长安担保疑似跑路，押金地址转出20万USDT 经入驻老板交叉核实，长安担保近期出现重大资金异常，存在跑路重大嫌疑。 相关疑点证据如下： 平台核心上押钱包地址大额转出20万USDT，当前地址余额近乎清零 资金异动后负责人极少在线，多名用户私信询问押金兑付无任何回复 正常合规担保平台不会单方面清空押金地址、失联回避用户咨询，目前多名入驻老板均无法联系平台负责人核对账目。 担保圈再次提醒： ❗️ 短时间接连出现担保平台资金出逃、停摆，近期入驻务必谨慎上押 ❗️ 无提前公告、私自大额转出押金资金的平台，跑路风险极高 ❗️ 负责人长期失联、回避押金兑付问题，不要抱有回款侥幸心理 📢 担保圈 @DanBaoQuan 将持续跟进长安担保后续动态。 ⬅️ 返回首页
❤8🤡1
担保圈内实时新闻 2026年6月30日 君赢担保疑似借故停摆，高度嫌疑演戏跑路 经担保圈多方核实对比，君赢担保本次停摆事件嫌疑极大存在演戏成分，整体套路说辞与早前超乖担保跑路流程高度相似。 补充背景： ⚠️ 本次君赢担保对外说辞、操作节奏、对外话术，与往期超乖担保“被查停摆、变卖资产”跑路模板高度重合，嫌疑重大。 负责人曾为聚宝盆股东，过往存在涉案背景，本次突发停摆仅对外渲染个人及家庭原因、变卖资产养子女，全程回避平台押金处置事宜，圈内普遍质疑为借故脱身、变相跑路演戏操作。 担保圈再次提醒： ❗️ 套路、说辞、流程高度复刻历史跑路盘，务必提高警惕 ❗️ 只公示资产拍卖、不处理用户押金，属于极高风险跑路前兆 ❗️ 突发变故只讲个人理由、不谈用户兜底，大概率为演戏脱身 📢 担保圈 @DanBaoQuan 将持续跟进后续动态。 ⬅️ 返回首页
❤3
担保圈内实时新闻 2026年6月24日 TG预警快讯：汇金担保开业仅四月跑路 汇金担保上线运营未满四个月便全线失联，大批合作公群老板缴纳的上押资金全部无法挽回 平台套路十分险恶，前期开放免费供需板块吸引流量，无需任何成本就能发布交易信息，凭借零门槛优势快速拉拢大量公群老板入驻，短时间积累海量客户资源。等积攒足够客源后，上押的人蜂拥而至，可等到老板申请退押时，客服不断找借口拖延、推诿。 汇金担保直接注销全部官方账号、解散对接客服群，运营人员彻底失联，所有托管资金全部无法挽回。 此次事件彻底暴露线上担保行业乱象：大量新开皮包担保无资金兜底、无长期运营规划，先用免费服务做诱饵吸纳流量，再通过各类限制变相扣押用户押金，收割完毕直接跑路，行业底线缺失。 在此提醒所有公群老板，筛选合作担保务必提高风控意识。尽量远离。优先选择运营周期久、口碑透明、押款可顺畅赎回的老牌担保；不要将大额资金长期单一托管，分散合作降低亏损风险，谨防这…
❤1
Showing the 12 most recent of 16 posts we hold for @danbaoquan. 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.
Named by 6 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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“担保圈 @DanBaoQuan 官方指南” (@danbaoquan), 26,458 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/danbaoquan.
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.