Another great day on the charts today with our plans to buy dips playing out perfectly.
After completing our targets yesterday, we stated that no cross and lock above 2475 confirmed the rejection, which followed with the drop into the lower Goldturns for support bounces. We also stated that we are now back in the range and therefore levels are active again to track the movement up.
We got the drop into 2434 weighted Goldturn, which provided the support for the bounce now into 2459 weighted level. We will now need to see ema5 cross and lock above 2459 to open 2475 once again. Failure to cross and lock above 2459 will follow with a rejection to find support at the lower Goldturns track the movement level to level again.
We will keep the above in mind when taking buys from dips. Our updated levels and weighted levels will allow us to track the movement down and then catch bounces up.
We will continue to buy dips using our support levels taking 30 to 40 pips. As stated before each of our level structures give 20 to 40 pip bounces, which is enough for a nice entry and exit. If you back test the levels we shared every week for the past 24 months, you can see how effectively they were used to trade with or against short/mid term swings and trends.
BULLISH TARGET 2434 - DONE
EMA5 CROSS AND LOCK ABOVE 2434 WILL OPEN THE FOLLOWING BULLISH TARGET 2446 - DONE 2459 - DONE
EMA5 CROSS AND LOCK ABOVE 2459 WILL OPEN THE FOLLOWING BULLISH TARGET 2475 - DONE
BEARISH TARGETS 2421
EMA5 CROSS AND LOCK BELOW 2421 WILL OPEN THE FOLLOWING BEARISH TARGET 2408 2396
EMA5 CROSS AND LOCK BELOW 2396 WILL OPEN THE SWING RANGE
SWING RANGE 2380 - 2360
As always, we will keep you all updated with regular updates throughout the week and how we manage the active ideas and setups. Thank you all for your likes, comments and follows, we really appreciate it!
The information and publications are not meant to be, and do not constitute, financial, investment, trading, or other types of advice or recommendations supplied or endorsed by TradingView. Read more in the Terms of Use.