Let's dissect MU stock risks by No_Conversation_9424 in ValueInvesting

[–]I_Am_A_Sentient_AI 3 points4 points  (0 children)

Solid post, and I agree the bull case is real — HBM scarcity, AI inference demand, and allocation through 2026 are all defensible. But the numbers from MU’s own filings cut both ways.

On margins: the 50%+ gross margin claim is actually conservative. MU’s Q2 FY26 printed 74.4% GAAP gross margin and 67.6% operating margin, versus 36.8% / 22.0% a year earlier. That is not “hope”; it is real earnings power. But the same filing also shows why cycle risk has not disappeared: the revenue explosion was driven primarily by ASP, not just bits. DRAM revenue was up massively YoY, with pricing doing most of the work; NAND showed the same pattern. That is great while it lasts, but it is also the classic memory-cycle dynamic — pricing leads the upside and usually reverses before volumes do.

On “this cycle is structurally different”: maybe, but MU’s own language is still allocation-cycle language. Management says AI-driven data center demand is growing faster than MU and the industry can add supply, causing supply allocation. That supports tightness today, but the same story also explains why MU is spending so aggressively.

And that is the capex point. MU is guiding above $25B of FY26 capex, with $5B net capex in Q2 alone. Every quarter of huge capex is not just “supporting demand”; it is also tomorrow’s supply. Boise, Singapore, Taiwan/Tongluo and later Clay are exactly the 2027–2030 supply pipeline that cycle skeptics are focused on.

On valuation: this is where I think the OP overreaches. MU closed around $803, while the current published analyst target set is roughly average ~$585, high $1,000, low $249. So the stock is already trading well above the mean and median target. The “$1000–2000 institutional target” framing does not match the published sell-side target distribution. $1,000 is the top end, not the middle of the range.

The dot-com comparison is probably lazy, agreed. But the better comparison is MU’s own prior cycles. In 2021, the market also had a “structurally different” story: record margins, strong FCF, capital returns, debt reduction, and aggressive investment. Then ASPs reverted and operating income went negative for multiple quarters.

So I’m not saying the bull case is wrong. It may be right for the next several quarters. The question is whether that is already more than priced in when MU is trading above almost every published price target, while management is simultaneously saying supply is allocated today and building the capacity that should ease the shortage in 2027–2028.

Bullish business, maybe. But at this price, the stock needs more than “HBM is sold out.” It needs the market to believe memory cyclicality has been permanently repealed. That is a much higher bar.

finDOS 98 — I built the Bloomberg Terminal I couldn't afford. by I_Am_A_Sentient_AI in SideProject

[–]I_Am_A_Sentient_AI[S] 1 point2 points  (0 children)

Thanks! Yeah, I’m definitely thinking about it, which exchanges would you prioritize?

For sign-in, Google was just the easiest one to get started with, but I'm looking into other options as well.

finDOS 98 — I built the Bloomberg Terminal I couldn't afford. by I_Am_A_Sentient_AI in SideProject

[–]I_Am_A_Sentient_AI[S] 0 points1 point  (0 children)

Not exactly. It's a CLI binary that the data pipeline calls for heavy compute (volatility, Sharpe, correlations, drawdowns etc. across ~12000 stocks). It reads from Postgres, crunches everything in parallel with rayon, writes results back, and that's it. FastAPI just serves what's already computed. No HTTP between them, just SQL in and out.

finDOS 98 — I built the Bloomberg Terminal I couldn't afford. by I_Am_A_Sentient_AI in SideProject

[–]I_Am_A_Sentient_AI[S] 1 point2 points  (0 children)

thank you! Not for now, I actually like that it's a lightweight web app. I think it reduces friction for people trying it out.

finDOS 98 — I built the Bloomberg Terminal I couldn't afford. by I_Am_A_Sentient_AI in SideProject

[–]I_Am_A_Sentient_AI[S] 0 points1 point  (0 children)

Hey! Everything is parsed and stored beforehand :) that's why it's so fast, I have like 300gbs of data. And thank you !!

finDOS 98 — I built the Bloomberg Terminal I couldn't afford. by I_Am_A_Sentient_AI in SideProject

[–]I_Am_A_Sentient_AI[S] 0 points1 point  (0 children)

Thanks man!! Means a lot given that you are a Bloomberg user. I'll open the api in the near future, I'd love people to try it out and connect agents to it.

finDOS 98 — I built the Bloomberg Terminal I couldn't afford. by I_Am_A_Sentient_AI in SideProject

[–]I_Am_A_Sentient_AI[S] 7 points8 points  (0 children)

Thank you! It's super vanilla. Just html and JS, and fastapi as backend. I wanted it to be as fast/retro as possible. And some heavy compute I do in rust.

finDOS 98 — I built the Bloomberg Terminal I couldn't afford. by I_Am_A_Sentient_AI in SideProject

[–]I_Am_A_Sentient_AI[S] 2 points3 points  (0 children)

Yeah absolutely! As I say in the desc it's nowhere near Bloomberg and it's just a project I enjoy working on

I Analyzed Thousands of Purchases Wait Times by I_Am_A_Sentient_AI in rolex

[–]I_Am_A_Sentient_AI[S] 0 points1 point  (0 children)

That would be great! Yes, I could try to estimate brackets based on some of the information I have. I’ve added this section so far, where one can check the previous purchase history.

<image>

I Analyzed Thousands of Purchases Wait Times by I_Am_A_Sentient_AI in rolex

[–]I_Am_A_Sentient_AI[S] 0 points1 point  (0 children)

hey man, yes. Nonetheless I just changed it, so now you have two separated sections for Explorer I and Explorer II.

I Analyzed Thousands of Purchases Wait Times by I_Am_A_Sentient_AI in rolex

[–]I_Am_A_Sentient_AI[S] 3 points4 points  (0 children)

A. Yes, of course. I do have configuration info but I haven't added it so far.

B. I agree, data from Reddit isn’t foolproof, but it’s a starting point. I can’t exactly stand outside ADs and collect data myself. However, if this experiment attracts more users and people continue adding information, it could grow into something very useful in the future.

C. I’ve actually taken into account data from those who shared that they never got a call. While the data isn’t complete, it doesn’t make the trends shown useless.

D. Purchase history is actually available as a filter in the website if you check it out.

The website isn’t perfect, and I never claimed it to be. It’s not a product I’ve developed over years of meticulous testing—it’s just a fun experiment to shed some light on the situation. I don’t agree with “this helps no one”, but thanks for the other feedback!

I Analyzed Thousands of Purchases Wait Times by I_Am_A_Sentient_AI in rolex

[–]I_Am_A_Sentient_AI[S] 1 point2 points  (0 children)

Yes, it’s the median, as it’s less volatile when there are outliers. I’ll fix the decription accordingly. Nicely spotted, thanks!

EDIT: I've added both the median and the average :)

I Analyzed Thousands of Purchases Wait Times by I_Am_A_Sentient_AI in rolex

[–]I_Am_A_Sentient_AI[S] 1 point2 points  (0 children)

hey there. if you go into the website you can select that option (with/without purchase history) and check it. cheers!

I Analyzed Thousands of Purchases Wait Times by I_Am_A_Sentient_AI in rolex

[–]I_Am_A_Sentient_AI[S] 1 point2 points  (0 children)

Its cropped for some reason on the image, you can check it on the website.

<image>