@richyang1 Yes but as @BrownMarubozu pointed out to me, dividend of Fairfax is excluded which would skew the outperformance probably to Fairfax rather than Markel (who hasnβt paid dividends).
Did a little work with Claude this morning to compare the Nasdaq with $BRK, $MKL and $FFH. Picked the 1994-2026 period because of the 1994-1999 build up of the Dotcom bubble. Interesting to see that CAGR's are relatively similar although current valuations are hugely different.
@BM_Visser De overduidelijke kortzichtigheid van politici blijft een ontstellend fenomeen om vanaf de zijlijn gade te slaan. Er lijkt geen enkele politicus bereid te zijn om nu pijn te nemen om er later stukken beter voor te staan. Investeren komt niet in het woordenboek voor.
@letuscompound Het is misselijkmakend dat er niet eens geprobeerd wordt dit op een classy manier te doen. Het is zo out in the open, het boeit niemand iets.
This wonβt age well. Feel sorry for the investors who will eventually suffer from flexing index inclusion rules and are going to read this as a case study somewhere in the 2030βs.
Rule changes for the SpaceX $SPCX IPO:
Index providers waived the profitability requirement and cut the seasoning window from 90 days to 5.
This forces over $30 trillion in passive 401k and retirement money to buy SpaceX at IPO valuations.
Bloomberg Intelligence estimates S&P 500 funds must absorb 19% of SpaceX's float within 6 months.
Russell 1000 and Nasdaq 100 funds will absorb 24%.
The rules built to protect passive investors:
1. S&P 500 has required 12 months of trading and 4 quarters of GAAP profitability since 2002. Both waived.
2. Nasdaq cut its inclusion window from 90 trading days to 15.
3. FTSE Russell cut its to 5.
All three benchmarks are now structured to buy SpaceX at IPO pricing.
It is quite disappointing how @Garmin is treating its customer with the 27.09 firmware that seems to break a lot of premium watches like the Forerunner 955. It has been this way for months and there is not a single word on a future firmware fix. Might explore @COROSGlobal instead