Telegram RegisterThe public register of Telegram
Telegram profile photo for FXFARO | PUBLIC SIGNALS

Channel

FXFARO | PUBLIC SIGNALS

@fxfaropublic

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

10,657subscribers

-14,089 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002146602787
TypeChannel
Username@fxfaropublic
CreatedBetween 1 December 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/fxfaropublic

Topic

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)
Posted firstThenOverlapGap
@fxfaro_public/30457 Aug 2026, 13:04 UTC@fxfaropublic/6612 · this entry7 Aug 2026, 13:05 UTC1.00under a minute
@fxfaropublic/6613 · this entry7 Aug 2026, 13:09 UTC@fxfaro_public/30467 Aug 2026, 13:09 UTC1.00under a minute
@fxfaro_public/30557 Aug 2026, 15:17 UTC@fxfaropublic/6622 · this entry7 Aug 2026, 15:17 UTC1.00under a minute
@fxfaropublic/6623 · this entry7 Aug 2026, 15:30 UTC@fxfaro_public/30567 Aug 2026, 15:30 UTC1.00under a minute
@fxfaropublic/6626 · this entry7 Aug 2026, 16:55 UTC@fxfaro_public/30597 Aug 2026, 16:55 UTC1.00under a minute
@fxfaro_public/30627 Aug 2026, 19:12 UTC@fxfaropublic/6629 · this entry7 Aug 2026, 19:12 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@fxfaro_public7 (7/7 hand-verifiable sample passed)1.00under a minutethis entry (4–3)
@FXFARO_FREEGROUP7 (7/7 hand-verifiable sample passed)1.00under a minute@FXFARO_FREEGROUP (4–3)
@FXFARO_FREE7 (7/7 hand-verifiable sample passed)1.00under a minute@FXFARO_FREE (4–3)

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. 11 of the 11 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.

Growth

10,65724,74617,701.57 August 2026 — 24,746 subscribers7 August 2026 — 24,746 subscribers7 August 2026 — 24,744 subscribers8 August 2026 — 24,718 subscribers9 August 2026 — 24,691 subscribers10 August 2026 — 20,521 subscribers11 August 2026 — 20,394 subscribers12 August 2026 — 20,366 subscribers13 August 2026 — 20,313 subscribers14 August 2026 — 20,260 subscribers16 August 2026 — 20,200 subscribers17 August 2026 — 20,136 subscribers18 August 2026 — 20,002 subscribers19 August 2026 — 19,988 subscribers20 August 2026 — 17,793 subscribers22 August 2026 — 17,717 subscribers23 August 2026 — 17,650 subscribers25 August 2026 — 15,685 subscribers26 August 2026 — 15,628 subscribers27 August 2026 — 15,606 subscribers27 August 2026 — 15,602 subscribers29 August 2026 — 14,770 subscribers30 August 2026 — 13,258 subscribers31 August 2026 — 13,211 subscribers1 September 2026 — 13,182 subscribers2 September 2026 — 13,154 subscribers3 September 2026 — 12,412 subscribers5 September 2026 — 12,395 subscribers8 September 2026 — 10,998 subscribers11 September 2026 — 10,923 subscribers13 September 2026 — 10,813 subscribers14 September 2026 — 10,747 subscribers16 September 2026 — 10,697 subscribers18 September 2026 — 10,657 subscribers7 August 202618 September 2026
34 measurements spanning 42 days, net -14,089. 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 8,544–26,859 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
18 Sept 2026, 13:5510,657-40
16 Sept 2026, 09:1810,697-50
14 Sept 2026, 13:2110,747-66
13 Sept 2026, 02:1910,813-110
11 Sept 2026, 01:5610,923-75
8 Sept 2026, 06:1710,998-1,397
5 Sept 2026, 02:2012,395-17
3 Sept 2026, 10:5812,412-742
2 Sept 2026, 04:5513,154-28
1 Sept 2026, 04:4513,182-29
31 Aug 2026, 04:1313,211-47
30 Aug 2026, 06:4813,258-1,512
29 Aug 2026, 03:3314,770-832
27 Aug 2026, 23:5915,602-4
27 Aug 2026, 01:3515,606-22
26 Aug 2026, 03:5515,628-57
25 Aug 2026, 00:2915,685-1,965
23 Aug 2026, 14:3917,650-67
22 Aug 2026, 01:0717,717-76
20 Aug 2026, 20:5317,793first reading

