While hiking in the Alps mateπ₯ you are a wizzard!!!
π8β€3
Channel
@FXTradingVision
On this record: Topic Β· Observations Β· Also posting the same content Β· Growth Β· Engagement Β· What this channel posts Β· Reactions Β· Posts Β· Posts edited after publishing Β· Polls Β· Cite this entry
338,398subscribers
+27,605 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of 316,228β1,000,000.
| Telegram ID | -1001651583302 |
|---|---|
| Type | Channel |
| Username | @FXTradingVision |
| 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 | 29 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 29 September 2026 |
| On Telegram | t.me/FXTradingVision |
Crypto & trading β 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 99% 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.
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 word for word on 1 other registered channel. They sit inside a group of 4 channels that share the same post bodies 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 |
|---|---|---|---|
| @FXTradingVision/81473 Β· this entry7 Aug 2026, 13:15 UTC | @mikefxtv/305707 Aug 2026, 13:15 UTC | 1.00 | under a minute |
| @FXTradingVision/81478 Β· this entry7 Aug 2026, 14:05 UTC | @mikefxtv/305757 Aug 2026, 14:05 UTC | 1.00 | under a minute |
| @FXTradingVision/81495 Β· this entry7 Aug 2026, 15:58 UTC | @mikefxtv/305937 Aug 2026, 15:58 UTC | 1.00 | under a minute |
| @FXTradingVision/81411 Β· this entry7 Aug 2026, 07:58 UTC | @mikefxtv/306027 Aug 2026, 16:09 UTC | 1.00 | 8.2 hours |
| @FXTradingVision/81516 Β· this entry7 Aug 2026, 17:31 UTC | @mikefxtv/306147 Aug 2026, 17:31 UTC | 1.00 | under a minute |
| @FXTradingVision/81524 Β· this entry7 Aug 2026, 19:02 UTC | @mikefxtv/306227 Aug 2026, 19:02 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @mikefxtv | 6 (6/6 hand-verifiable sample passed) | 1.00 | under a minute | this entry (6β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. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
βPublished firstβ means first in this corpus. We hold 16 comparable posts for this entry, running 7 August 2026 to 7 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.
Across the whole group of 4, the earliest publisher we hold is @FXTradingVision β which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 8 August 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βs posts match, word for word or near enough, posts on 3 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable β 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times β 60%, no better than a coin flip β because it depends on how deep our own crawl happened to reach into each channelβs history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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 |
|---|---|---|
| 29 Sept 2026, 20:37 | 338,398 | -5,106 |
| 18 Sept 2026, 00:00 | 343,504 | +677 |
| 15 Sept 2026, 18:19 | 342,827 | +1,982 |
| 14 Sept 2026, 03:40 | 340,845 | +1,921 |
| 12 Sept 2026, 09:39 | 338,924 | +3,180 |
| 10 Sept 2026, 08:42 | 335,744 | +1,447 |
| 7 Sept 2026, 03:40 | 334,297 | +2,058 |
| 4 Sept 2026, 08:40 | 332,239 | +1,510 |
| 2 Sept 2026, 21:38 | 330,729 | +1,029 |
| 1 Sept 2026, 20:15 | 329,700 | +158 |
| 31 Aug 2026, 19:26 | 329,542 | +174 |
| 30 Aug 2026, 20:29 | 329,368 | +26 |
| 29 Aug 2026, 23:58 | 329,342 | +135 |
| 28 Aug 2026, 22:12 | 329,207 | -17 |
| 28 Aug 2026, 00:07 | 329,224 | +14 |
| 27 Aug 2026, 00:33 | 329,210 | +141 |
| 26 Aug 2026, 02:04 | 329,069 | +1,302 |
| 24 Aug 2026, 22:37 | 327,767 | +2,313 |
| 23 Aug 2026, 09:57 | 325,454 | +2,789 |
| 21 Aug 2026, 20:36 | 322,665 | first reading |
1,330 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 96 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 29 September 2026 |
|---|---|
| Posts held | 1,330 (7 August 2026 β 29 September 2026) |
| Views total | 3,307,907 |
| Reactions total | 41,742 |
| Forwards / comments | not exposed by the public surface β not measured, not estimated |
| Readings taken | 29 Sept 2026, 17:27 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.
Measured directly from 13 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.
48,497 reactions across 976 posts, in 14 distinct kinds. The most used accounts for 56.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| π | 27,469 | 56.6% | |
| β€ | 14,099 | 29.1% | |
| π₯ | 3,245 | 6.69% | |
| π | 1,136 | 2.34% | |
| π | 627 | 1.29% | |
| π― | 373 | 0.769% | |
| β‘ | 321 | 0.662% | |
| π | 264 | 0.544% | |
| π | 257 | 0.53% | |
| π | 208 | 0.429% | |
| β€βπ₯ | 185 | 0.381% | |
| π₯° | 173 | 0.357% | |
| π€© | 107 | 0.221% | |
| π | 33 | 0.068% |
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 977 of the 1,000 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 48,497 reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 August 2026 to 29 September 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.
While hiking in the Alps mateπ₯ you are a wizzard!!!
π8β€3
Video message, posted without a caption
π10β€3π1
THIS WEEK'S RESULTS IN MY VIP GROUP (so far) Week 40, 2026 π Trades shared: 16 β Win: 14 β Loss: 2 >> Win-ratio: 87.5% Another solid day in the books! We're on a roll and I'm not slowing down. The setups keep coming π This is what professional trading looks like. WANT TO COPY ALL MY TRADES? Click the button below to get FREE ACCESS to my VIP ππ»
π8π₯2π1
FXTradingVision l Forex & Crypto Signals π pinned Β«THIS WEEK'S RESULTS IN MY VIP GROUP (so far) Week 40, 2026 π Trades shared: 16 β Win: 14 β Loss: 2 >> Win-ratio: 87.5% Another solid day in the books! We're on a roll and I'm not slowing down. The setups keep coming π This is what professional trading looksβ¦Β»
1,300 USD in todayyyyy!!
π14β€4
Iβm dreaming ππππππ
π10
I SWEAR TO GOD YOUR THE BEST TRDER IVE SEEN IN MY LIFE
π8β€1
Close tp 2 here + 130 pips profit
π11β€4
β οΈYES, OUR VIP IS CURRENTLY FREEβ¦ AT 4000 MEMBERS IT WILL BE PAIDβ¦ 22 MORE FREE SPOTS LEFT πΈ
π19β€8
tp 1 hit + 40 pips Move sl to entry
π13β€6π₯2
Unbelievable, are u from one other π?π€
π11β€5π―3π1
Unbelievable, are u from one other π?π€
π11π―3β€2
Showing the 12 most recent of 1,330 posts we hold for @FXTradingVision. 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.
@FXTradingVision edited 7 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.
The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A pollβs figures keep moving after that, so each one is dated.
GOLD RIGHT NOW ποΈ
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Are you active this weekend? π€π€
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Do you like our new logo?
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only β there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each optionβs share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each optionβs own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 1,000 most recent posts we hold (the sample is capped at 1,000), published 18 August 2026 to 29 September 2026. Telegram labels each poll by kind β an anonymous poll, a quiz, a closed set of final results β and that label is reproduced rather than paraphrased.
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 29 September 2026 β this entry's latest reading, not the date you are reading this.
βFXTradingVision l Forex & Crypto Signals πβ (@FXTradingVision), 338,398 subscribers as measured 29 September 2026. Telegram Register, tgregister.com/channel/FXTradingVision.
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.