Source Post

Could This Be The Most Controversial Multibagger Stock In The Making?

Aug 8, 2026

The creator discusses the concept of multibagger stocks, referencing Peter Lynch's insights from "One Up on Wall Street." While the episode focuses on a popular and currently overvalued company, the creator aims to make a case for its potential as a multibagger, exploring factors like earnings growth and potential multiple expansion, and contrasting this with the idea of buying during market panics when good companies are cheap.

Linked Mentions

Tickers discussed in this post

INTCNeutralLow ConvictionResearch Only

Intel is mentioned as a reference point for the time and complexity involved in building large fabrication plants.

TSLANeutralLow ConvictionResearch Only

Tesla is mentioned as a potential merger candidate with SpaceX.

RKLBNeutralLow ConvictionResearch Only

Rocket Lab is mentioned as a potential player in the space data center industry with its Neutron rocket, though it's smaller than Starship.

CRWVNeutralMedium ConvictionSignal-backedSecondary

CoreWeave's bare case is not turning a profit, having high interest payments, and not improving margins, which they must show improvement on soon.

ORCLNeutralLow ConvictionResearch Only

Oracle is mentioned as a potential beneficiary of increased compute demand if SpaceX achieves its ambitious revenue targets.

AMZNNeutralLow ConvictionResearch Only

Amazon is mentioned as a hyperscaler with significant cloud revenue and capex, used for comparison with SpaceX.

MSFTNeutralLow ConvictionResearch Only

Microsoft is mentioned in passing as part of the context for discussing SpaceX.

NVDANeutralLow ConvictionResearch Only

Nvidia's Rubin Ultra might use less memory, potentially impacting memory stocks.

NODKNeutralLow ConvictionResearch Only

Nibus is mentioned as a prime example of a company that was not well-known or cared about by the market, and is set to report quarterly figures soon.

Linked Signals

Tracked calls opened from this post

No linked signals were opened directly from this post.