The call, on record
ORCL bullish call
Quoted text as recorded“Yes, Oracle has probably bottomed.”
Our interpretation
- Source published
- Sep 22, 2026
- Interpreted confidence
- low
- Specificity
- vague
Why this call is unscored
- Status
- Not scored
- Notes
- There is no numerical target that can be objectively scored.
Email me when ORCL calls resolve
When a tracked ORCL 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
BullishStructured interpretation of the video, not a verbatim quotation. Check the source for conditions, emphasis and context.
Kevin briefly suggests Oracle has likely bottomed as part of the broader hardware/AI infrastructure recovery narrative.
Key arguments
- Oracle is cited as an example of a hardware-adjacent stock that has 'probably bottomed'
Hedges and caveats (from the video)
- Goldman Sachs framing these as 'headwinds' rather than bearish calls
- Analysis based on forward-looking depreciation estimates that may not materialize as predicted
- Host acknowledges earnings valuations are 'in line with 10-year average' on forward P/E basis
- Discussion of GPU price appreciation as unsustainable suggests speculative asset valuations
- Commentary focuses on 2027 specifically, implying near-term (12-month) caution rather than long-term bearishness
About this record
Not yet reviewed by a moderatorAI-extracted record. A quote, summary and outcome each need their own context. Moderator review does not certify investment performance.
- Source published
- Sep 22, 2026, 7:01 PM UTC
- First recorded by TubeRank
- Sep 22, 2026, 7:19 PM 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
- claude-sonnet-5
- This can identify a workflow rather than an exact AI model version.
- Extraction pipeline version
- v1.0.0
- 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
Before148.56
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.
Why we interpreted the confidence this way
Hedge word 'probably' and lack of specifics keep confidence low despite clear directional lean.