Channel
@DBFWLB
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
8,121subscribers
-94 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001643281998 |
|---|---|
| Type | Channel |
| Username | @DBFWLB |
| Description | 每天实时更新全网担保服务状态 共建电报中文担保生态环境 |
| 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 | 17 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 17 August 2026 |
| On Telegram | t.me/DBFWLB |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Aug 2026, 10:23 | 8,121 | -4 |
| 14 Aug 2026, 03:57 | 8,125 | -47 |
| 10 Aug 2026, 19:16 | 8,172 | -40 |
| 8 Aug 2026, 05:10 | 8,212 | -3 |
| 7 Aug 2026, 12:16 | 8,215 | first reading |
7 posts held, back to 28 November 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 11 pagesof 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 7 posts for this entry, the most recent from 8 December 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 18 August 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.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
168 reactions across 7 posts, in 10 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 84 | 50.0% | |
| 👍 | 28 | 16.7% | |
| 🔥 | 16 | 9.52% | |
| 👏 | 15 | 8.93% | |
| 🥰 | 13 | 7.74% | |
| 🎉 | 7 | 4.17% | |
| 🐳 | 2 | 1.19% | |
| ☃ | 1 | 0.595% | |
| ✍ | 1 | 0.595% | |
| 🤩 | 1 | 0.595% |
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 7 of the 7 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 168reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 28 November 2025 to 8 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
2025/12/8更新 网友投稿：骗子UID：8037138134 骗子昵称：新發担保·公群负责人 骗子用户名： KOKO 骗子作案过程：这个担保是一个假押 这个担保目前是旗下有三个假押 一个是 koko 一个是 idaye 和 cpddt 新發担保的公群里的地址余额只有40多U 并且公群内的项目全都是假的 请大家谨防上当受骗 自己担保做假押都做不好还去曝光别人 假押负责人的手机号码：+86 18315194118 请大家睁大双眼好好看清楚 请记住：邪恶永远压制不了正义！ 备注：大家走担保一定要看清用户名以及匿名号码，有很多假押担保模仿一些正规担保，用户名就相差一位，大家交易的时候细心一点。 ✈️ 担保服务商收录及信息修改 ✈️ 全网担保列表 ✈️ 担保常见骗术 ✈️ 全网供需查询 🔥 娱乐圈千万押金 🔥 腾博会电子 👉 投稿联系
❤38🔥4🥰3👍2👏2🎉1
2025/12/6更新 据多名用户反映，火狐担保存在恶意拖延退还押金的行为。公群老板自11月23日起多次联系担保负责人要求退还押金，但对方以“负责人有事”、“现实中出事情”等借口故意拖延，至今未履行退款。在此期间，该担保地址（TVBkV6EdmkdrZz7L2o4fWEt6WpTmk6Scmk）仍显示正常活跃状态，可见其并非无法操作，而是故意不退押金。 恶意拖延以各种虚假理由拒绝按时退还押金； 担保方在仍有活跃操作的情况下，拒不履行下押 此行为已实质构成“变相跑路”，损害用户利益。 该担保虽然规模较小，但此类行为已严重破坏信任基础。请所有用户提高警惕，谨慎选择担保渠道，避免继续上当受骗。如有类似遭遇，建议保留证据并及时通过社群渠道公开曝光，防止更多人受害。 备注：请务必通过正规、可信的渠道进行交易或担保，对于缺乏透明度和信用记录的小型担保服务，应保持警惕，避免财产损失。 ✈️ 担保服务商收录及信息修改 ✈️ 全网担…
❤12🐳2👍2🔥2✍1🎉1🥰1
2025/12/2更新 网友投稿：此人以买卖盘口招助理等手段骗取押金，昨天晚上收助理押金10000u往上，凌晨的时候把我们踢了 ，找个借口说群死了，到现在频道还在收割，大家注意点 备注：望大家转发一下别让此人在忽悠人，继续收割了。快过年了希望大家看紧自己的钱包。下期将曝光一个担保跑路，担保负责人已经有10天左右没回消息下押。 ✈️ 担保服务商收录及信息修改 ✈️ 全网担保列表 ✈️ 担保常见骗术 ✈️ 全网供需查询 🔥 娱乐圈千万押金 🔥 腾博会电子 👉 投稿联系
❤8👏7👍6🥰3🔥2
2025/12/2更新 网友投稿：骗子不变id :8.434.947.121 骗子用户名: @aayyz91 关于网传“YY担保将被收购”的澄清声明 致各位合作老板及各界朋友： 近期，我们留意到账号名为“言言”的主体在其主页简介中发布“马上收购@yydb”的不实言论，该内容与事实严重不符，已对YY担保的品牌声誉及正常经营造成不良影响。在此郑重澄清：YY担保作为亿级担保体系孵化的子担保机构，始终安全稳定运营，当前、未来均无任何被收购的可能，相关传言纯属无稽之谈。 我们严正谴责“言言”的不实言论行为，其未经核实便散布虚假信息、恶意抹黑我方的做法，违背商业诚信原则，损害行业良性发展秩序。在此敦促“言言”摒弃不良企图，秉持诚信底线，立即删除相关不实内容，停止一切损害我方权益的行为。 YY担保将持续坚守稳定经营理念，稳步推进业务发展，切实保障合作方权益。对于任何编造、传播虚假信息、损害我方声誉的行为，我方严厉谴责！再次重申，我方不存在被…
❤7👍3🔥3👏2🎉1🥰1
2025/11/30更新 网友投稿：lhdb lhgq lhlh lhgx llhh sisi sxdb 这些账号目前已经被“假压海森”拿走了，这里面的水很深，他们正准备坑人！ 说什么“劳务之家上压10万”，大家觉得这可能吗？担保还给一个曝光上压，这不是明摆着扯淡吗？稍微动脑想想都知道有问题。 了解内情的朋友都清楚“只只”和“海森”之间的关系。海森原本就是“富府担保假押”的创始人，2024年11月到2025年1月期间被曝光假押金1.10的记录，事后他干脆把“虎牙担保原劳务之家”卖掉了。而在拍卖过程中，那个“只只”闪亮登场，用6万U拿下了群聊——结果被爆出来，只只其实就是海森本人，或者是他手下的小弟。 之前“领航担保”在的时候，这帮人就喜欢恶意诋毁、P图造谣，现在又换了个壳继续出来骗。 目前已知上述ID已经被海森控制，但很多人还不清楚里头的套路，因为这水太深了！建议大家保持警惕，不要再相信他们的话 另外，如果各位中介看到新出现的…
❤9👍7🥰4🔥2🎉1
😄😄😄😄—供需频道招募计划 😀招募对象：供需频道的拥有者 👤如果您需要更多的频道曝光 👤如果您想增加频道投稿收入 😐服务内容：流量曝光远程投稿 👤行业导航—供需板块永久展示 👤搜索引擎—关键词汇永久展示 👤联盟成员—我的追踪永久推送 👤远程投稿—低价收费随时提现 😐加盟方法：点击此处查看教程 👤自定义供需消息价格 👤自定义供需消息媒体 👤自定义供需消息按钮 👤兼容大会员表情与富文本
❤5👏3👍2🔥1🤩1🥰1
2025/11/28更新 据悉，领航担保目前已确认跑路。此前，该担保被官方封禁用户名、频道及相关群组。期间，领航担保一度恢复运营，并对部分用户进行了押金退还。然而，恢复后不久，其账号再次遭到官方封禁。在此之后，领航担保彻底，形成“跑路”局面。 除常见的担保专群押金外，领航担保还涉及博彩电子充值等金额业务，进一步扩大了受影响用户的范围。 据相关人士透露，领航担保在失联前，曾向部分关系密切的公群老板退还了押金，显示出一定的选择性退押行为。此外，其名下所使用的多个用户名已被转售。尽管买家同为劳务担保圈内人士，并有意将这些用户名继续用于担保业务，但有分析认为，这些账号很可能已被平台标记，未来极有可能面临再次封禁的风险。 ✈️ 担保服务商收录及信息修改 ✈️ 全网担保列表 ✈️ 担保常见骗术 ✈️ 全网供需查询 🔥 娱乐圈千万押金 🔥 腾博会电子 👉 投稿联系 👉 返回置顶
👍6❤5🎉3🔥2☃1👏1
Showing the 7 most recent of 7 posts we hold for @DBFWLB. 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 — 1,373,375 of 1,548,671entries 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 1 registered channel — 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.
@DBFWLB named 1 handle 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 17 August 2026 — this entry's latest reading, not the date you are reading this.
“<担保圈>全网担保状态查询” (@DBFWLB), 8,121 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/DBFWLB.
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.