Forex Fury V6 / CORE 1.4
Commercial scalping + grid EAs (licensed .set files)
Every configuration came in below profit factor 1.0 net of costs (0.73–0.90). A zero-cost control pins gross PF at ≈1.0 — a coin flip. The deployable edge is not in the parameters; same no-edge grid+martingale family as basket-grid.
- Category
- Commercial EA
- Window
- 2023–2026 (3.4y)
- Instruments
- EURUSD, GBPUSD, USDJPY, AUDUSD (per vendor sets)
- Timeframe
- M1 / M15 / H1 (tested on M15)
- Tested
- 2026-06-20
The story in one line
Brent’s licensed Forex Fury V6 and CORE 1.4 .set files, run on real Dukascopy M15 data over a 3.4-year out-of-sample window (2023–2026), lose money in every configuration: net profit factor lands in the 0.73–0.90 range against a deployment bar of PF > 1.2. Every monthly mean return is negative (−0.13% to −1.38%/mo) versus the +5–7%/mo the systems advertise.
The decisive result is the zero-cost control: strip all costs, and the gross profit factor pins at ≈1.0 (a coin flip) for every entry proxy. There is no directional edge in the parameters. The grid + money-target machinery simply manufactures a high win rate sitting on a fat-tailed loss distribution — the same no-edge grid+martingale family the prior basket-grid backtest already failed (gross PF 1.01 / net 0.51).
The deployable edge that would justify $5k on Monday is not in the .set files, and there is no sign the unknown encrypted entry trigger supplies one on these pairs and windows.
Headline results — net of realistic costs
Costs: effective spread+commission (EURUSD 0.9 / GBPUSD 1.3 / USDJPY 1.0 pip round-turn), 0.3 pip slippage on stops, 0.5 pip/night swap.
| Config (fidelity) | Trades | Win% | PF (net) | Tot ret 3.4y | Max DD |
|---|---|---|---|---|---|
| EURUSD M15 default — meanrev (HIGH) | 712 | 50.7% | 0.90 | −1.2% | 1.5% |
| EURUSD M15 default — momentum (HIGH) | 712 | 48.7% | 0.84 | −2.1% | 2.2% |
| USDJPY scalp +Stoch (LOW, M1→M15) | 518 | 70.7% | 0.88 | −5.1% | 10.1% |
| GBPUSD H1 swing, 0.01 lot (HIGH) | 288 | 58.0% | 0.83 | −5.0% | 7.2% |
| GBPUSD H1 swing, 0.10 native lot (HIGH) | 690 | 89.7% | 0.75 | −44.2% | 50.2% |
The 0.10-native GBPUSD row is the martingale tail made visible: 89.7% of baskets win ~$10, but the losers average −$123 and the account bleeds 44% with a 50.2% drawdown — the canonical “smooth curve until it isn’t” grid failure. Per-pair filter tests (all 7 scalping sets at shipped lots) did not restore an edge: the full portfolio loses even with all costs removed (−70%, DD 68%).
The decisive test — zero-cost control
Re-run with all costs set to zero to ask the one question that matters: is there any entry edge before the broker takes its cut?
| Config | meanrev gross PF | momentum gross PF |
|---|---|---|
| EURUSD M15 default | 1.028 | 0.951 |
| EURUSD [regular] scalp | 0.925 | 1.016 |
| USDJPY scalp +Stoch | 0.906 | 0.906 |
| GBPUSD H1 swing 0.01 | 0.892 | 0.939 |
Best gross PF across everything ≈ 1.0–1.03 — a coin flip. A strategy with a real edge would show gross PF comfortably above 1.1 even through a rough proxy, and the money-target grid would amplify it. It doesn’t. Gross PFs straddle 1.0 (0.52–1.09 across the full set sweep) — the signature of no edge + noise, not a real signal. The conclusion triangulates three ways: net PF below 1.0, zero-cost gross PF at a coin flip, and the prior independent basket-grid failure.
Verdict: FAIL (net PF 0.73–0.90). Do not deploy. Not close. Every licensed configuration loses net of costs, and the zero-cost control proves the deployable edge is not in the parameters — the gross result is a coin flip. This is not “needs more tuning”; it is the same no-edge, grid+martingale family already failed once. Forex Fury V6 / CORE 1.4 is retired.
Frequently asked
Is Forex Fury V6 profitable in 2026?
Not in this independent backtest. Every configuration of the licensed V6 and CORE 1.4 .set files came in below profit factor 1.0 net of realistic costs (range 0.73–0.90), against a deployment bar of PF > 1.2. A zero-cost control run pins gross profit factor at roughly 1.0 — a coin flip — meaning there is no directional edge in the parameters.
Why can the entry edge not be found in the .set files?
The .set files expose the full risk/exit/grid/timing/filter machinery but not the proprietary entry trigger, which lives inside the encrypted .ex5. We tested disclosed entry proxies plus the documented Stochastic rule and ran a zero-cost control to isolate any edge. No proxy reached an edge, and the high-fidelity M15-native default is also a coin flip gross — so there is no sign the unknown trigger supplies a deployable edge on these pairs and windows.
Methodology: The Validation Gauntlet — pre-registered spec, 11-gate battery, real market data.
Full reproducible report: backtests/fury/REPORT.md in the source repository.
Author: Brent Akamine (Founder, Vinovest). Backtests are not investment advice.