Channel
@db_dsj
On this record: Growth · Engagement · Posts · Citations · Cite this entry
2,080subscribers
-74 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002358085361 |
|---|---|
| Type | Channel |
| Username | @db_dsj |
| 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/db_dsj |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 23:34 | 2,080 | -40 |
| 10 Aug 2026, 19:14 | 2,120 | -34 |
| 7 Aug 2026, 10:16 | 2,154 | no change |
| 7 Aug 2026, 10:03 | 2,154 | first reading |
11 posts held, back to 21 July 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 2 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 7 August 2026 |
|---|---|
| Posts held | 11 (21 July 2026 – 7 August 2026) |
| Views total | 17,461 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:54 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.
8月7日最新新闻 #网友爆料 云顶pc股东叶门负责人手机被偷走 据网友爆料就在刚刚，叶门负责人叶明轩手机被小姐偷走，要求打50万u返还所有NFT，不然就解散此账号 @yd28 所有群组，据合伙人刚子透露损失高达91万u，其中有49u是云顶pc28偷走，实际总损失是120万u，手机里的u跟NFT全部被转走，包括新币N小组222 天天PG也暂停运营。 明天凌晨1点应该会恢复，已经达成和解。 PS：最近市场动荡，这种事情明显多起来了，大家要注意看管好自己的财物 关注频道➡️ @db_dsj 投稿爆料➡️ @yuzhongyou
8月5日最新新闻 #网友爆料 白金担保不作为 打纠纷需交纠纷费 据网友投稿：白金担保 我在他们公群里面上分被骗！ 事情经过：我在他们公群内上分，然后没人回应我，后面有个自称群内财务的人 私聊我 我去他们公群里面核对了一下 确实是同一个用户名 我转账之后 对方直接拉黑，公群方不认 目前是担保 @jinzheng 偏袒公群方，非要我交30u纠纷费，估计纠纷费交了一样判我输 大家避雷这个担保。 PS：各位看官怎么看，欢迎评论区留言讨论。 关注频道➡️ @db_dsj 投稿爆料➡️ @yuzhongyou
8月3日最新新闻 #网友爆料 天空娱乐假出款引流！ 据网友爆料天空娱乐以出款1300万u线下实体大户出名。 爆奖15000倍与到处送特邀让大家熟知 天空娱乐 请看图，图中出款记录相当于转了一圈钱又回来了，以假出款用户名义来引流。 PS：请大家选择出名有背书的综合盘进行娱乐。 关注频道➡️ @db_dsj 投稿爆料➡️ @yuzhongyou
8月1日最新新闻 #网友爆料 淘宝娱乐通缉黑客50万u！ 就在今日富贵官方频道中 富贵旗下淘宝娱乐发布声明，出资50万美元购买黑客信息，起因是此黑客恶意盗取巨富娱乐9万u！ PS：最近黑客有点猖狂，入侵事件明显增多 关注频道➡️ @db_dsj 投稿爆料➡️ @yuzhongyou
7月31日最新新闻 #网友爆料 巨富娱乐被入侵！ 就在刚刚富贵娱乐旗下 巨富娱乐被黑客入侵，同时会员数据也被黑客全部窃取，并公开出售！ 本次巨富娱乐损失14万u，被拦截回5万u，总损失9万u 据网友爆料本次黑客是上次攻击okpay的黑客方阳 PS：不知道下一个被入侵的是哪个大佬的产业 关注频道➡️ @db_dsj 投稿爆料➡️ @yuzhongyou
7月28日最新新闻 #网友爆料 #担保环境 顶尖担保一周未上线 失联！ 据网友爆料即柬埔寨担保与索隆担保跑路后，顶尖担保全部工作人员已多天未上线，直至今天还未上线回应。 PS：近日跑路与失联担保较多，各位老板审时度势，谨慎选择担保，建议选择有信任背书的担保。 关注频道➡️ @db_dsj 投稿爆料➡️ @yuzhongyou
7月25日最新新闻 #网友爆料 星星漏洞已经修复 官方开始追查扣回 7月23日的星星漏洞已经被官方全部处理。 因此漏洞产出的低价星星礼物与会员已经全部被消除并退回，目前没有出现封禁账号的情况。 PS：谨慎利用漏洞赚钱，被追回得不偿失。 关注频道➡️ @db_dsj 投稿爆料➡️ @yuzhongyou
2026年7月25日最新新闻 #担保环境 柬埔寨担保地址被清空，疑似跑路！ 就在24日23:40，柬埔寨担保官方地址被清空，转出5万余u，目前柬埔寨官方未发布任何公告与解释。 PS：近日跑路与失联担保较多，各位老板谨慎上押，建议选择有信任背书的担保 关注频道➡️ @db_dsj 投稿爆料➡️ @yuzhongyou
7月24日最新新闻 #担保环境 突发状况！就在刚刚索隆担保跑路！ 据网友爆料就在刚刚 15:16分，索隆负责人在自己大群发布了因各种原因，索隆已无法维持运营，正式跑路，终止所有业务运营。 此次索隆跑路公群为100个左右，押金大约7万u左右。 PS：这已经是今年第十个跑路的担保，请大家擦亮眼睛选择背书强有保障的担保。 关注频道➡️ @db_dsj 投稿爆料➡️ @yuzhongyou
7月23日最新新闻 #网友爆料 刚刚 Telegram官方出现其支付漏洞！ 据网友爆料，就在刚刚部分日本地区飞机号购买会员，充值Stars（星星）出现异常价格，最低只需0.25USDT！ 消息一经流出，大量用户抓住漏洞疯狂操作，两小时内已经流出千万星星！ 但是，利用这次漏洞获得的星星变现才是最麻烦的，因为就算打赏或者购买礼物也需要14天，这完全可以被官方修复！ PS：官方漏洞获利以往买卖双方都会销号，各位最近谨慎购买低价礼物和会员 关注频道➡️ @db_dsj 投稿爆料➡️ @yuzhongyou
7月21日最新新闻 #网友爆料 #担保环境 旺旺担保凌晨发布声明，确认跑路！ 在今日的凌晨1：23分旺旺担保在自己供需频道发布声明，自称因平台运营不善，长期经营未能达到预期，经过团队慎重评估与讨论决定停止运营。 还自称，自己家乡位于重庆彭水，想将跑路的押金捐赠与家乡做公益。 此担保从运营开始公群便是担保倒数水平，此次跑路公群数量为15个，押金大约7000u左右。 小编在此提醒大家，这已经是今年跑路的第九个担保，请大家擦亮眼睛选择有背书有实力的担保进行交易。 PS：拿别人的钱给自己家乡做公益？ 关注频道➡️ @db_dsj 投稿爆料➡️ @yuzhongyou
Showing the 11 most recent of 11 posts we hold for @db_dsj. 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,728 of 1,336,469entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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.
“担保新闻圈｜全担保行业新闻” (@db_dsj), 2,080 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/db_dsj.
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.