Breakout Lens

Channel profile · tracked by Breakout Lens

CloverSHORT

41,900 subscribers · about 4 months old · ~10.8K subs/month to date ·publishing in English / Global ·Romance / Mini-Drama, Sci-Fi / Time Travel

2tracked breakouts
1.0×best breakout score
9.1×best reach, views per subscriber
571.2Ktotal views tracked
6.8×median reach, tracked videos

Breakout videos

  1. 01

    She think cold CEO marry her just for deal—every night he can't stop kissing her! He love her long!

    💕 Romance / Mini-Drama ·379.7K views · 10.3K/day ·9.1× its audience · 1:41:22 ·2026-09-04 · English / Global

    1.0×
  2. 02

    She time-travel as parents' classmate, plan split them save mom, but fall for their sweet love!

    🌌 Sci-Fi / Time Travel ·191.5K views · 3.2K/day ·4.6× its audience · 2:47:59 ·2026-08-12 · English / Global

    0.8×

How to read this channel

CloverSHORT is a 41,900-subscriber channel (about 4 months old) working mainly in Romance / Mini-Drama, Sci-Fi / Time Travel, publishing first in English / Global. The radar tracks 2 of its uploads. Its strongest signal (breakout score 1.0× the dataset median) reaches 9.1× the channel's subscriber count and has averaged 10,262 views a day since it was published 37 days ago, on “She think cold CEO marry her just for deal—every night he can't stop kissing her” (379,678 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: 2 tracked uploads pulling 571,227 views between them, the strongest reaching 9.1× 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 (1), contradiction hook (1), and the production choices that repeat are no-face format (no host on camera), single-sitting long-form (30min+), billionaire / cinderella romance template, ends on a cliffhanger to farm next-episode views.

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.

Those are audience numbers, not earnings: the public API returns views and subscribers but never revenue, so nothing on this site can tell you what the channel takes in. To turn an audience size like this one into a money figure under assumptions you set yourself, the YouTube channel value calculator applies an RPM you choose to views the API actually reports — it draws its comparables from the same tracked channels, and it holds no revenue data either.

Reproducible playbook

Opening hook (title-derived)

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

Beat rhythm (Conflict → reversal → cliffhanger)

  • Hook 0%–3%
  • Setup 3%–15%
  • Act 2 15%–55%
  • Climax 55%–85%
  • Resolution 85%–100%

Production choices that repeat

  • No-face format (no host on camera)
  • Billionaire / Cinderella romance template
  • 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-10-11 · 3536 signals · 1334 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.