The call, on record
LCID bearish call
Quoted text as recorded“I still do feel that just mathematically it's not there for them to hit that 20,000. So I feel like Mark might kind of cut it a little bit which of course the stock price will be impacted by that.”@ 10:27 · open at this moment on YouTube ↗
Our interpretation
- Source published
- Aug 3, 2025
- 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 LCID calls resolve
When a tracked LCID 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
MixedStructured interpretation of the video, not a verbatim quotation. Check the source for conditions, emphasis and context.
The speaker provides a comprehensive Q2 earnings preview noting the implied move is 11.42%, the key variables are guidance reiteration, reverse stock split justification, Uber deal elaboration, and potential new partnership. He believes Mark will announce another partnership but doubts 20K production guidance can be maintained — expecting 16-18K is more realistic — and warns that a guidance cut would be very negative for the stock.
Key arguments
- Implied earnings move 11.42% — ~30 cent move expected in either direction
- Speaker expects another partnership announcement beyond Uber
- 260 and 207 are the strong support/resistance points post-earnings
- Reverse stock split rationale is weak — institutions don't avoid Lucid because of penny stock status
- Canada tariffs just increased to 35% — will impact margins more than guided
- Mark overhyped earnings with 'pleasant surprises' on Bloomberg — expectations are high
Counter-arguments acknowledged
- 8 of 9 analyst EPS estimates are positive revisions — bar is set low
- Stochastic RSI very oversold — upside potential if guidance holds
About this record
Reviewed by a moderatorSubmitted record. A quote, summary and outcome each need their own context. Moderator review does not certify investment performance.
- Source published
- Aug 3, 2025, 1:15 PM UTC
- First recorded by TubeRank
- Apr 20, 2026, 5:33 PM UTC
- Record last updated
- Oct 6, 2026, 6:32 AM UTC
- Moderator review recorded
- Apr 26, 2026, 9:32 AM UTC
- Transcript provenance
- YouTube captions (manual or automatic)
- Recorded analysis processor/source label
- manual_claude_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: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
- Reference price
Before24.1
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.