Breakout Signal

Channel profile · tracked by Breakout Signal

1.234.567 Dragon Ball

28,100 subscribers ·publishing in English / Global ·Gaming / Anime

5tracked breakouts
1.3×best breakout score
23.7×best reach, views per subscriber
2.3Mtotal views tracked
21.1×median reach, tracked videos

Breakout videos

  1. 01

    LEGEND 2: A Dragon Ball Tale (2026) | Live-Action AI Film (Fan-made)

    🎮 Gaming / Anime ·666.5K views · 4.6K/day ·23.7× its audience · 12:18 ·2026-05-03 · English / Global

    1.3×
  2. 02

    Dragon Ball Super: The AI Movie (2026) | Ultimate Cinematic Collection (Fan-made)

    🎮 Gaming / Anime ·598.5K views · 3.6K/day ·21.1× its audience · 47:43 ·2026-04-13 · English / Global

    1.2×
  3. 03

    Dragon Ball: AI Evolution (2026) | The Ultimate Collection (Fan-made)

    🎮 Gaming / Anime ·609.6K views · 2.9K/day ·21.7× its audience · 1:01:50 ·2026-03-02 · English / Global

    1.0×
  4. 04

    Buu vs Moro | Dragon Ball The Galactic Patrol Live Action AI Fan-made (Seedance 2.0)

    🎮 Gaming / Anime ·304.7K views · 1.3K/day ·10.8× its audience · 4:11 ·2026-02-11 · English / Global

    0.9×
  5. 05

    Goku vs Merus | Dragon Ball The Galactic Patrol Live Action AI Fan-made (Seedance 2.0)

    🎮 Gaming / Anime ·90.3K views · 409/day ·3.2× its audience · 6:15 ·2026-02-16 · English / Global

    0.3×

How to read this channel

1.234.567 Dragon Ball is a 28,100-subscriber channel working mainly in Gaming / Anime, publishing first in English / Global. The radar tracks 5 of its uploads. Its strongest signal (breakout score 1.3× the dataset median) reaches 23.7× the channel's subscriber count and has averaged 4,597 views a day since it was published 145 days ago, on “LEGEND 2: A Dragon Ball Tale (2026) | Live-Action AI Film (Fan-made)” (666,517 views). That is a lifetime average, not a current rate — one capture per video means this dataset cannot distinguish a video that is still climbing from one that already peaked. The API reports the audio track language as en.

There is one statistic this page deliberately does not print: a per-channel “share of uploads that reached 3×”. Every video on this site cleared that floor before it could be tracked at all, so the figure would read 100% for every channel and would distinguish nothing. What is left instead: 5 tracked uploads pulling 2,269,693 views between them, the strongest reaching 23.7× its audience. Repeated strong reach across several uploads is the part that suggests a format; one outlier is not. The hook patterns the tracker infers from its titles are statement / cold open (3), contradiction hook (2), and the production choices that repeat are no-face format (no host on camera), talking about ai, not an ai-made film, fan-made / concept trailer format, single-sitting long-form (30min+).

What to copy and what to skip: copy the packaging pattern (title structure, the promise made in the first seconds, the episode length that keeps working) and skip the parts that only this channel can do — an existing subscriber base, cross-posting, or a back catalogue that feeds recommendations. Then compare this channel against the others on its category board: same niche, different market, different length. That comparison is where the transferable part usually hides.

Reproducible playbook

Opening hook (title-derived)

Statement / cold open · estimated hook window 12s before the main body.

Beat rhythm (Hook → ranked/labeled segments → closing tease)

  • Hook 0%–6%
  • Context 6%–20%
  • Escalation 20%–60%
  • Turn 60%–85%
  • Close 85%–100%

Production choices that repeat

  • No-face format (no host on camera)
  • Talking about AI, not an AI-made film
  • Fan-made / concept trailer format
  • Single-sitting long-form (30min+)
  • Ends on a cliffhanger to farm next-episode views

Derived from the title, duration and market — no frame-level video analysis, and no use of the labels this site writes on an entry.

Compare with

Same niche, market by market

Niche board and neighbouring channels

Snapshot rebuilt 2026-09-25 · 2557 signals · 954 channels. Metrics come from the YouTube Data API v3 and are stored captures, not live counters; ages are recalculated from each video's publish date at build time.