Updated - Tron (TRX) - Elliott Wave Count and Prediction - 4hr
I'm making a slight adjustment to my Tron (TRX) EWT count.
It appears TRX isn't waiting around for a slightly deeper pullback to complete (2), so it's highly probable we are now in a (3) of W3 which will give us a fantastic run-up in the next week or so. Notice the red vertical time cycle lines and the beautiful symmetry between the subwaves of W1. This supports the wave count further and I can find no alternate count nearly as probable as this. The subwaves of W1 peaked around 17 day increments. Using this symmetry puts us at January 27th (+/- 24hr) for the next noteworthy pullback. At which time, wave (3) of W3 should complete. Then we will consolidate for a wave (4) of W3.
Please feel free to comment and/or make suggestions on how to improve my wave counts.
I love wave counting the markets and am in awe of their beauty, but *NOTE* I am not an investment advisor and am not offering investment advice.
It appears TRX isn't waiting around for a slightly deeper pullback to complete (2), so it's highly probable we are now in a (3) of W3 which will give us a fantastic run-up in the next week or so. Notice the red vertical time cycle lines and the beautiful symmetry between the subwaves of W1. This supports the wave count further and I can find no alternate count nearly as probable as this. The subwaves of W1 peaked around 17 day increments. Using this symmetry puts us at January 27th (+/- 24hr) for the next noteworthy pullback. At which time, wave (3) of W3 should complete. Then we will consolidate for a wave (4) of W3.
Please feel free to comment and/or make suggestions on how to improve my wave counts.
I love wave counting the markets and am in awe of their beauty, but *NOTE* I am not an investment advisor and am not offering investment advice.
Related publications
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.