The call, on record
LCID bullish call
Quoted text as recorded“if Lucid hits their 18,000 target, I could easily see it going up about 5 to 10% in that day. Um at the very bare minimum.”@ 7:31 · open at this moment on YouTube ↗
Our interpretation
- Source published
- Jan 1, 2026
- Interpreted confidence
- medium
- Specificity
- vague
Why this call is unscored
- Status
- Not scored: condition
- Notes
- The claim contains a condition. Its trigger has not been verified, so price alone cannot establish an outcome.
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
NeutralStructured interpretation of the video, not a verbatim quotation. Check the source for conditions, emphasis and context.
A New Year's Day preview of Q4 expectations for Lucid and Rivian. Lucid is down 65% for 2025. The speaker believes Lucid will hit its 18,000 production target but notes the persistent problem of deliveries lagging production (a pattern since 2022). Hitting the number would be a 5–10% pop, while missing would cause a 2–4% red day. 2026 guidance for ~40,000 units is what Wall Street will really be watching for.
Key arguments
- Lucid down 65% in 2025 vs Rivian up 48%, Tesla up 11%, S&P up 16%
- Q4 numbers expected early January; needs ~10,000 production for 18,000 full-year target
- Delivery-production gap is a persistent pattern (2022-2025) — market will scrutinize
- 5–10% pop if target hit; 2–4% red if missed
- 2026 targets (ideally ~40,000) and guidance will be the real market mover
- Speaker expects Rivian to fall slightly short at ~40,000 deliveries
Counter-arguments acknowledged
- CEO saying 1,000 vehicles per week should make 18K achievable
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
- Jan 1, 2026, 9:46 PM UTC
- First recorded by TubeRank
- Apr 20, 2026, 5:21 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
- unverified_condition
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
unverified condition
- Outcome methodology version
BeforeNot recorded
After2026-10-06.1
- Reference price
Before11.15
AfterNot recorded
- Recorded outcome date
BeforeNot recorded
After2026-10-06
- Outcome explanation
BeforeNot recorded
AfterThe claim contains a condition. Its trigger has not been verified, so price alone cannot establish an outcome.
- Outcome reason
BeforeNot recorded
AfterUnverified condition
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
The claim contains a condition. Its trigger has not been verified, so price alone cannot establish an outcome.
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.