TubeRank
The call, on record
AMD bearish call
Quoted text as recorded“the CPU trade, in my opinion, is overblown”
Our interpretation
- Source published
- Sep 30, 2026
- Timeframe
- longer term
- Interpreted confidence
- medium
- Specificity
- vague
Why this call is unscored
- Status
- Not scored
- Notes
- There is no numerical target that can be objectively scored.
Email me when AMD calls resolve
When a tracked AMD call is scored — hit, miss or partial — we’ll email you the result. No account needed.
Used only for these updates. Privacy
Evidence and source
Our summary of the thesis
BearishStructured interpretation of the video, not a verbatim quotation. Check the source for conditions, emphasis and context.
AMD's move through the mid-400s to about 645 is overbought, and he thinks the agent-CPU demand story is a rounding error versus frontier chips.
Key arguments
- One high-core AMD CPU could serve hundreds of agents.
- Nvidia's quarterly data-center sales dwarf the CPU revenue he models for a billion agents.
Hedges and caveats (from the video)
- Short-term direction depends on an Iran deal.
- He still calls AMD a good company and the frontier-chip trade the real one.
About this record
Not yet reviewed by a moderatorSubmitted record. A quote, summary and outcome each need their own context. Moderator review does not certify investment performance.
- Source published
- Sep 30, 2026, 12:23 AM UTC
- First recorded by TubeRank
- Sep 30, 2026, 3:38 AM UTC
- Record last updated
- Oct 6, 2026, 6:32 AM UTC
- Moderator review recorded
- Not recorded
- Transcript provenance
- YouTube captions (manual or automatic)
- Recorded analysis processor/source label
- grok-session
- This can identify a workflow rather than an exact AI model version.
- Submission path version
- manual_v1
- Identifies the precomputed submission path. It does not identify an AI model version or imply human authorship.
- Outcome methodology version
- 2026-10-06.5
- Outcome reason code
- missing_target
Recent record changes 4 shown
Oct 6, 2026, 6:32 AM UTC
corrected
- Outcome methodology version
Before2026-10-06.4
After2026-10-06.5
Oct 6, 2026, 5:14 AM UTC
corrected
- Outcome methodology version
Before2026-10-06.2
After2026-10-06.4
Oct 6, 2026, 4:01 AM UTC
corrected
- Outcome methodology version
Before2026-10-06.1
After2026-10-06.2
Oct 6, 2026, 3:27 AM UTC
missing target
- Outcome methodology version
BeforeNot recorded
After2026-10-06.1
- Reference price
Before607.87
AfterNot recorded
- Recorded outcome date
BeforeNot recorded
After2026-10-06
- Outcome explanation
BeforeNot recorded
AfterThere is no numerical target that can be objectively scored.
- Outcome reason
BeforeNot recorded
AfterMissing target
Showing up to 20 recent changes. The complete feed has 5 recorded events for this call, including its initial entry. Read the full paginated history (JSON); follow nextCursor while hasMore is true.
Stored outcome evidence
- Stored reference price
- Not recorded
- Not recorded · provider not recorded
- Target as extracted
- Not recorded
- Stated deadline as extracted
- None recorded
- Recorded outcome date
- Oct 6, 2026
- Outcome price observation
- Not recorded
- Not recorded · provider not recorded
Stored explanation
There is no numerical target that can be objectively scored.
Missing timestamps, providers and versions are historical gaps. Stored observations can include daily closes; they do not show every intraday touch or prove an executable trade. Read the methodology.