The call, on record
LCID bearish call
Quoted text as recorded“If they come out and just say, 'Hey, you know what? We're targeting about 25,000 for 2026.' Like Lucid Stock is going to get hit.”
Our interpretation
- Source published
- Feb 13, 2026
- Extracted deadline
- Feb 24, 2026
- Interpreted confidence
- medium
- Specificity
- specific
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
BullishStructured interpretation of the video, not a verbatim quotation. Check the source for conditions, emphasis and context.
Lucid is up 6.3% largely riding Rivian's 25% post-earnings surge, which itself came from a triple beat with strong 2026 guidance. The speaker says Lucid's own upcoming earnings hinge entirely on 2026 guidance — if Lucid says 25,000 units, the stock gets hit; they need to be aggressive. The Gravity delivery halt for a seat component issue was a brief negative, but the stock's current momentum above the 10-day moving average is encouraging. Big money is buying on the secondary market.
Key arguments
- Lucid up 6.3% on Rivian's earnings momentum, showing correlation between the two stocks
- Earnings guidance will be decisive — low targets like 25K would be seen as bearish
- Two large institutional buys ($1.3M and $696K) on secondary market
- Gravity delivery halt for seat component fixed with new SVP of Supply Chain hire
- Shorts have been stagnant for a week, not increasing significantly
Counter-arguments acknowledged
- Gravity delivery halt for seat component signals ongoing quality control issues
- Q4 EPS consensus is -$2.67, still deeply unprofitable
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
- Feb 13, 2026, 5:32 PM UTC
- First recorded by TubeRank
- Apr 20, 2026, 5:20 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
Before10.28
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
- Feb 24, 2026
- 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.