
불이 났을 땐 (1절) #동요 #불조심 #깨비키즈
Published October 10, 2026
At a glance
Views
94,172
Likes
803
Comments
0
Performance vs. channel
All-time outlier score
Engagement rate
More features coming
We're working on new analytics and tools. Stay tuned.
About
불이 났을 땐 무섭다고 숨지 말고 큰 소리로 불이야 소리쳐 알리며 빨리빨리 밖으로 뛰어나가요 불이야! 안 그러면 매운 연기 눈앞을 가려 뜨거운 불 속에 갇히게 되지요
- Published
- October 10, 2026
- Made for kids
- Yes
More features coming
We're working on new analytics and tools. Stay tuned.
How 불이 났을 땐 (1절) #동요 #불조심 #깨비키즈 is doing
It has 94.1K views in total. It ranks #11,996,264 among tracked YouTube videos by views.
Key facts about 불이 났을 땐 (1절) #동요 #불조심 #깨비키즈
- Total views
- 94.1K
- Total likes
- 803
- Total comments
- 0
- Published
- October 10, 2026
- Global rank by views
- #11,996,264
Frequently asked questions
How many views does 불이 났을 땐 (1절) #동요 #불조심 #깨비키즈 have?
불이 났을 땐 (1절) #동요 #불조심 #깨비키즈 has 94,172 views, 803 likes, ranking #11,996,264 among tracked YouTube videos by views.
How accurate are these YouTube video analytics?
View, like, and comment counts come from YouTube's public API and refresh regularly. Growth and revenue figures are estimates built from tracked historical data, so they can differ slightly from what the creator sees privately in YouTube Studio.
What is the outlier score?
How this video's views compare to the channel's usual Shorts or long-form video. A 2x score means double the usual views for that channel, 0.5x means half.
What is engagement rate and how is it calculated?
Likes and comments per view, compared to this channel's typical engagement rate — shown as above or below what's usual for the channel.
How is the revenue estimate calculated?
It's a rough public estimate based on a $0.7–$2.0 CPM (revenue per 1,000 views) applied to view count — not actual creator earnings, which depend on ad rates, audience geography, and monetization settings YouTube doesn't expose publicly.
Is this YouTube video analytics checker free?
Yes. You get 10 free channel and video analytics lookups per 24 hours without an account — logging in, which is also free, removes that limit entirely.