
The call, on record
UMAC bullish call
Quoted text as recorded“It points to next year the revenue being somewhere between, you know, 250 300 million dollars.”
Our interpretation
- Source published
- Jul 31, 2026
- Timeframe
- next year
- Interpreted confidence
- medium
- Specificity
- specific
Why this call is unscored
- Status
- Not scored
- Notes
- There is no numerical target that can be objectively scored.
Email me when UMAC calls resolve
When a tracked UMAC 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 BullishStructured interpretation of the video, not a verbatim quotation. Check the source for conditions, emphasis and context.
The guest, who discloses his fund owns roughly 3% of the company, argued that Wall Street's revenue estimates for Unusual Machines are dramatically too low, projecting next year's revenue in the $250-300 million range versus consensus of about $60 million. He based this on the company's own guidance that revenue can be predicted from its planned employee headcount growth, tied to strong demand for US-made drone parts amid bans on Chinese drone components.
Key arguments
- Management says employee count is a reliable predictor of revenue, and their targeted headcount implies $250-300M in revenue next year vs. Wall Street's ~$60M estimate.
- Bans on Chinese and other foreign drone parts force US drone makers (e.g., Anduril) to source domestically, benefiting Unusual Machines as an OEM motor supplier.
- Growing military and consumer/commercial drone demand, including potential BVLOS delivery approvals, could expand the addressable market further.
Counter-arguments acknowledged
- Guest acknowledges he is 'talking his book' given his fund's ~3% ownership stake.
Hedges and caveats (from the video)
- Story relies on unconfirmed reports and allegations
- Speculative narrative about market causation
- No specific price targets or directional calls on individual stocks
- Discussion of past events rather than forward predictions
- Margin and leverage risks acknowledged but not quantified
About this record
Not yet 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
- Jul 31, 2026, 12:48 AM UTC
- First recorded by TubeRank
- Jul 31, 2026, 11:18 AM UTC
- Record last updated
- Oct 6, 2026, 6:32 AM UTC
- Moderator review recorded
- Not recorded
- Transcript provenance
- YouTube captions (manual or automatic)
- Recorded analysis processor/source label
- claude-sonnet-5
- 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
Specific revenue range and timeframe given with high conviction ('this is what we think based off what the company's sharing with us'), but it is a revenue forecast rather than a per-share stock price target, and the speaker discloses a financial stake in the company.