I recently published the March edition of my DivGro 2.0 newsletter. You'll need to sign up to read, but all current content will be free until I formally launch DivGro 2.0 on 1 May 2023.
In this edition, I review my DivGro portfolio as of 28 February 2023 and present several top 10 lists of Dividend Radar stocks.
In February, I added shares to three existing positions, reduced one position, and closed two positions. Thirteen DivGro stocks announced dividend increases in February, and two stocks paid higher dividends due to exchange rate fluctuations. Another stock executed at a 3-for-2 stock and announced a small dividend increase on a split-adjusted basis. One of my holdings announced a significant dividend cut.
As a result of these transactions, DivGro's projected monthly dividend income decreased by $4 to $3,864, but that's a year-over-year increase of 15.3%.
The top 10 lists present Dividend Radar stocks that pass various screens and trade at discounted valuations:
- Highest Quality Scores (quality scores of 21-30)
- Highest Dividend Quality Grades (A+ only)
- Very Safe Dividend Safety Scores
- High Forward Dividend Yields (≥ 4%)
- High Dividend Growth Rates (≥ 10%)
- High Total Returns (≥ 10%)
- Best Income Prospects (≥ 4%)
- Best Growth Prospects (favorable Adjusted Chowder Numbers)
The site is still very much in progress, and I'm working hard on adding more content in preparation for the launch.
After 1 May 2023, some pages that are now tagged Members Only will become Paid Members Only. Monthly newsletters and my Portfolio page will be available to subscribers only. DivGro 2.0 will always contain free content as well, such as this article on How to Assess Dividend Quality.
I'm planning at least two subscription tiers, one for dividend growth investors and an add-on for subscribers interested in options trading.
No comments:
Post a Comment
Please don't include links in comments. I will mark such comments as spam and the comment won't be published. To make me aware of your blog or website, comment on my Blogrole page instead.