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 10 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 why it has no browse page of its own yet.
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 word for word on 3 other registered channels. 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)
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. 12 of the 12 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 7 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.
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).
Across the whole group of 4, the earliest publisher we hold is @FXFARO_FREE. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, 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.
Also posting the same content
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.
7 measurements spanning 5 days, net -72. 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 85,576β85,670 and does not start at zero.
Measurement log β every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 18:57
85,587
-11
11 Aug 2026, 16:52
85,598
-8
10 Aug 2026, 13:47
85,606
-19
9 Aug 2026, 15:14
85,625
-16
8 Aug 2026, 16:08
85,641
-18
7 Aug 2026, 19:30
85,659
no change
7 Aug 2026, 19:23
85,659
first reading
Engagement
94 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 15 pagesof Telegramβs post history, 20 posts per page.
ERR Β· 30 days
6.90%
avg views Γ· 85,587 subscribers
Avg views / post
5,910
94 posts measured
Reaction rate
5.01%
reactions Γ· views Β· ER floor
Posts in window
94
of 94 held
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 90 of 94 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days Β· latest post in window 12 August 2026
Posts held
94 (7 August 2026 β 12 August 2026)
Views total
555,207
Reactions total
26,666
Forwards / comments
not exposed by the public surface β not measured, not estimated
Readings taken
12 Aug 2026, 18:46 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.
What this channel posts
Video runtime
3s
Average length
3s
Measured directly from 1 video 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.
Reaction mix
26,666 reactions across 90 posts, in 5 distinct kinds. The most used accounts for 25.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
π
6,817
25.6%
β€
6,716
25.2%
π
6,598
24.7%
π₯
6,534
24.5%
π
1
0.004%
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 90 of the 94 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 26,666reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 94 most recent posts we hold, published 7 August 2026 to 12 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.
Telegram Stars
Stars received
1
across the posts below
Posts paid on
1
of 94 we hold a reading for Β· 1%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars β bought with money β on a post by @fxfaro_public. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 94 most recent posts we hold for this entry, published 7 August 2026 to 12 August 2026. Star counts above 1,000 reach us in Telegramβs short form and carry the same three-significant-figure rounding as everything else on this page.
The opportunities just KEEP coming, especially with GOLD. π₯
And just to make this 100% clear...
I DO NOT share GOLD trades publicly.
These setups are simply too valuable. My exact GOLD entries, SL, TP and live updates are shared exclusively inside VIP.
If you want to be ahead of 99% of traders instead of seeing the results afterwards...
JOIN HERE: π
https://t.me/m/-BwzlxT7OGVk
My CPI bias inside VIP is SUPER clear!
I strongly believe something interesting is about to happen with GOLD.
The full bias, analysis and plan are already inside VIP.
JOIN HERE: https://t.me/m/-BwzlxT7OGVk
The amount of people who messaged me about the Funded Summer Discount has been INSANE. π€―
Even after the offer officially ended, the messages just kept coming in.
Yesterday, I personally gave a few more people one final chance to get in at the Summer Discount price.
And trust me... I had to be selective.
A lot of people took action during the sale.
Some waited and missed it.
And some were lucky enough to get oneβ¦
Stop using multiple TPs.
And you will go MUCH further in your trading..
Seriously.
That TP1, TP2, TP3 habit is holding you back more than you think.
π77π68π₯67β€63
Showing the 12 most recent of 94 posts we hold for @fxfaro_public. 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 12 August 2026 β this
entry's latest reading, not the date you are reading this.
βFXFARO | PUBLIC TRADES π¬π§β (@fxfaro_public), 85,587 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/fxfaro_public.
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.