Channel
@FMCFXSIGNALS
On this record: Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
252subscribers
-4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001227784489 |
|---|---|
| Type | Channel |
| Username | @FMCFXSIGNALS |
| Created | Between 1 March 2018 and 17 February 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 1 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 1 September 2026 |
| On Telegram | t.me/FMCFXSIGNALS |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Sept 2026, 14:25 | 252 | -2 |
| 25 Aug 2026, 18:17 | 254 | -1 |
| 13 Aug 2026, 02:56 | 255 | -1 |
| 7 Aug 2026, 02:02 | 256 | no change |
| 6 Aug 2026, 06:43 | 256 | first reading |
19 posts held, back to 17 February 2021 — 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 19 posts for this entry, the most recent from 15 June 2026. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 11 months. If they remain inactive for the next 7 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Photo, posted without a caption
GU M15 - BYSL TO SSL PURGE https://www.tradingview.com/x/hMTcqQNH/
Photo, posted without a caption
TP HIT +35 PIPS✅ https://www.tradingview.com/x/Ru6bTk6b/
🔥🔥🔥
Take Partials if you want, stops to entry. +30 Pips✅✅ Holding till 1.8400 https://www.tradingview.com/x/iIZkozJq/
GBPUSD BUY @ 1.3830 TP 1 : 1.3880 TP 2 : 1.3920 SL 1.3810 https://www.tradingview.com/x/FiwL2Cyh/
🔰DELETE ORDER
NZDUSD BUY LIMIT @ 0.7129 TP 1 : 0.7184 TP 2 : 0.7230 SL 0.7093 https://www.tradingview.com/x/X7Dk2GCp/
FULL CLOSE EURJPY +90 PIPS💰✅ 0% DD🔥🔥 https://www.tradingview.com/x/hCYIc9Xq/
GBPNZD HIT TP 2 +70 PIPS💰✅ https://www.tradingview.com/x/Pmtosuz7/
Showing the 12 most recent of 19 posts we hold for @FMCFXSIGNALS. 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.
@FMCFXSIGNALS named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 1 September 2026 — this entry's latest reading, not the date you are reading this.
“FOREX MILLION CAPITAL” (@FMCFXSIGNALS), 252 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/FMCFXSIGNALS.
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.