The call, on record
LYFT bearish call
Quoted text as recorded“Whimos cooked. Uber's cooked. Lift is cooked.”@ 3:30 · open at this moment on YouTube ↗
Our interpretation
- Source published
- Apr 19, 2026
- 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 LYFT calls resolve
When a tracked LYFT 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
Strongly BearishStructured interpretation of the video, not a verbatim quotation. Check the source for conditions, emphasis and context.
Like Uber, Lyft faces an existential threat from Tesla's robotaxi technology and deployment capabilities.
Key arguments
- Tesla's unsupervised robotaxi technology makes ride-sharing companies obsolete
Hedges and caveats (from the video)
- Speaker expresses personal excitement and uses hyperbolic language ('cooked') rather than measured analysis
- Regulatory approval for steering wheel-less vehicles still pending (2500 unit exemption mentioned)
- Competitive threats from Uber, Lyft, and other autonomous vehicle developers not fully addressed
- Fleet size estimates based on visual observation rather than official Tesla confirmation
- Timeline predictions (end of year Cybercab availability) are speculative
About this record
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
- Apr 19, 2026, 10:36 PM UTC
- First recorded by TubeRank
- Apr 23, 2026, 7:42 PM UTC
- Record last updated
- Oct 6, 2026, 6:32 AM UTC
- Moderator review recorded
- Apr 26, 2026, 9:35 AM UTC
- Transcript provenance
- YouTube captions (manual or automatic)
- Recorded analysis processor/source label
- claude-sonnet-4-20250514
- 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:00 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
- 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
Strong conviction language with definitive statement