Achievement Unlocked: x13! ⚡️ @bgbcncall made a x13+ call on Delivery Guy. $93K ➡️ $1.2M 👁 View Call 📊 View Stats 🪶 Super Ishikaw... - TRENDING #1
💯15🎉14🔥13❤12👍11

Channel
@bgbcncall
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
34,569subscribers
-3,385 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002297451987 |
|---|---|
| Type | Channel |
| Username | @bgbcncall |
| Description | CEO-FOUNDER👩💼: @Xiufinen MKT: @Yue_NicotineGG | @Ruolan_io BGB CN|多链KOL营销网络 连接中国及亚洲加密市场的活跃交易者与高参与度社区助力优质项目扩大影响力与曝光 Main: @bgbcncall Group: @bgbcnchat 𝕏 https://x.com/sinamengyao 𝕏 https://x.com/yue_nicotinegg WB: https://weibo.com/u/7963123431 |
| 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 | 4 October 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/bgbcncall |
Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 18:15 | 34,569 | -889 |
| 26 Sept 2026, 18:37 | 35,458 | -871 |
| 19 Sept 2026, 12:57 | 36,329 | -99 |
| 17 Sept 2026, 00:38 | 36,428 | -249 |
| 15 Sept 2026, 01:41 | 36,677 | -242 |
| 13 Sept 2026, 13:38 | 36,919 | -446 |
| 11 Sept 2026, 21:16 | 37,365 | -529 |
| 9 Sept 2026, 09:18 | 37,894 | +7,951 |
| 6 Sept 2026, 00:19 | 29,943 | +1,195 |
| 3 Sept 2026, 18:17 | 28,748 | +1,932 |
| 2 Sept 2026, 07:56 | 26,816 | -661 |
| 1 Sept 2026, 08:26 | 27,477 | -2,014 |
| 31 Aug 2026, 10:58 | 29,491 | -4,343 |
| 30 Aug 2026, 07:57 | 33,834 | -1,670 |
| 29 Aug 2026, 10:45 | 35,504 | -260 |
| 28 Aug 2026, 09:28 | 35,764 | -113 |
| 27 Aug 2026, 07:54 | 35,877 | -107 |
| 26 Aug 2026, 04:57 | 35,984 | +1,726 |
| 25 Aug 2026, 01:33 | 34,258 | -207 |
| 23 Aug 2026, 15:36 | 34,465 | first reading |
465 posts held, back to 3 August 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 108 pages of 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. It is computed over the 66 of 273 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 October 2026 |
|---|---|
| Posts held | 465 (3 August 2026 – 8 October 2026) |
| Views total | 1,050,650 |
| Reactions total | 2,554 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Oct 2026, 19:41 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.
Lifetime counters from Telegram’s own channel header, read 8 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 14 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
8,854 reactions across 116 posts, in 9 distinct kinds. The most used accounts for 24.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2,130 | 24.1% | |
| ❤ | 2,104 | 23.8% | |
| 💯 | 2,058 | 23.2% | |
| 🔥 | 2,029 | 22.9% | |
| 🎉 | 524 | 5.92% | |
| 🆒 | 4 | 0.045% | |
| 🐳 | 3 | 0.034% | |
| 👾 | 1 | 0.011% | |
| 🦄 | 1 | 0.011% |
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 116 of the 465 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 8,854 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 465 most recent posts we hold, published 3 August 2026 to 8 October 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Achievement Unlocked: x13! ⚡️ @bgbcncall made a x13+ call on Delivery Guy. $93K ➡️ $1.2M 👁 View Call 📊 View Stats 🪶 Super Ishikaw... - TRENDING #1
💯15🎉14🔥13❤12👍11
Achievement Unlocked: Consistency is key! 🔑 @bgbcncall has made 5 x2+calls in the past 7 days. 👁 View Call 1 👁 View Call 2 👁 View Call 3 👁 View Call 4 👁 View Call 5 📊 View Stats 🟣 TWEETCRAFT - TRENDING #1
❤19👍16🔥13🎉12💯5
10X $DGUY 0xe34356DCD3d7bb991248F322E4ec31B5d60Bc54e
🎉17👍15❤13🔥12💯10👾1🆒1
Achievement Unlocked: Printer! 💲 @bgbcncall made a x10+ call on Delivery Guy. $93K ➡️ $969K 👁 View Call 📊 View Stats 💙 AF - TRENDING #2
❤19🎉16🔥13💯12👍9🐳1🆒1
2X $YEHI 命中 ⭑ 2X 😀 👀 @Yue_NicotineGG 🎯 $95.25K → $190.88K 0xba4c9375c899acb9b99b4a032a7756dd24ec6666
🔥28❤18🎉18👍17💯15🐳1🆒1
Achievement Unlocked: Back In Town 🤠 @bgbcncall made a x2+ call for Ye Hi on BSC after a time away from the chain. $85K ➡️ $177K 👁 View Call 📊 View Stats 😎 NEW: SpyDefi LIVE - FREE real-time feed of call alerts
🎉16👍15💯14❤12🔥9
天哪,我刚在 Discord 上看到有人把 20 美元变成了 6.5 万美元。 如果你还没领过,记得去拿 MetaWin 每天向新存款用户提供的 2,500 美元免费赠金。 使用代码“X100”,他们还会提供最高 1,000 美元的存款匹配奖励。 这两个优惠活动不会持续太久,趁现在还有机会赶紧行动吧。 在 metawin.com 进行首次存款即可获得资格。 $METAWIN #METAWIN
🎉29❤21🔥18👍17💯16
Ye Hi $YEHI 🪙⛓ Ye Hi 是 BSC 链上的一个实验性社区代币,仅源于项目官方账号发布的一条简短推文,且没有公开的团队;其定位是一次构建社区驱动型项目的尝试。 0xBa4C9375C899Acb9B99b4A032A7756dD24EC6666
🎉28💯26❤21🔥19👍13
Achievement Unlocked: x6! ⚡️ @bgbcncall made a x6+ call on Delivery Guy. $93K ➡️ $637K 👁 View Call 📊 View Stats 😎 NEW: SpyDefi LIVE - FREE real-time feed of call alerts
💯18🔥17👍14🎉11❤10
3X $FULLMARGIN FmybF8WBgdCuk1ZYrLQsNdFkauiU23Z8wD8QXoXupump
🎉8👍7❤6🔥6💯3
Achievement Unlocked: x2! ✌️ @bgbcncall made a x2+ call on FullMargin. $175K ➡️ $358K 👁 View Call 📊 View Stats 😎 NEW: SpyDefi LIVE - FREE real-time feed of call alerts
🎉11💯8🔥6👍3❤2🐳1
$FULLMARGIN $FULLMARGIN 正在快速升温,Solana生态热度持续聚集,社区关注度不断提升,交易活跃度也越来越强。故事才刚刚开始,后续值得持续关注。 🚀🔥 $FullMargin 市场动能正在增强,越来越多目光开始聚集,社区正在快速成长。早期阶段值得关注,接下来或许会更加精彩。 👀📈 $FullMargin 热度持续上升,社区不断扩大,市场关注度快速增长。现在只是开始,保持关注。 🌱🚀 🟩: https://dexscreener.com/solana/8LXqhybMxAKUtJTrQ8LCda6Z397NdrrTtYdNLoeakark
🔥10❤8🎉6👍6💯1
Showing the 12 most recent of 465 posts we hold for @bgbcncall. 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.
@bgbcncall edited 5 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
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.
@bgbcncall named 1 handle 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“🏹 BGBCN 🏹 #sᴏʟ | #ᴇᴛʜ | #ʙᴀsᴇ | #ʙsᴄ” (@bgbcncall), 34,569 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/bgbcncall.
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.