The call, on record
LCID bullish call
Quoted text as recorded“if Lucid hits their 18,000 target, that's going to be a pretty good thing, um, overall... I could easily see it going up about 5 to 10% in that day.”@ 4:36 · open at this moment on YouTube ↗
Our interpretation
- Source published
- Jan 4, 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.
The speaker previews Q4 production numbers expected Monday or Tuesday, needing ~10,000 Q4 to hit the 18,000 full-year target. Hitting the target would prompt a 5–10% pop at minimum; missing would be very damaging given the CEO's public comment about producing 1,000 vehicles per week. The speaker expects a volatile week but doesn't see new lows or FOMO unless a major production surprise emerges. The 50-day MA at $14.09 is the critical resistance.
Key arguments
- Q4 production numbers expected Monday or Tuesday — needs ~10,000 to hit 18K target
- CEO Mark publicly said 1,000 vehicles/week — missing would be especially damaging
- 5–10% minimum upside if target is hit; 2–4% downside if missed
- Short interest at 35.52% entering week; close to all-time highs
- CES tech/AI rally could provide positive tailwind for speculative growth stocks
- Lucid not meaningfully participating in CES — only one speaker (Claudia Gast)
Counter-arguments acknowledged
- If Lucid somehow delivers 20,000+ it would be a genuine surprise squeeze catalyst
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 4, 2026, 12:06 AM 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.