Channel
@FX_signal_1
On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
599subscribers
-14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001879731951 |
|---|---|
| Type | Channel |
| Username | @FX_signal_1 |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/FX_signal_1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 17:38 | 599 | -1 |
| 9 Sept 2026, 01:59 | 600 | -6 |
| 29 Aug 2026, 21:14 | 606 | -3 |
| 21 Aug 2026, 23:53 | 609 | -1 |
| 14 Aug 2026, 04:48 | 610 | -4 |
| 8 Aug 2026, 03:03 | 614 | no change |
| 7 Aug 2026, 18:01 | 614 | +1 |
| 7 Aug 2026, 15:05 | 613 | first reading |
20 posts held, back to 27 February 2025 — 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 20 posts for this entry, the most recent from 3 March 2025. An engagement rate over an empty window would be a number about nothing.
از دوشنبه 24 تا جمعه 28 فوریه AUDUSD SELL 20PIP🟢 GBPAUD SELL 20PIP🟢 CHFJPY BUY 60PIP🔴 XAUUSD SELL 20PIP🟢 GBPJPY BUY 20PIP🟢 XAUUSD SELL 50PIP🟢 XAUUSD SELL 100PIP🟢 AUDCAD SELL 20PIP🟢 GBPJPY BUY 50PIP🟢 EURGBP SELL 20PIP🟢 USDCHF BUY 20PIP🟢 USDCHF BUY 20PIP🟢 AUDJPY BUY 60PIP🔴 EURGBP SELL 50PIP🟢 AUDCAD SELL 50PIP🟢 TOTAL +420 PIP🟢
🔴 AUDCAD sell at : 0.9065 Target1 : 0.9045 Target2 : 0.9015 Target3 : 0.8965 StopLoss : 0.9125
🔴 EURGBP sell at : 0.8295 Target1 : 0.8275 Target2 : 0.8245 Target3 : 0.8195 StopLoss : 0.8355
🟢 USDCHF buy at : 0.8945 Target1 : 0.8965 Target2 : 0.8995 Target3 : 0.9045 StopLoss : 0.8885
🟢 AUDJPY buy at : 94.15 Target1 : 94.35 Target2 : 94.65 Target3 : 95.15 StopLoss : 93.55
🟢 CHFJPY buy at : 166.65 Target1 : 166.85 Target2 : 167.15 Target3 : 167.65 StopLoss : 166.05
✅✅ TP 2 +50 pip
❌❌ SL -60 pip
✅✅ TP 2 +50 pip
✅✅ TP 2 +50 pip
✅✅ TP 1 +20 pip
✅✅ TP 1 +20 pip
Showing the 12 most recent of 20 posts we hold for @FX_signal_1. 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“𝗕𝗟𝗨𝗘 𝗙𝗢𝗥𝗘𝗫” (@FX_signal_1), 599 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/FX_signal_1.
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.