TubeRank
Quoted text as recorded“We got to break that, get above it, and hold it, and then confirm, and then we should run.”
Our interpretation
- Source published
- Sep 28, 2026
- Interpreted confidence
- low
- Specificity
- vague
Why this call is unscored
- Status
- Not scored
- Notes
- There is no numerical target that can be objectively scored.
Email me when XRP calls resolve
When a tracked XRP 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.
The host interprets XRP's pullback after breaking above the Bollinger Band as a normal release of overheating. He expects a late-October advance, with a confirmed break above the weekly 50 EMA supporting that outlook.
Key arguments
- The pullback reached the 13 EMA, consistent with his stated pattern following repeated Bollinger Band breaks.
- Trading between the daily 13 and 50 EMAs does not yet make him nervous.
- The weekly chart is retesting the 50 EMA, while the five-period moving average is rising.
Counter-arguments acknowledged
- XRP could retest the daily 50 EMA before advancing.
- A confirmed break below the daily 50 EMA would warrant a different response.
- The weekly 50 EMA remains resistance that must be overcome.
Hedges and caveats (from the video)
- A confirmed XRP breakdown below the daily 50 EMA would change his assessment and prompt action.
- XRP must break above and hold its weekly 50 EMA to confirm the anticipated advance.
- The XRP advance could begin earlier than his late-October estimate.
- HYPE could decline to its 50 EMA if support fails.
- The promoted algorithm's historical backtesting does not guarantee future performance; the host explicitly says he does not know whether it will outperform.
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
- Sep 28, 2026, 9:04 PM UTC
- First recorded by TubeRank
- Oct 6, 2026, 6:51 AM UTC
- Record last updated
- Oct 6, 2026, 8:49 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 2 shown
Oct 6, 2026, 8:49 AM UTC
missing target
- Outcome methodology version
BeforeNot recorded
After2026-10-06.5
- Reference price
Before1.518358
AfterNot recorded
- Reference observation time
Before2026-09-27T23:59:59.999+00:00
AfterNot recorded
- Reference price source
Beforeyahoo_daily_crypto
AfterNot recorded
- 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
Oct 6, 2026, 6:51 AM UTC
source updated
- Recorded analysis processor/source label
BeforeNot recorded
Aftercodex-cli-scheduled
- Extraction or submission version
BeforeNot recorded
Aftermanual_v1
Showing up to 20 recent changes. The complete feed has 3 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 advance depends on breaking, holding, and confirming above the weekly 50 EMA. The conditional requirement reduces the base conviction score from 5 to 3.