Posted without readable text
👍19

Channel
@bcgamewin
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · View velocity · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Domains linked from posts · Cite this entry
741,337subscribers
-18,496 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 316,228–1,000,000.
| Telegram ID | -1001166926064 |
|---|---|
| Type | Channel |
| Username | @bcgamewin |
| Description | Official notification channel for BC.Game - Get the latest updates on events, promos and more. We value your time and due to this we never spam our notifications channel with irrelevant content - Only important events you need to know |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/bcgamewin |
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 3 other registered channels. This entry also sits inside a group of 4 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @official_bc_token/241215 Aug 2026, 21:44 UTC | @bcgamewin/4224 · this entry15 Aug 2026, 22:40 UTC | 1.00 | 56 minutes |
| @official_bc_token/257021 Oct 2026, 20:30 UTC | @bcgamewin/4389 · this entry21 Oct 2026, 20:31 UTC | 1.00 | 2 minutes |
| @official_bc_token/257122 Oct 2026, 00:00 UTC | @bcgamewin/4390 · this entry22 Oct 2026, 00:03 UTC | 1.00 | 4 minutes |
| @bcgamewin/4196 · this entry2 Aug 2026, 09:19 UTC | @bcgamesports/977630 Aug 2026, 08:10 UTC | 1.00 | 28 days |
| @bcgamesports/987722 Sept 2026, 15:00 UTC | @bcgamewin/4298 · this entry22 Sept 2026, 15:11 UTC | 1.00 | 11 minutes |
| @bcgamesports/99192 Oct 2026, 15:01 UTC | @bcgamewin/4325 · this entry6 Oct 2026, 15:07 UTC | 1.00 | 4 days |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @official_bc_token | 121 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (65–56) |
| @bcgamesports | 36 (8/8 hand-verifiable sample passed) | 0.97 | 68 minutes | @bcgamesports (26–10) |
| @bcgamewinbig | 14 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @bcgamewinbig (14–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 39 of the 41 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 243 comparable posts for this entry, running 27 July 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 4 channels, the one whose matching posts we hold earliest is @official_bc_token. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 4 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 14:06 | 741,337 | -907 |
| 8 Nov 2026, 07:16 | 742,244 | -858 |
| 7 Nov 2026, 03:58 | 743,102 | -732 |
| 6 Nov 2026, 00:20 | 743,834 | -634 |
| 5 Nov 2026, 00:09 | 744,468 | -652 |
| 3 Nov 2026, 22:47 | 745,120 | -433 |
| 2 Nov 2026, 21:05 | 745,553 | -452 |
| 1 Nov 2026, 22:20 | 746,005 | -400 |
| 31 Oct 2026, 20:40 | 746,405 | -438 |
| 30 Oct 2026, 19:08 | 746,843 | -720 |
| 29 Oct 2026, 17:11 | 747,563 | -766 |
| 28 Oct 2026, 14:00 | 748,329 | -625 |
| 27 Oct 2026, 10:45 | 748,954 | -991 |
| 26 Oct 2026, 12:27 | 749,945 | -309 |
| 25 Oct 2026, 09:26 | 750,254 | -387 |
| 24 Oct 2026, 11:08 | 750,641 | -601 |
| 23 Oct 2026, 10:09 | 751,242 | -506 |
| 22 Oct 2026, 06:47 | 751,748 | -4,516 |
| 20 Oct 2026, 23:46 | 756,264 | -1,342 |
| 19 Oct 2026, 19:56 | 757,606 | first reading |
309 posts held, back to 27 July 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 200 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.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 309 (27 July 2026 – 11 November 2026) |
| Views total | 6,221,700 |
| Reactions total | 16,598 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 05:00 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 11 November 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 110 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.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /42076 Aug 2026, 17:05 UTC | 129 minutes – 29 minutes old | 10,500 views ~1 reaction | no checkpoint reading yet | not yet at 24h | not measurable yet |
| /42066 Aug 2026, 15:08 UTC | 286 minutes – 2.4 hours old | 22,600 views ~8 reactions | no checkpoint reading yetstill climbing at last reading | not yet at 24h | 86 minutesupper bound — already past half at first reading · provisional — final view count still climbing |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
32,848 reactions across 305 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 32,848 | 100.0% |
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 305 of the 309 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 32,848 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 309 most recent posts we hold, published 27 July 2026 to 11 November 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.
Telegram’s own ‘edited’ marker: 0 of 174 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Posted without readable text
👍19
Posted without readable text
👍34
Posted without readable text
👍35
⚡⚡⚡⚡⚡💵💵💵💵 CODE 👉 Join HERE & check the latest message for the code. — Go to Bonus page and copy paste above code to claim. ☑️ Wager over 5000 USD past 3days ☑️ Reward: Real Money (1x Rollover) 📌 Stay tuned to this channel for more bonuses & events! 🎁 🌐 Anti Ban Link ✉️ Global 📱 Twitter 📱 Whatsapp 📱 Facebook 📱 Instagram 🚫 Warning: Don't trust any ads on Telegram—they're not official
👍20
Posted without readable text
👍20
Posted without readable text
👍14
🟩 Join the BC Game TypeX Community! 🚀 Jump in today to chat with other players, stay updated with the latest news, and grab tons of daily rewards with no requirements! 🎁 📢 Official TypeX Channel 👥 Official TypeX Group ✨ Coco is waiting for you! Join now and grab your daily bonus! 🔥 🟩🎰🎰🎰🎰🎰 🚫 Warning: Don't trust any ads on Telegram—they're not official
👍8
Posted without readable text
👍39
⚔️ GLORY IN THE ARENA! Matt fights his way to an epic 27,195 WIN on Gladiator Legend! 🏆🔥 A true champion's moment! The arena is heating up! 💥 🟩🎰🎰🎰🎰🎰 🚫 Warning: Don't trust any ads on Telegram—they're not officia
👍48
🎲🎲🎲🎲🎲 GIVEAWAY. 🔥⚽🎉 Next week’s top internationals are loading and BCGame Sport is giving away Free Bets. 10 winners → $5 each. To enter: ➡️ Follow @bcgamewinsports ➡️ Comment with the flag of the country you support + your UID Draw is 20 November 🟩🎰🎰🎰🎰🎰
👍45
Posted without readable text
👍24
⚡⚡⚡⚡⚡💵💵💵💵 CODE 👉 Join HERE & check the latest message for the code. — Go to Bonus page and copy paste above code to claim. ☑️ Wager over 5000 USD past 3days ☑️ Reward: Real Money (1x Rollover) 📌 Stay tuned to this channel for more bonuses & events! 🎁 🌐 Anti Ban Link ✉️ Global 📱 Twitter 📱 Whatsapp 📱 Facebook 📱 Instagram 🚫 Warning: Don't trust any ads on Telegram—they're not official
👍16
Showing the 12 most recent of 309 posts we hold for @bcgamewin. 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.
We recorded 4 posts on @bcgamewin as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. 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 19 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.
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.
@bcgamewin named 7 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.
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.
References a handle that is not a live channel — we have no record it ever was one.
9 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“BC.Game 🔔 Notifications” (@bcgamewin), 741,337 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/bcgamewin.
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.