卡尔担保需求信息 pinned a photo

Channel
卡尔担保需求信息
@DBX0INFO
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
33subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001308063994 |
|---|---|
| Type | Channel |
| Username | @DBX0INFO |
| Description | 担保对接记录 @DBIYJL 担保供应信息 @DBGYINF0 担保需求信息 @DBX0INFO 业务联系人 @CARZ789 |
| Created | Between 1 March 2018 and 18 October 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/DBX0INFO |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 01:01 | 33 | no change |
| 6 Aug 2026, 20:43 | 33 | first reading |
Engagement
20 posts held, back to 18 October 2020 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 18 February 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 11 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.
Recent posts
OK娱乐活动 今日注册的用户 注册前1000名随机赠送38-3888彩金 注册网址: http://www.1230879.com OK娱乐上分U地址余额价值600多万RMB的U,不用担心上分不下款的问题 现在还有活动首冲1000送500!首冲1万送1万!每个IP限领一次!(名额100位) 联系客服 @OKYL1
需求序号0006 四方收小额通道 费率:11 PS:成功率高量大可谈点位 担保费:0.1 总支出:11.1 通道类型:微信H5 微信话费 支付宝话费 原生支付宝 可用时间:24H 日量:1000W+ 成功率:40%以上 押金要求:5-10万起放担保方 商户类型:HB. ZB. QP. BC(已接入所有已知包网)分开的通道 备注可以跑的产品 金额:30,50,100,200,300(最少支持其中三个金额) @CARZ789
卖币回RMB 打卡 3% 卖币ATM无卡存仅限工行 4% @CARZ789
需求序号0002 四方收小额通道 费率:13 担保费:0.1 总支出:13.1 通道类型:微信H5 可用时间:24H 日量:1000W+ 成功率:40%以上 押金要求:10万起放担保方 商户类型:BC(已接入所有已知包网) 金额:10,20,30,50,100,200,300,400,500(最少支持其中三个金额) @CARZ789
需求序号0005 招商类型:支付宝群红包码商 模式:支付宝 后台手动回调 利润结算:实时系统结算 入款额度:单笔支付宝红包1000~10000元 回款模式:归集回款 支付佣金:1.5+0.1=1.6 0.1是担保利润,由供付 工作时间:早上10点到晚上22点(最好能24小时) 押金要求:3万RMB起放担保方 要求:产码量要快,成功率要高,下发速度要快,量管够 备注:长期招募码商跑分总代理 @CARZ789
置顶广告招商 30万RMB/月 15万半个月 @CARZ789
需求序号0004 1. 招商类型:招支付宝码商 模式:支付宝 后台手动回调 费率构成:码商1.6.担保费0.1.提现费0.1,也就是总支出1.7到码商,0.1担保费由供付,码商纯利润是1.7% 利润结算:日结 入款额度:单笔3000~50000 回款模式:归集回款 押金要求:5万RMB起放担保方 要求:产码量要快,成功率要高,下发速度要快,量管够 2. 招商类型:卡商(网银+手银) 模式:出款给会员 资金类型:BC 利润结算: 系统自动结算 出款额度: 100~50000 费率:0.4+0.1=0.5%+单笔1元 押金要求:5万RMB起 USDT付款 3. 招商类型:卡商(网银+手银) 模式:支付宝转银行卡 资金类型:BC 利润结算: 日结 出款额度: 300~50000 费率:1.3+担保0.1=1.4 押金要求:3万RMB起 USDT付款 担保业务联系人 @CARZ789
供应序号0148 产品:移动话单(黄播)效果等同于原生h5 微信 30/50/100/200 只接hb视频类,不接雷,不接BC 接入要求:日量5w,需验盘 费率:18% 24小时跑量,成功率95+%,(独家技术) 对私下发基本24小时太晚或太早有时没人处理,usdt有两个点手续费 投诉:我方处理 押金模式:1-50w 不对接四方,不对接四方,不对接四方 不是普通快充话费,小白勿扰! 担保业务联系人 @CARZ789
担保对接交流 @CARL7895 担保对接记录 @DBIYJL 担保供应信息 @DBGYINF0 担保需求信息 @DBX0INFO 卡尔担保负责人 @CARZ789
需求序号0004 1. 招商类型:招支付宝码商 模式:支付宝 后台手动回调 费率构成:码商1.4.担保费0.1.提现费0.1,也就是总支出1.6到码商,0.1担保费由供付,码商纯利润是1.5% 利润结算:日结 入款额度:单笔500~10000 回款模式:归集回款 押金要求:3万RMB起放担保方 要求:产码量要快,成功率要高,下发速度要快,量管够 2. 招商类型:卡商(网银+手银) 模式:出款给会员 资金类型:BC 利润结算: 系统自动结算 出款额度: 100~50000 费率:0.4+0.1=0.5%+单笔1元 押金要求:5万RMB起 USDT付款 担保业务联系人 @CARZ789
需求序号0045 棋牌游戏寻一手卡商代收团队 卡转卡模式:直流银行卡代收 费率: 0.5+0.1=0.6不需包司法 0.7+0.1=0.8需包司法 银行卡:农业,建设,中国,邮政,中信 代收限额100-50000 单日跑量100W起 押金要求:5w rmb起 担保业务联系人 @CARZ789
Showing the 12 most recent of 20 posts we hold for @DBX0INFO. 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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@DBX0INFO named 2 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 11 August 2026 – 11 August 2026
named in 1 post, 11 August 2026 – 11 August 2026
Cite this entry
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“卡尔担保需求信息” (@DBX0INFO), 33 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/DBX0INFO.
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.