Breakout Lens

Channel profile · tracked by Breakout Lens

Tiny Indian Kitchen - Evgeny Pavlovich

38,400 subscribers · about 10 months old · ~4.0K subs/month to date ·publishing in English / Global ·ASMR / Cozy, Romance / Mini-Drama

2tracked breakouts
10.2×best breakout score
383.3×best reach, views per subscriber
24.6Mtotal views tracked
319.8×median reach, tracked videos

Breakout videos

  1. 01

    Miniature Doll Cooking Massive BIG TUNA FISH ASMR 🐟🌊| Floating Hut Tiny Kitchen Recipe

    😌 ASMR / Cozy ·14.7M views · 97.5K/day ·383.3× its audience · 14:45 ·2026-05-13 · English / Global

    10.2×
  2. 02

    💍🌸Miniature Doll Tiny Indian Wedding Ceremony | Traditional Village Bride Story

    💕 Romance / Mini-Drama ·9.8M views · 53.8K/day ·256.3× its audience · 15:16 ·2026-04-11 · Hindi

    6.2×

How to read this channel

Tiny Indian Kitchen - Evgeny Pavlovich is a 38,400-subscriber channel (about 10 months old) working mainly in ASMR / Cozy, Romance / Mini-Drama, publishing first in English / Global. The radar tracks 2 of its uploads. Its strongest signal (breakout score 10.2× the dataset median) reaches 383.3× the channel's subscriber count and has averaged 97,487 views a day since it was published 151 days ago, on “Miniature Doll Cooking Massive BIG TUNA FISH ASMR 🐟🌊| Floating Hut Tiny Kitche” (14,720,507 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 24,562,509 views between them, the strongest reaching 383.3× 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 shock / scale hook (1), scene-immersion hook (1), and the production choices that repeat are no-face format (no host on camera), ambient audio, no narration track, still images + motion (miniature/cooking asmr style), non-english market spoken first, global subs second.

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)

Shock / scale hook · estimated hook window 2s before the main body.

Beat rhythm (Ambient bed → single action loop → soft close)

  • Hook 0%–5%
  • Escalation 5%–80%
  • Close 80%–100%

Production choices that repeat

  • No-face format (no host on camera)
  • Ambient audio, no narration track
  • Still images + motion (miniature/cooking ASMR style)
  • Non-English market spoken first, global subs second

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.