TubeRank
Quoted text as recorded“I think you know it's probably sometime next year where we're going to see kind of the rapid roll out you know across many city not just many cities but without uh the Tesla monitor in the car”@ 35:26 · open at this moment on YouTube ↗
Our interpretation
- Source published
- Jun 23, 2025
- Timeframe
- sometime next year
- Extracted deadline
- Dec 31, 2026
- Interpreted confidence
- medium
- Specificity
- specific
Why this call is unscored
- Status
- Not scored
- Notes
- There is no numerical target that can be objectively scored.
Email me when TSLA calls resolve
When a tracked TSLA 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 reports five smooth robotaxi rides without interventions and believes Tesla has assembled the core elements of a competitive ride-hailing service. He is bullish on scaling in 2026 but expects safety improvements and removal of the in-car monitor to determine the pace.
Key arguments
- All five rides were smooth and required no interventions from the monitor or passenger.
- The service uses a standard Model Y without special external equipment.
- The app and in-car experience are convenient and largely polished.
- The vehicle handled a tight parking lot through a multi-point maneuver.
- More vehicles could shorten pickup times, while competitive pricing could support market-share gains.
- Launching with monitors allows Tesla to learn from real operations and resolve service issues.
Counter-arguments acknowledged
- The host does not yet feel fully confident sleeping in a vehicle running his current FSD version.
- The actual robotaxi software version and its relative capabilities remain unknown.
- An in-car monitor limits the scalability of a fully driverless service.
- Drop-off locations can require walking or crossing the street.
- Limited fleet size can produce longer waits.
- Safety edge cases and safeguards against passenger interference remain works in progress.
Hedges and caveats (from the video)
- Five successful rides provide a limited sample of the service's safety and reliability.
- The robotaxi software version and its improvement over the host's FSD 13.2.9 are unknown.
- Removing the in-car monitor is a major scaling bottleneck.
- Pickup and drop-off locations, fleet availability, and customer controls still need refinement.
- Remote monitoring and takeover capabilities are speculative and unconfirmed.
- The description discloses a long TSLA position and states that the content is personal opinion rather than professional financial advice.
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
- Jun 23, 2025, 1:24 AM UTC
- First recorded by TubeRank
- Oct 6, 2026, 8:34 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
- Reference price
Before322.16
AfterNot recorded
- Reference observation time
Before2025-06-20T23:59:59.999+00:00
AfterNot recorded
- Reference price source
Beforeyahoo_daily
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
Oct 6, 2026, 8:34 AM UTC
source updated
- Recorded analysis processor/source label
BeforeNot recorded
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
- Dec 31, 2026
- 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
The base score of 5 plus 'going to' and minus the description's disclaimer yields 6. 'I think' and 'probably' further indicate a tentative forecast rather than certainty.