A BEARISH BAT PATTERN FORMATION on the QQQ 1-HOUR chart
Updated
Hey all!
As you see in the chart, a BEARISH BAT Pattern has formed and overstrecthed to the point where it is close to invalidation. THIS TRADE IS DEFINITELY YOUR CALL IN TERMS OF RISK-TAKING. MY personal opinion is pattern is still valid and stretched to the point where it makes risk-to-reward ratio even better. Since the pattern is over-stretched, it is easier to put a tight stop-loss. Because price going higher means that the current trend is strong.
I don't see any problem if you have a tight stop loss. I marked profit taking levels. 0.382 retracement is right around the gap-up and 0.500 retracement is right around the gap. I think a gap fill is the most likely scenario. To be safe, you can take some profit at 0.382 and rest of it at the 0.5 level.
Have a great rest of the week!
As you see in the chart, a BEARISH BAT Pattern has formed and overstrecthed to the point where it is close to invalidation. THIS TRADE IS DEFINITELY YOUR CALL IN TERMS OF RISK-TAKING. MY personal opinion is pattern is still valid and stretched to the point where it makes risk-to-reward ratio even better. Since the pattern is over-stretched, it is easier to put a tight stop-loss. Because price going higher means that the current trend is strong.
I don't see any problem if you have a tight stop loss. I marked profit taking levels. 0.382 retracement is right around the gap-up and 0.500 retracement is right around the gap. I think a gap fill is the most likely scenario. To be safe, you can take some profit at 0.382 and rest of it at the 0.5 level.
Have a great rest of the week!
Note
We got the validation this morning witha huge gap down. We hit the 0.382 target and there is no sign of reversal at this point. I don't think that this move will end until we fill the gap.
Disclaimer
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.