产 品:马来西亚二道BC 汇率:实时报价 保时:永久 结算周期:D0,亦可双方协议 打款模式:银行卡,可接私户出款 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:5,000MYR起 下发回u限额:双方协议 交易时间:12:00-20:00 下发时间:12:00-20:00 回U时间:12:00-20:00 到帐时间:1小时内 客服时间:12:00-20:00 商户承接类型:二道BC 商户最低开户日量:不限制

Channel
博创担保—供应频道
@BCDBGY
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
425subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001303891721 |
|---|---|
| Type | Channel |
| Username | @BCDBGY |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/BCDBGY |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 08:51 | 425 | no change |
| 7 Aug 2026, 05:32 | 425 | first reading |
Engagement
20 posts held, back to 2 June 2023 — 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 21 September 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
产 品:越南二道BC 汇率:实时报价 保时:48hr 结算周期:D0,亦可双方协议 打款模式:银行卡,私户出款 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:10万-3亿 VND 下发回u限额:双方协议 交易时间:12:00-20:00 下发时间:12:00-20:00 回U时间:12:00-20:00 到帐时间:1小时内 客服时间:12:00-20:00 商户承接类型:二道BC 商户最低开户日量:不限制
产 品:印尼BC 汇率:实时报价 保时:永久 结算周期:D0,亦可双方协议 打款模式:银行卡,可接私户出款 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:500,000印尼盾起 下发回u限额:双方协议 交易时间:12:00-20:00 下发时间:12:00-20:00 回U时间:12:00-20:00 到帐时间:1小时内 客服时间:12:00-20:00 商户承接类型:二道BC 商户最低开户日量:不限制
产 品:新加坡二道BC 汇率:实时报价 保时:永久 结算周期:D0,亦可双方协议 打款模式:银行卡,可接私户出款 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:1,500 SGD起 下发回u限额:双方协议 交易时间:12:00-20:00 下发时间:12:00-20:00 回U时间:12:00-20:00 到帐时间:1小时内 客服时间:12:00-20:00 商户承接类型:二道BC 商户最低开户日量:不限制
产 品:日本二道BC 汇率:实时报价 保时:永久 结算周期:D0,亦可双方协议 打款模式:银行卡,可接私户出款 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:50,000 JPY起 下发回u限额:双方协议 交易时间:12:00-20:00 下发时间:12:00-20:00 回U时间:12:00-20:00 到帐时间:1小时内 客服时间:12:00-20:00 商户承接类型:二道BC 商户最低开户日量:不限制
产 品:菲律宾二道BC 汇率:实时报价 保时:Gcash-保1hr,银行卡保48hr 司法:Gcash-打款方造成司法冻结需赔付单笔入款金额,银行卡-打款方造成司法冻结需赔付账户余额及一切行政费用 结算周期:D0,亦可双方协议 打款模式:银行卡,Gcash,paymaya 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:100,000 peso起叫卡(可拆笔) 下发回u限额:双方协议 交易时间:24小时 下发时间:24小时 回U时间:24小时 到帐时间:1小时内 客服时间:24小时 商户承接类型:二道BC 商户最低开户日量:10W
产 品:印度二道BC 汇率:实时报价 保时:永久 结算周期:D0,亦可双方协议 打款模式:银行卡,可接公户、私户出款 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:20w起 下发回u限额:双方协议 交易时间:11:30 AM – 18:00 PM(印度时间) 下发时间:11:30 AM – 18:00 PM(印度时间) 回U时间:11:30 AM – 18:00 PM(印度时间) 到帐时间:1小时内 客服时间:11:30 AM – 18:00 PM(印度时间) 商户承接类型:二道BC 商户最低开户日量:不限制
产 品:公检法一道进算 汇率:实时报价 保时:进算 司法:经查证如有非公检法之款项则当日不予回款 结算周期:D0,到账后回款 打款模式:银行卡,私户出款 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:10,000-300,000 RMB 下发回u限额:双方协议 交易时间:10:00-19:00 下发时间:10:00-19:00 回U时间:10:00-19:00 到帐时间:1小时内 客服时间:10:00-19:00 商户承接类型:公检法 商户最低开户日量:不限制
产 品:中国一道常规 汇率:实时报价 保时:进算 结算周期:D0,亦可双方协议 打款模式:银行卡,私户出款,如需其他支付方式需预先通知 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:5,000-200,000RMB 下发回u限额:双方协议 交易时间:7:00-1:00 下发时间:7:00-1:00 回U时间:7:00-1:00 到帐时间:1小时内 客服时间:7:00-1:00 商户承接类型:刷单、色料 商户最低开户日量:不限制
产 品:中国二道资金盘 汇率:欧易上浮0.4 保时:7天 结算周期:D0,亦可双方协议,回单需保留三天查帐时间,如无到帐需与我方确认是否补入或是换卡补入 打款模式:银行卡,可接公户/私户出款 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:10,000-50,000 RMB 下发回u限额:双方协议 交易时间:24小时 下发时间:24小时 回U时间:24小时 到帐时间:1小时内 客服时间:24小时 商户承接类型:二道资金盘 商户最低开户日量:不限制
产 品:中国二道常规 汇率:欧易上浮0.8 保时:进算 结算周期:D0,亦可双方协议 打款模式:银行卡,私户出款 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:3,000-8,000RMB 下发回u限额:双方协议 交易时间:09:00-04:30 下发时间:09:00-04:30 回U时间:09:00-04:30 到帐时间:1小时内 客服时间:09:00-04:30 商户承接类型:二道混料、大区、精聊 商户最低开户日量:不限制
产 品:中国二道精聊 汇率:欧易上浮+0.75(参见oke第三条) 保时:进算 结算周期:D0,亦可双方协议 打款模式:银行卡,私户出款 下发模式:回U 回U汇率依据:欧易C2C买价 打款单笔限额:1,000-9,999 RMB 下发回u限额:双方协议 交易时间:24hr 下发时间:24hr 回U时间:24hr 到帐时间:1小时内 客服时间:24hr 商户承接类型:二道精聊、色料 商户最低开户日量:不限制
Showing the 12 most recent of 20 posts we hold for @BCDBGY. 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
Citation-graph rank — 925,397 of 1,169,250entries 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.
Mentions
Named by 2 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.
Handles this channel named that no longer answer
- Dead references
- 5
- 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
- 5
- vacant every time we have ever looked
@BCDBGY named 5 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 2 posts, 8 August 2026 – 8 August 2026
named in 2 posts, 8 August 2026 – 8 August 2026
named in 2 posts, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“博创担保—供应频道” (@BCDBGY), 425 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/BCDBGY.
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.