Hurry up and drop your feedback before Alex gets upset! Because if Alex really gets sulky, there might be NO MORE FREE SIGNALS in this channel next week! Come on, guys! Show some support and share your feedback! @DulcieGold
🔥1

Channel
@BmrTradingChannel
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Posts recorded as deleted · Cite this entry
6,168subscribers
-5,194 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001637491566 |
|---|---|
| Type | Channel |
| Username | @BmrTradingChannel |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 42 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/BmrTradingChannel |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 6 other registered channels. This entry also sits inside a group of 6 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 |
|---|---|---|---|
| @BMRCopy/182312 Aug 2026, 08:52 UTC | @BmrTradingChannel/9686 · this entry12 Aug 2026, 08:52 UTC | 1.00 | under a minute |
| @BmrTradingChannel/9769 · this entry15 Aug 2026, 14:49 UTC | @BMRCopy/186115 Aug 2026, 14:49 UTC | 1.00 | under a minute |
| @BmrTradingChannel/9980 · this entry28 Aug 2026, 08:03 UTC | @BMRCopy/198028 Aug 2026, 08:03 UTC | 1.00 | under a minute |
| @BMRCopy/34143 Nov 2026, 07:39 UTC | @BmrTradingChannel/11415 · this entry3 Nov 2026, 07:39 UTC | 1.00 | under a minute |
| @BMRCopy/34314 Nov 2026, 06:44 UTC | @BmrTradingChannel/11432 · this entry4 Nov 2026, 06:44 UTC | 1.00 | under a minute |
| @BMRCopy/34715 Nov 2026, 12:08 UTC | @BmrTradingChannel/11472 · this entry5 Nov 2026, 12:08 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @BMRCopy | 50 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (30–20) |
| @BMRCopyTrade | 23 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (23–0) |
| @peroinvesting | 9 (8/8 hand-verifiable sample passed) | 0.98 | 3.0 hours | @peroinvesting (6–3) |
| @alexgoldhunte0 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 3.0 hours | @alexgoldhunte0 (6–0) |
| @willygoldusd | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | @willygoldusd (6–0) |
| @thegoldengarry_official0 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 22 hours | @thegoldengarry_official0 (4–1) |
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. 42 of the 42 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 141 comparable posts for this entry, running 7 August 2026 to 6 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 6 channels, the one whose matching posts we hold earliest is @alexgoldhunte0. That is a statement about our reading window, not a claim of authorship.
Recorded under the keys clone_copy · clone_mutual · clone_source, last confirmed 13 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 6 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 |
|---|---|---|
| 10 Nov 2026, 17:59 | 6,168 | -23 |
| 6 Nov 2026, 20:25 | 6,191 | -28 |
| 3 Nov 2026, 09:18 | 6,219 | -25 |
| 31 Oct 2026, 14:49 | 6,244 | -33 |
| 28 Oct 2026, 22:21 | 6,277 | -18 |
| 26 Oct 2026, 06:27 | 6,295 | -33 |
| 23 Oct 2026, 05:18 | 6,328 | -75 |
| 20 Oct 2026, 06:51 | 6,403 | -24 |
| 17 Oct 2026, 05:57 | 6,427 | -33 |
| 14 Oct 2026, 13:40 | 6,460 | -51 |
| 10 Oct 2026, 21:58 | 6,511 | -119 |
| 4 Oct 2026, 20:20 | 6,630 | -804 |
| 25 Sept 2026, 01:59 | 7,434 | -114 |
| 16 Sept 2026, 09:21 | 7,548 | -245 |
| 12 Sept 2026, 20:16 | 7,793 | -744 |
| 9 Sept 2026, 03:37 | 8,537 | -1,293 |
| 4 Sept 2026, 06:01 | 9,830 | -104 |
| 1 Sept 2026, 04:27 | 9,934 | -108 |
| 31 Aug 2026, 07:36 | 10,042 | -206 |
| 30 Aug 2026, 05:37 | 10,248 | first reading |
346 posts held, back to 7 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 44 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 6 of 69 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 November 2026 |
|---|---|
| Posts held | 346 (7 August 2026 – 6 November 2026) |
| Views total | 2,678 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Nov 2026, 16:22 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.
73 reactions across 44 posts, in 10 distinct kinds. The most used accounts for 28.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 21 | 28.8% | |
| 🔥 | 14 | 19.2% | |
| 😁 | 11 | 15.1% | |
| 🤔 | 11 | 15.1% | |
| 🤡 | 7 | 9.59% | |
| 💯 | 3 | 4.11% | |
| 👏 | 2 | 2.74% | |
| 🤣 | 2 | 2.74% | |
| ❤🔥 | 1 | 1.37% | |
| 👌 | 1 | 1.37% |
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 44 of the 346 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 73 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 346 most recent posts we hold, published 7 August 2026 to 6 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 69 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).
Hurry up and drop your feedback before Alex gets upset! Because if Alex really gets sulky, there might be NO MORE FREE SIGNALS in this channel next week! Come on, guys! Show some support and share your feedback! @DulcieGold
🔥1
But once Alex delivered quality setups, suddenly everyone became too stingy to share their feedback?
👍1
Earlier, so many of you were asking for free signals.
Done secure our profits? Go share yours feedback to Alex Admin! 😎🫵🏻 @DulcieGold
🔥1
R2 : TP1 85pips ✅ Zerofloat setup sell running well! Secure half hold set BE+! 🔥🫵🏻 This is how waiting game & secure low risk setup!
🔥1
Gold sell now @ 4043.5 - 4048.5 sl : 4053.5 tp1 : 4038.5 tp2 : 4028.5 👉🏻Broker gold leverage 1:3000
Gold sell now
Do you guys want Alex signal?
🔥1
HIGH-IMPACT NEWS AHEAD 🔥 US Non-Farm Payrolls (NFP) US Unemployment Rate Average Hourly Earnings Canadian Employment Data Trade Smart. Stay Disciplined. Execute with Precision 📈
🔥VIP SIGNAL RESULTS — YESTERDAY Another strong XAUUSD session completed with the VIP group. 💰Total Profit: +$8,950.50 📉Early SELL setups captured the downside move from the 4140 area 📈Later BUY setups followed the recovery back toward 4135 ✅Despite a few losing trades, the overall session still closed strongly positive. Real-time signals. Clear entry zones. Structured trade management. Trading involves risk. Past…
DISCIPLINE. PATIENCE. PAYOUT. Hard now, easy later. The charts reward those who wait. Stick to the plan when emotions get loud. Skip the shortcuts. Take the setups that matter. Master yourself today, and the market pays you tomorrow.
🟡BMR TREND FORECAST | XAUUSD H1 Gold has shifted bearish in the short term following a sharp rejection from 4147–4150 and successive lower highs. Price is trading near 4047 after breaking below 4060–4063. A corrective rebound into this resistance zone could attract further selling, while 4032–4029 remains the immediate support to watch. Keylevel Resistance: 4060–4063 → 4105 (Breakout Level) → 4147–4150 Support: …
Showing the 12 most recent of 346 posts we hold for @BmrTradingChannel. 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 1 post on @BmrTradingChannel 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.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“BMR Trading Channel” (@BmrTradingChannel), 6,168 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/BmrTradingChannel.
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.