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 24 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.
Observations
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.
Content that also appears on other registered channels
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.
Matching posts — open both and compare (6 of the pairs behind the counts below)
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
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. 1 of the 3 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 11 comparable posts for this entry, running 22 June 2026 to 8 August 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.
Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).
Of the group of 2 channels, the one whose matching posts we hold earliest is @forexrus7. That is a statement about our reading window, not a claim of authorship.
Recorded under the key 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.
Channels linked by matching posts
This channel is in a group of 2 registered channels linked by matching posts. 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.
10 measurements spanning 94 days, net +5. 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 210–223 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
9 Nov 2026, 15:07
221
+3
1 Nov 2026, 21:54
218
+5
18 Oct 2026, 23:36
213
+1
12 Oct 2026, 20:47
212
+1
1 Oct 2026, 14:14
211
-1
16 Sept 2026, 03:59
212
-2
7 Sept 2026, 20:42
214
-1
29 Aug 2026, 20:55
215
-1
8 Aug 2026, 10:47
216
no change
7 Aug 2026, 16:37
216
first reading
Engagement
11 posts held, back to 22 June 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 1 page of 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 11 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
4 reactions across 4 posts, in 1 kind.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
4
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 4 of the 11 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 22 June 2026 to 8 August 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.
🚀 Gold Striker EA | Strong Performance During Gold’s Rally
Last week, Gold made a strong bullish move that caught many traders, and many grid and martingale EAs, on the wrong side of the market.
While a lot of recovery-based systems suffered heavy drawdowns or even blew accounts, Gold Striker EA was built to trade momentum.
📊 Client results last week: +5% to +14%
Even during Gold’s explosive rally, Gold Striker w…
Hi everyone!
Great news! We’re excited to launch our another trading bot for the community.
If you’d like to trade Gold using our bot, you can now get started!
Gold Striker EA
Minimum deposit: $400
Risk: 2% per trade
Average of 1–4 trades per day, depending on Gold’s market volatility.
Here is the performance of our model account over the last four months:
April: +13%
May: +12%
June: +37%
July: +27%
Overall Pr…
🚀 Patience pays in trading.
One of the biggest truths in the markets is this:
"The stock market is a device for transferring money from the impatient to the patient." – Warren Buffett
The same principle applies to our BTC EA.
Our BTC strategy continues to reward those who trusted the process and stayed disciplined.
Many of our early clients have already achieved 100% to 200% returns, while others continue to compo…
🚀 BTC EA Aggressive Account Update 🚀
🔥 +637% COMPOUNDED PROFIT since February 20 🔥
What started as a small trading account has grown aggressively through the power of compounding and the volatility of Bitcoin opportunities.
✅ +637% Total Growth
✅ Fully Automated Trading
✅ No Manual Entries Required
✅ Designed to Capture BTC Market Movements
✅ Single entry with stop loss
✅ No grid, no martingale, no layering.
📈 Th…
🚨 100% PROFITS ALREADY! 🚨
Another milestone achieved! 🎉
Our early BTC EA users have now doubled their accounts, with many already reaching 100% profit! 💰🔥
And the best part?
Several accounts are now closing in on the 200% profit milestone, and it's only a matter of time before they get there. 📈🚀
This is exactly why our clients continue to trust our Bitcoin EA:
✅ Fully automated trading
✅ Proven and consistent pe…
🚀 BTC EA clients are crushing it!
Almost all of our clients have already crossed the 100% profit mark, and several accounts are now on track to hit 200% gains! 📈
The best part? This isn't based on high-risk strategies.
✅ Single-entry trades only
✅ No martingale
✅ No grid trading
✅ Every trade has a Stop Loss
✅ Automated trading – set and forget
✅ Designed for steady long-term growth
Consistency beats hype. Our BT…
Happy to see our clients consistently making profits with our BTC automated trading software! 🚀
Let the software do the trading, no emotions, just a disciplined strategy.
Many of our clients have already achieved 100%+ returns. 📈
⚠️ Disclaimer: Trading involves risk. Past performance does not guarantee future results.
Contact @MarrkDy to get started.
🚀 BTC EA Performance Update 🚀
📈 +465% Growth Since February 20
The market has presented incredible opportunities, and our BTC EA has capitalized on them with disciplined, rule-based execution.
🔥 Key Features
✅ Fully automated Bitcoin trading
✅ Single entry w/ stop loss
✅ No grid. No layering. No martingale
✅ With trailing stop to lock-in profit.
✅ Breakout scalping strategy
📊 Results
Performance Since February 20…
🚀 BTC EA UPDATE 🚀
What a month! 🔥
+51% PROFIT in June alone! 📈💰
The market rewards discipline, and our BTC EA continues to deliver exceptional results.
✅ Single Entry Strategy
✅ Hard Stop Loss on Every Trade
✅ Trailing Stop to Lock In Profits
✅ Breakout Scalping Algorithm
✅ No Grid
✅ No Martingale
✅ Fully Automated
✅ Risk Management Built In
Consistency beats hype—but these results speak for themselves. 📊
If yo…
🚨 BTC EA RESULTS ARE SPEAKING FOR THEMSELVES 🚨
In just a short time, 14 of my clients have already achieved 100%+ profit using my BTC Expert Advisor (EA). 📈🔥
This isn't about chasing hype, it's about having a disciplined, automated strategy that trades based on predefined rules.
✅ Fully automated BTC trading
✅ No emotional decision-making
✅ Consistent strategy execution
✅ All trades with stop loss. No grid. No mar…
🚨 ANOTHER WAVE OF 100%+ RESULTS! 🚀
The BTC EA keeps delivering.
More clients have now doubled their trading accounts, with several already reaching 100%+ returns while trading fully automated.
📈 Real client results:
💰 $404 deposit → $497 profit
💰 $521 deposit → $550 profit
💰 $206 deposit → $229 profit
💰 $300 deposit → $293 profit
…and more accounts continuing to grow.
This is what happens when you trust the pro…
Showing the 11 most recent of 11 posts we hold for @marketwizardsforex. 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.
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 9 November 2026 — this
entry's latest reading, not the date you are reading this.
“Market Wizards Forex” (@marketwizardsforex), 221 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/marketwizardsforex.
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.