Updates for my Portfolio for February 2022
I wanted to post this much earlier but similar as my last update due to various circumstances in life, I didn't find much time until recently.
For my side project, it is placed in hiatus until further notice as the place I am working on it is undergoing major works.
That being said, I am kinda screwed where due to new iBanking changes on many banks, transfer limits require 24h to take effect. I prefer to dynamically change my limits as required. I also selected the iBanking platform where it is not very possible to change other settings using the app, plus other measures within the iBanking settings to alert me of any issues in my bank account. But I guess I can only workaround these new measures, however as annoying and less useful they are (my previous settings in iBanking are even more tighter, less the waiting time).
Sad to say because of the above works and the new measures, I missed deploying 2 tranches before the HK market ran up as I wasn't able to fund my account in time. It really sucks there.
Sad to say because of the above works and the new measures, I missed deploying 2 tranches before the HK market ran up as I wasn't able to fund my account in time. It really sucks there.
- Buy Adobe at 466.79
- Buy Tencent at 430
- Reasons/Notes
- Just adding to my current positions.
- I would point out that the amount of Adobe purchased is rather small (I was afraid of running out of cash), looking to add more as prices fall.
- I added Tencent at 430 was a mistake as I was supposed to queue at about ~390 (last entry was 430). I kinda queued a GTC order and totally forgot about it.
That's all for my money for now.
I have place a small % of my net worth in crypto-assets.
Conclusion
My portfolio YTD is now -36.09%, with the long term XIRR at 8.69%, pretty much the same as VT's performance. The HK shares is really being badly hit due to what China is doing to their tech giants.
My cash position is currently at about 6%. Have to wait for cash position to accumulate while waiting.
No comments:
Post a Comment