
The call, on record
AMD bullish call
Quoted text as recorded“But I think we're going to have an absolute ripper rally.”
Our interpretation
- Source published
- Aug 25, 2026
- Timeframe
- end of the year and into the first quarter of next year
- Interpreted confidence
- high
- 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
Our summary of the thesis
Strongly BullishStructured interpretation of the video, not a verbatim quotation. Check the source for conditions, emphasis and context.
The host expects an unusually strong AMD rally into year-end and the first quarter of the following year, based on its historical seasonal pattern. He acknowledges near-term uncertainty and that this year's pattern could differ, while maintaining his existing position.
Key arguments
- The host says AMD frequently struggles in late summer and September.
- He identifies mid-November through mid-February as a historically stronger period.
- He considers pessimism about AMD's remaining-year performance excessive.
Counter-arguments acknowledged
- He cannot predict the next two to four weeks.
- AMD could remain weak through fall and winter this year.
- He will not buy call options or increase exposure simply to time seasonality.
Hedges and caveats (from the video)
- Year-end forecasts do not motivate portfolio changes; long-term fundamentals remain the priority.
- AMD's usual seasonal pattern could fail this year, and its next few weeks are unpredictable.
- An RH purchase depends on improved cash reserves and a meaningful market pullback.
- RH's long-term recovery assumes it avoids bankruptcy; the Williams-Sonoma comparison is not a base-case forecast.
- Hims faces recurring negative headlines, possible state penalties, and subscription changes.
- The outcome of Celsius's Rockstar-related leadership dispute is uncertain.
About this record
Not yet reviewed by a moderatorImported analysis · scheduled AI source. A quote, summary and outcome each need their own context. Moderator review does not certify investment performance.
- Source published
- Aug 25, 2026, 12:57 AM UTC
- First recorded by TubeRank
- Oct 6, 2026, 7:59 AM UTC
- Record last updated
- Oct 6, 2026, 8:49 AM UTC
- Moderator review recorded
- Not recorded
- Transcript provenance
- YouTube captions (manual or automatic)
- Recorded analysis processor/source label
- codex-cli-scheduled
- 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 2 shown
Oct 6, 2026, 8:49 AM UTC
missing target
- Outcome methodology version
BeforeNot recorded
After2026-10-06.5
- Recorded outcome date
BeforeNot recorded
After2026-10-06
- Outcome explanation
Before[deadline_review] Deadline requires review (ambiguous_window). Rejected interpreted date: 2027-03-31; no replacement deadline is inferred.
AfterThere is no numerical target that can be objectively scored.
- Outcome reason
BeforeNot recorded
AfterMissing target
Oct 6, 2026, 7:59 AM UTC
source updated
- Recorded analysis processor/source label
Beforeclaude-haiku-4-5-20251001
Aftercodex-cli-scheduled
- Extraction or submission version
BeforeNot recorded
Aftermanual_v1
Showing up to 20 recent changes. The complete feed has 3 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.
Why we interpreted the confidence this way
Base 5 plus 2 for 'going to' gives 7; nearby caveats acknowledge uncertainty without retracting the forecast.