Quick answer: On 13 October 2026, the engine issued a limit sell order for EUR/NZD based on a liquidity sweep and a confirmed change of character (CHoCH). The trade was filled at 1.99626 during the London session. Price reached TP1 and TP2, resulting in a realized profit of 0.5R and 13.5 pips after closing the remaining exposure at 1.98948.
*Real H1 chart: blue = entry, red = stop, green = TP1-TP3. Times in UTC.*
The setup: why the engine took it
The engine identified a sell opportunity for EUR/NZD using historical Smart Money engine rules, predating the updated five-check system introduced on 15 October 2026. The logic was as follows: The Higher Timeframe bias was neutral. The engine observed a sweep of buy-side liquidity, followed by a CHoCH (Change of Character) signal, indicating a potential shift in market structure. The entry was positioned within a premium zone, specifically targeting a Fair Value Gap (FVG) that overlapped with an Order Block. These combined factors suggested a potential reversal to the downside.
The trade plan
| Item | Value |
| :--- | :--- |
| Entry | 1.99626 |
| Stop Loss | 1.99896 |
| TP1 | 1.99219 |
| TP2 | 1.98948 |
| TP3 | 1.98542 |
| Risk (pips) | 27 |
| Order type | LIMIT |
| Session | London |
What happened
| Time (UTC) | Event |
| :--- | :--- |
| 2026-10-13 09:00 | Signal Published |
| 2026-10-13 21:00 | Order Filled |
| 2026-10-14 03:00 | TP1 Hit |
| 2026-10-14 12:00 | TP2 Hit |
| 2026-10-14 14:00 | Trade Closed |
The trade was filled twelve hours after the initial signal at 21:00 UTC. It hit the first two targets sequentially over the next fifteen hours before the final position was closed. The market did not reach the stop loss or the third take profit level.
Result
The trade outcome was recorded as TP1 hit, though the exit was managed to capture the move to TP2. The total result was 0.5R, amounting to 13.5 pips. Following the standard management plan, one third was closed at TP1, and the remaining portion was exited at the TP2 level when the position was closed manually at 14:00 UTC on 14 October.
What this trade teaches
- Market conditions vary: The price reached a best move of 87.1 pips (3.23R) during the duration of the trade, demonstrating that the potential reward was significantly higher than the realized 0.5R, yet the trade closed earlier according to the management plan.
- Risk Management: The stop loss of 27 pips was never touched, and the worst move against the entry was only 0.78R, which kept the trade within safe risk parameters.
- Execution Timing: The trade was active for 17 hours. This highlights the importance of patience, as the entry was not triggered until 12 hours after the initial publication of the signal.
Frequently asked questions
Why was the trade closed before TP3?
The management rules dictate that trades should be exited after a specific timeframe or if conditions change. In this instance, the position was closed at 14:00 UTC on 14 October, approximately 17 hours after the entry, rather than waiting for the third take profit level to be triggered by the market.
How is the R-multiple calculated?
The R-multiple is calculated based on the sum of the shares closed at each target. In this case, one third was closed at TP1 and the remaining two thirds were closed at the TP2 level. This cumulative result provides a snapshot of the actual realized profit relative to the initial risk placed on the trade.
What does a neutral HTF bias mean?
A neutral High Timeframe bias suggests that the long-term trend for the pair was not clearly trending upward or downward. The engine opted to take the trade based on the immediate micro-structure signals, specifically the liquidity sweep and the FVG, rather than relying on a strong directional bias from higher timeframes.
Every signal, win or lose, is on the record: weekly results · how the signals are built · today's signals · get free signals.
*Educational only, not financial advice. Past results do not guarantee future results.*