Engagement

310 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 33 pages 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 310 posts for this entry, the most recent from 22 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 39s
Average length
7s

Measured directly from 22 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.

Reaction mix

48 reactions across 35 posts, in 7 distinct kinds. The most used accounts for 52.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2552.1%
❤714.6%
👌714.6%
👏48.33%
👍24.17%
🤩24.17%
🤯12.08%

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 38 of the 310 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 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 310 most recent posts we hold, published 7 August 2026 to 22 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.

Recent posts

22 Aug 2026, 21:36 UTC6 viewsread 22 August 2026

I'm getting A LOT of messages from people with questions about Funded Passing and Funded Management. 👀 So I'm ONLINE in the chat right now. Not sure how challenge passing works? Questions about getting your funded account connected to our management system? Want to understand the risk, payouts or the full process? MESSAGE ME. @fxfaro I'll personally answer your questions and explain exactly how it works. 🔥

22 Aug 2026, 20:56 UTC14 viewsread 22 August 2026
Video

FULL SCREEN VIDEO OF AMBER’S FUNDED ACCOUNT. 👀🔥 She’s only been connected to our Funded Management system for ONE DAY. And we’ve taken just ONE trade. Account size: $50K Current profit: +$943 ROI: +1.89% ONE DAY. ONE TRADE. +$943. And look at the risk we’re using… No overtrading. No gambling. No ridiculous lot sizes. Just our LOW-RISK, SINGLE TP strategy doing exactly what it’s designed to do. This is only …

22 Aug 2026, 19:18 UTC20 viewsread 22 August 2026

🥇TOMORROW I’M DROPPING AN INSANE FREE GOLD ANALYSIS! Stay READY for it… you don’t want to miss this. @fxfaro

22 Aug 2026, 18:33 UTC23 viewsread 22 August 2026

✅️ACCORDING TO MY STATS, 4152 POEPLE JOINED.. https://t.me/m/no_1qvwSNzk0

22 Aug 2026, 16:00 UTC32 viewsread 22 August 2026

All you need to do is answer 2 simple questions: 1️⃣ How much capital are you currently trading with? 2️⃣ What’s your monthly profit goal with trading? Send me your answers and I’ll grant you access. Don’t miss this, last time spots filled fast 💵 DM ME NOW @fxfaro

22 Aug 2026, 16:00 UTC32 viewsread 22 August 2026

You know what, I’ll give 25 people the chance to join the VIP for free today ONLY!

22 Aug 2026, 14:06 UTC39 viewsread 22 August 2026

📍This Week’s VIP Profit Recap: +21490 pips secured! 📈🔥 Here’s what that looks like based on your lot size: 💸 1.00 LOT = $ 214900 💸 0.10 LOT = $ 21490 💸 0.01 LOT = $ 2149 This is what YOU could’ve earned this week. Still on the sidelines? JOIN HERE: https://t.me/m/no_1qvwSNzk0

22 Aug 2026, 13:13 UTC40 viewsread 22 August 2026

LAST WEEK WAS ABSOLUTELY CRAZY. 💰🔥 The GOLD and BTC entries were NEXT LEVEL. 🤯 WIN RATE: 96.2% And here's the important part... EVERYTHING was traded using our ONE TP STRATEGY. No overmanagement. No closing half the trade at TP1. No TP1, TP2, TP3 nonsense. ONE setup. ONE SL. ONE TP. Clean execution. Patience. FULL profits when TP hits. 96.2% win rate with ONE TP. Let that sink in. 👀🔥 @fxfaro

22 Aug 2026, 13:02 UTC34 viewsread 22 August 2026
Photo

📍 Last Week’s VIP Results: ✅ +22380 pips profit 🛑 -890 pips loss 📈 Net: +21490 pips 💯 Win Rate: 96.2%

22 Aug 2026, 10:56 UTC39 viewsread 22 August 2026

I've spent the past hour analyzing BTC across both the higher and lower time frames.! Something very interesting is developing. The charts are starting to align, and this could lead to a high-probability opportunity. Don't miss what's coming. Join here before I share the full analysis and trade idea: 👉 https://t.me/m/k6Lm7K7mODQ0

Showing the 12 most recent of 310 posts we hold for @fxfaropublic. 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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“FXFARO | PUBLIC SIGNALS” (@fxfaropublic), 10,657 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/fxfaropublic.

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.