11 NOVEMBER 2026 · 66 HAZEM SIGNAL · 5M SELL · TREND
Two Hazem SELLs Shared a Timestamp. Which One Reached TP3?
Two Hazem SELL plans were created at 09:15 UTC on 11 November. The five-minute TREND record activated 52 minutes later and reported TP3 at noon UTC. Following its full identity shows which levels and milestones belong to that case, and where the evidence ends.
Open CyGuru Gold Terminal to inspect signal plans and lifecycle events →
The production evidence
This selected favorable example is an indicator-reported reference observation. The production gateway retained a separate activation report and an actual TP3_HIT with the same signal identity. Engine 66-HAZEM-V1, payload schema 1, OANDA:XAUUSD, 5-minute timeframe, SELL and TREND were recorded. A separate script build hash was unavailable.
Signal ID 66-HAZEM-V1|OANDA:XAUUSD|5|1794388500000
TP3 event ID 66-HAZEM-V1|OANDA:XAUUSD|5|1794388500000|1794398400338|TARGET
Production feed observed through .
All 5 production messages retained the same original Entry, SL and three targets, along with the same creation and expiry timestamps and setup fields. The event trail contains no earlier stop or invalidation for this identity. The receiver timestamps below come from the matching stored rows.
| Field | Level | Distance | Original risk multiple |
|---|---|---|---|
| Entry | 4055.274 | — | — |
| Original SL | 4058.351 | 3.077 adverse | 1.000R |
| TP1 | 4051.736 | 3.538 favorable | 1.150R |
| TP2 | 4048.841 | 6.433 favorable | 2.091R |
| TP3 | 4044.981 | 10.293 favorable | 3.345R |
One reference R is the absolute distance from the original entry to the original stop. Each target multiple divides the distance from entry by that fixed denominator. The ratios describe the proposal’s price levels. Broker fills, commissions, spread, slippage and P&L are unverified.
| Recorded stage | Source time | Receiver time |
|---|---|---|
| SIGNAL_CREATED | ||
| SIGNAL_UPDATED · activation | ||
| TP1_HIT | ||
| TP2_HIT | ||
| TP3_HIT |
Replay of the site’s retained one-minute ranges
The signal-specific collector audit returned 114 OANDA:XAUUSD one-minute bars. The audited window has no missing minute slots. For a SELL, a low at or below a target counts as a nominal touch and a high at or above the original stop counts as a nominal stop. An earlier stop contradicts target-first ordering. A bar touching both requires finer verified observations to resolve the order. The window runs from the activation minute through the TP3 report minute. The activation minute is partial relative to the event clock and contains neither the stop nor TP1.
The maximum retained high in that window is 4056.170, below the original stop. No stop-before-target or same-bar stop/target conflict appears in these ranges. The site’s collector and the indicator both rely on TradingView inputs. An independently authenticated matching OHLC series was unavailable, so the replay remains a diagnostic on the collector data.
| Threshold | Minute open, UTC | High | Low |
|---|---|---|---|
| TP1 | 10:10 | 4053.210 | 4051.655 |
| TP2 | 10:16 | 4051.420 | 4048.405 |
| TP3 | 11:59 | 4046.665 | 4044.325 |
When the creation timestamp is shared
The five-minute TREND SELL and the fifteen-minute CHoCH SELL carry the same engine, symbol and 09:15 UTC creation timestamp. Their identities differ at the timeframe field, their setups differ, and their event histories are separate. At the observation cutoff the fifteen-minute case had reported TP2, while the five-minute case had a TP3_HIT. A search based only on creation time would risk assigning the target to the wrong plan.
For this audit I joined every event to the entire five-minute signal ID. The creation message gives the reference entry of 4,055.274, the stop of 4,058.351 and the three lower targets. All subsequent events preserve those values. The stop sits 3.077 per troy ounce above entry and TP3 sits 10.293 below it, about 3.35 times the original stop distance. These are distances between the recorded levels.
The activation report sets the replay window
The source reports activation at 10:07:00.175 UTC, 52 minutes and 0.175 seconds after creation. I replayed the retained ranges from that activation minute. Its high of 4,055.780 and low of 4,055.075 bracket the reference entry, but the range supplies no precise fill time or price. The highest high in the replay window was 4,056.170, leaving 2.181 per troy ounce to the original stop.
The 10:10 and 10:16 UTC collector minutes contain the first TP1 and TP2 touches. Separate source reports followed at 10:11:00.176 and 10:17:00.174. The 11:59 minute had a low of 4,044.325, below the 4,044.981 third target. TP3 was reported at 12:00:00.338 UTC, 1 hour, 43 minutes and 0.164 seconds after the TP2 report. The receiver stored TP3 34.858 seconds after its source timestamp. Those clocks describe the recorded sequence. The cause of the delay is unverified.
A different TREND SELL reported a stop
Another five-minute Hazem TREND SELL activated at 10:30:00.205 UTC during this window and later reported STOP_LOSS_HIT at 11:07:00.204 UTC. It had its own creation time and plan. That adverse outcome belongs to its own identity. The two SELLs share underlying market exposure, and the selected TP3 case offers no estimate of how often the TREND setup succeeds.
In the terminal, open the individual setup and compare its creation, activation and target events against the original plan. The dated snapshot keeps the full identities and overlapping records alongside the collector bars, so readers can repeat the comparison after the live terminal changes.
The snapshot preserves 6 other records with overlapping reported active windows on the same symbol. The selection and shared price exposure preclude an overall win rate, a claim of independence or an inference about future profits.
Download the dated JSON evidence and replay inputs →
Use Gold Terminal to compare the original plans, setup identities and reported outcomes →
66 Hazem Signal dossier · Research methodology · Gold trading journal guide · Gold Intelligence · Follow Research Lab