The new month of our trade marathon is over. And it's high time to sum up the statistics of our trades. If you closely follow our ideas, you have probably noticed that we haven't published weekly trading statistics for 3 weeks. The fact is that after a series of unprofitable trades, which we wrote about in the previous idea, we reduced the number of trades because we saw that the market is not moving as we forecast.
Trading result of the previous month +1.13% to the deposit. This result looks rather ridiculous, considering that for the previous month we showed a yield of more than 30%.
Though, the main highlight is in the general trading statistics.
So, in a month, starting from 15 March and ending today, we made 20 trades.
Out of 20 trades: profitable - 6 break-even - 1 unprofitable - 12 active - 1
According to statistics, after having 60% of unprofitable trades, the deposit still had a small plus. This fact has tested the strength of our trading strategy. A series of unprofitable trades has been passed. The total result of the trade marathon for 2 months is +33.31%.
The main problem of the last two trading weeks is the transfer of capital to the old altcoins. If last month the new altcoins gave a good increase to our deposit, this month they have significantly failed. However, the timely stop of trading and control of weekly limits on losses allowed to catch the wheel of the turbulent crypto market and prevent large drawdowns of the deposit even today.
In the latest ideas, we described in detail all the trades that have happened in the previous period. But we did not feel that this information is interesting for you.
If we made a mistake and you are interested to see all our trades for the 3 previous weeks with details from us - write about it in the comments. In this case, we will update the idea and describe all our past positions.
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.