Telegram RegisterThe public register of Telegram

Channel

博创担保—需求频道

@BCDBXQ

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

360subscribers

-2 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-1001429321200
TypeChannel
Username@BCDBXQ
CreatedBetween 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/BCDBXQ

Growth

3603623617 Aug 2026, 04:04 — 362 subscribers7 Aug 2026, 04:17 — 362 subscribers8 Aug 2026, 00:26 — 360 subscribers7 Aug 2026, 04:048 Aug 2026, 00:26
3 measurements taken within a single day, net -2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 360–362 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 00:26360-2
7 Aug 2026, 04:17362no change
7 Aug 2026, 04:04362first reading

Engagement

20 posts held, back to 18 May 2023the 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 11 July 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

11 Jul 2023, 13:30 UTC≈4,420 viewsread 7 August 2026

需求编号: CH123 需求: 中国承兑 资金性质:一道BC代收付 结算时间:可聊 通道时间:可聊 费率、汇率:可聊 日量:可聊 押金支持:是 联系人员:@CNHD_BCDB / @CSHD_BCDB 支持担保:博创担保

11 Jul 2023, 13:30 UTC≈2,180 viewsread 7 August 2026

需求编号: DG104 需求: 马来西亚承兑 资金性质:一道二类 结算时间:可聊 通道时间:可聊 费率、汇率:可聊 日量:可聊 押金支持:是 联系人员:@DGHD_BCDB / @CSHD_BCDB 支持担保:博创担保

11 Jul 2023, 13:30 UTC≈2,510 viewsread 7 August 2026

需求编号: DG163 需求: 印度承兑 资金性质:一道二类 结算时间:可聊 通道时间:可聊 费率、汇率:可聊 日量:可聊 押金支持:是 联系人员:@DGHD_BCDB / @CSHD_BCDB 支持担保:博创担保

11 Jul 2023, 13:30 UTC≈3,200 viewsread 7 August 2026

需求编号: DG102 需求: 新加坡承兑 资金性质:二道BC 结算时间:可聊 通道时间:可聊 费率、汇率:可聊 日量:可聊 押金支持:是 联系人员:@DGHD_BCDB / @CSHD_BCDB 支持担保:博创担保

11 Jul 2023, 13:30 UTC≈4,130 viewsread 7 August 2026

需求编号: CH231 需求: 中国承兑 资金性质:二道二类 结算时间:可聊 通道时间:可聊 费率、汇率:可聊 日量:可聊 押金支持:是 联系人员:@CNHD_BCDB / @CSHD_BCDB 支持担保:博创担保

11 Jul 2023, 13:30 UTC≈1,960 viewsread 7 August 2026

需求编号: DG101 需求: 泰国承兑 资金性质:三类 结算时间:可聊 通道时间:可聊 费率、汇率:可聊 日量:可聊 押金支持:是 联系人员:@DGHD_BCDB / @CSHD_BCDB 支持担保:博创担保

7 Jul 2023, 06:50 UTC≈1,850 viewsread 7 August 2026

需求编号: DG161 需求: 印度刷单通道 资金性质:一道 结算时间:可聊 通道时间:北京12:00-19:00 费率、汇率:可聊 日量:可聊 押金支持:是 联系人员:@DGHD_BCDB / @CSHD_BCDB 支持担保:博创担保

5 Jun 2023, 10:01 UTC≈3,160 viewsread 7 August 2026

需求编号:BCDB1719 需求:海外 日本二类资金通道 盘口类型:综合 结算时间:可聊 通道时间:可聊 点位:可聊 日量:可聊 押金金额:有 备注:(不用牌照) 联系人员:@DGTD_BCDB 支持担保 :博创担保

2 Jun 2023, 10:01 UTC≈1,870 viewsread 7 August 2026

需求编号:BCDB1718 需求:海外 印度一二类资金通道 盘口类型:综合 结算时间:可聊 通道时间:可聊 点位:可聊 日量:可聊 押金金额:有 联系人员:@DGTD_BCDB 支持担保 :博创担保

1 Jun 2023, 10:01 UTC≈1,570 viewsread 7 August 2026

需求编号:BCDB1717 需求:国内 卡接回U、大/小额通道 盘口类型:综合 结算时间:可聊 通道时间:可聊 点位:可聊 日量:可聊 押金金额:有 备注:不包/包)司,24H 联系人员:@CNTD_BCDB 支持担保 :博创担保

31 May 2023, 10:01 UTC≈1,350 viewsread 7 August 2026

需求编号:BCDB1716 需求:国内 小额卡卡 2.8以下 盘口类型:综合 结算时间:可聊 通道时间:可聊 点位:可聊 日量:可聊 押金金额:有 备注:包风包司 联系人员:@CNTD_BCDB 支持担保 :博创担保

30 May 2023, 10:01 UTC≈2,210 viewsread 7 August 2026

需求编号:BCDB1715 需求:国内 大额卡卡 2.5%以下 盘口类型:综合 结算时间:可聊 通道时间:可聊 点位:可聊 日量:可聊 押金金额:有 备注:包风包司 联系人员:@CNTD_BCDB 支持担保 :博创担保

Showing the 12 most recent of 20 posts we hold for @BCDBXQ. 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.

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“博创担保—需求频道” (@BCDBXQ), 360 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/BCDBXQ.

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.