TubeRankThe call, on record
US10Y bearish call
Quoted text as recorded“The 10-year Treasury has hockey stick just in the last two weeks, three weeks from 4.9 to like 5.27, which is what I'm calling peak. I could be wrong about that.”
Our interpretation
- Source published
- Oct 2, 2026
- Timeframe
- Current yield peak; no explicit future deadline
- 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 US10Y calls resolve
When a tracked US10Y 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
BearishStructured interpretation of the video, not a verbatim quotation. Check the source for conditions, emphasis and context.
The host identifies the recent Treasury yield level around 5.27% as a potential peak. His view implies limited further upside in yields, although he expressly acknowledges uncertainty.
Key arguments
- He describes a rapid rise from approximately 4.9% to 5.27% over two to three weeks.
- He expects an Iran agreement to reduce broader interest rates.
Counter-arguments acknowledged
- He explicitly says his peak assessment could be wrong.
Hedges and caveats (from the video)
- The host explicitly acknowledges that his assessment of a peak in Treasury yields could be wrong.
- An AI trade collapse would severely damage the broader economy.
- Higher borrowing costs could cause weaker, CCC-rated companies to fail.
- A sharp equity decline could hurt the economy through a reversal of the wealth effect.
- Private credit could become a significant problem if the entire sector rolls over.
- He favors reducing debt as a hedge.
About this record
Not yet reviewed by a moderatorImported analysis · scheduled AI source. A quote, summary and outcome each need their own context. Moderator review does not certify investment performance.
- Source published
- Oct 2, 2026, 9:25 PM UTC
- First recorded by TubeRank
- Oct 3, 2026, 1:39 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
- codex-cli-scheduled
- 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:01 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
The base calibration score is 5, with no specified lexical adjustment. Calling a peak conveys directional conviction, but the explicit admission of uncertainty limits confidence.