DivGro is now DivGro 2.0!

DivGro moved to another platform and is now DivGro 2.0!

Please enjoy complimentary access to all the content on DivGro 2.0 until I formally launch it! You can sign up for free and join more than 1,600 existing members!

Complimentary access includes my monthly newsletter and articles like
 How to Assess Dividend Quality and The Chowder Ruleand a live spreadsheet of my DivGro Portfolio.

Read more About DivGro 2.0 ...

Wednesday, July 16, 2025

July 2025 Newsletter

Welcome to the JULY edition of my DivGro 2.0 newsletter!

After a brief market recap, I provide an overview of my DivGro portfolio (as of June 30, 2025), along with a list of all transactions that impacted DivGro's projected annual dividend income.

In June, I added shares to one position and trimmed another, so DivGro still contains 77 positions. Of these, 68 are dividend growth [DG] stocks, 3 are dividend-paying stocks, and 4 are closed-end funds. By convention, I label stocks with dividend increase streaks of five or more years as DG stocks.

This year, I'm consolidating my DivGro portfolio in preparation for converting our IRAs to Roth IRAs later this year. To the extent possible, we aim to hold high-growth, low-yielding stocks in Roth IRAs, where significant gains won't be taxed. Likewise, we aim to hold high-yielding stocks in taxable brokerage accounts, where qualified dividends are taxed at lower capital gains tax rates.

Please read my July 2025 Newsletter at DivGro 2.0!


More than 1,500 members have joined DivGro 2.0 since its soft launch in February 2023. I have decided to delay the formal launch of DivGro 2.0, allowing members to continue with complimentary access to all content on DivGro 2.0, including my DivGro Portfolio

Thanks for Reading!
You can follow me on TwitterFacebookSeeking Alpha, and TalkMarkets

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.