Channel
@jbdbsm
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
99subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001517180794 |
|---|---|
| Type | Channel |
| Username | @jbdbsm |
| Description | 核心大群:@JBDB （金貝担保 首字母） 公群频道:@JBGQ （金貝公群 首字母） 供需频道:@JBGXPD (金貝供需频道 首字母) 客服频道:@JBKFPD (金貝客服频道 首字母) 公司介绍:@jbjtdb (金貝集团担保 首字母) 担保说明:@JBDBSM 记账机器人:@jbdbjqr_bot (免费使用) |
| Created | 5 April 2023 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/jbdbsm |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 11:03 | 99 | no change |
| 7 Aug 2026, 10:21 | 99 | first reading |
8 posts held, back to 5 April 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 8 posts for this entry, the most recent from 29 February 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 9 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.
11 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 36.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4 | 36.4% | |
| 🤮 | 3 | 27.3% | |
| ❤ | 2 | 18.2% | |
| 🌭 | 2 | 18.2% |
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 3 of the 8 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 11reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 5 April 2023 to 29 February 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🪧战略合作官方公告 金贝集团注资500万美金助力起点交易 @QiDian 。 原金贝集团担保业务合并至起点交易，并将在柬埔寨展开大规模官方宣传。 金贝担保官方公示 @JBDB @JBGQ @JBJTDB 😀起点交易 & 😋 金贝集团 强强联合 大额资金无忧 1️⃣ 起点交易已在金贝总部(西港金贝2期10楼)设立实体公司 2️⃣ 已全面支持线下集团部门办理上下押。 3️⃣ 原班运营团队，无限推广预算，携手金贝集团再造流量巅峰。 金贝集团•柬埔寨集赌场、酒店、休闲、旅游业为一体的大型集团企业，隶属太子集团 金贝集团官网 https://www.jinbei-group.com/
注意金貝担保官方唯一上押账户： TRC地址： TBeGksiAkYdymEVgL8AZLbA3krktkGy24M 点击地址自动复制，（TBeGks开头 kGy24M结尾） 上押只收美金和usdt,不收rmb,使用其他账户和地址的都是骗子。
《规则须知》 规则是双方根据自身的条件制定的条例，专群双方一定把交易规则发在群内。规则用来限制双方避免纠纷，专群的规则由双方制定，或者双方认可为准。公群的规则必须遵守置顶规则，规则在置顶以后禁止修改，如果发错请重新发，修改以后的规则不作数，其次禁止文字游戏，如果出现纠纷完全按照担保方的审核为准。 公群001-金贝担保-张三供已退押【暂停担保】 公群001-【押金已退】金贝担保- 李四供【保留群】供押500U 这个意思是供方已经没有押金，需方也还没有确定，没有需方不属于担保， 押金已退 不属于担保内，没确认需方禁止交易。如果需方确定了，请找担保方修改群名，群名没有修改以前禁止交易，如果交易所有产生的纠纷担保方可以不处理，或者根据人品仲裁供方或需方。 《赔付参照》 专群赔付也就是交易的时候供方出了问题，要求担保方用押金补偿需方，公群赔付按顺序来，常规操作一个需方回款以后下一个需方进款，交易总额度不要超过押金，否则很容易造…
👍3🤮3🌭2❤1
《规则须知》 规则是双方根据自身的条件制定的条例，专群双方一定把交易规则发在群内。规则用来限制双方避免纠纷，专群的规则由双方制定，或者双方认可为准。公群的规则必须遵守置顶规则，规则在置顶以后禁止修改，如果发错请重新发，修改以后的规则不作数，其次禁止文字游戏，如果出现纠纷完全按照担保方的审核为准。 公群001-金贝担保-张三供已退押【暂停担保】 公群001-【押金已退】金贝担保- 李四供【保留群】供押500U 这个意思是供方已经没有押金，需方也还没有确定，没有需方不属于担保， 押金已退 不属于担保内，没确认需方禁止交易。如果需方确定了，请找担保方修改群名，群名没有修改以前禁止交易，如果交易所有产生的纠纷担保方可以不处理，或者根据人品仲裁供方或需方。 《赔付参照》 专群赔付也就是交易的时候供方出了问题，要求担保方用押金补偿需方，公群赔付按顺序来，常规操作一个需方回款以后下一个需方进款，交易总额度不要超过押金，否则很容易造…
❤1
【金貝担保】业务流程 《拉群》流程 在双方谈好业务确定后，再让担保客服方拉群，需要说明需方负责人与供方负责人，或者发送对接方的用户名，等客服设置完成供需双方后上押截图确认完成即可交易。 金貝一组 @jbdb02 @jbdb03 业务办理、上下押 金貝二组 @jbdb04 @jbdb05 业务办理、上下押 用户名不是个人简介一定分清楚 《上押》流程 确认好你们的规则，业务范围。上押必须认准担保方拉的群，担保方发出的钱包地址，打币成功请及时发图并通知担保方查收，以回复对话或者@担保方查收为准。上押以后才会改群名。禁止私自打押金， 打币第一时间通知担保号。为避免后续办理退押出现纠纷,由上押人员确认供方负责人及供方，需方也要第一时间确认好，需方负责人及需方人员 。退押必须由负责人确认。双方规则确认好 如需修改请及时确认好，为避免纠纷请严格按照规则入款，后续如若有纠纷将以制定规则进行仲裁，一定要供需双方负责人确认…
👍1
Channel photo updated
Channel name was changed to «金貝担保说明»
Channel created
Showing the 8 most recent of 8 posts we hold for @jbdbsm. 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 — 941,222 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“金貝担保说明” (@jbdbsm), 99 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/jbdbsm.
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.