Alexander_Nikitin

GBPAUD. unified gartley

Long
Alexander_Nikitin Mis à jour   
FX:GBPAUD   Livre sterling / Dollar australien
A potential unified gartley is setting up.
Trade plan: enter long@1.82473 with sl @1.80718(58.5 pips) and tp @1.81303(117 pips).

Statistics:
Over the past 12 (2007 is the first available date) years a pattern with these B-point and C-point ratios appears 8 times on GBPAUD,30M if the swings are identified with prex(6) algorithm. The best expectancy of 0.5915 of the Risk is acheived if the entry is placed @0.7XA (limit order), stoploss is placed @0.9XA and target is twice greater than risk distance. Historically average RR ratio is 2.18, the probability of win is 50.0%

Comment below if you think it is a good idea to share statistics of a pattern in description. Let me know if I am to do it in future:)
Transaction en cours:
orders executed. 50% to hit the target based on stats:)
Trade fermée: ordre d’arrêt atteint:
It's been a 50% setup. We had 8 in historical collection, now we have nine. This one changes the statistics:
If traded the way explained on the chart there's a 44.44% probability to hit tp with an average RR of 1.92. Now expectancy becomes lower (0.2967R) which is still worth trading. But the probability of win is low to my taste...
Good news is that there's one more profitable way of trading it: entry @0.8xa, stoploss @1.1xa and target twice greater than risk distance. In this case historically there's a 50% probability to hit tp with average RR of 2.13 and math expectancy of 0.5664 of R. Good luck
Transaction en cours:
Re-enter based on the second variation.
Commentaire:
Here's the screenshot with trade levels: prntscr.com/oxpk0j
Commentaire:
Here's the statistics file for GBPAUD, 30M: prntscr.com/oy69i6

Clause de non-responsabilité

Les informations et les publications ne sont pas destinées à être, et ne constituent pas, des conseils ou des recommandations en matière de finance, d'investissement, de trading ou d'autres types de conseils fournis ou approuvés par TradingView. Pour en savoir plus, consultez les Conditions d'utilisation.