
실시간으로 먹튀 당하는 기자 (방송사고 레전드)
Published November 26, 2021
At a glance
Views
803,515
Likes
12,038
Comments
186
Performance vs. channel
All-time outlier score
Engagement rate
More features coming
We're working on new analytics and tools. Stay tuned.
About
이 영상은 번개장터의 지원을 받아 제작되었습니다. #문상 #문상기자 #shorts Instagram @bdnspresents
- Published
- November 26, 2021
- Made for kids
- No
More features coming
We're working on new analytics and tools. Stay tuned.
How 실시간으로 먹튀 당하는 기자 (방송사고 레전드) is doing
It has 803K views in total. It ranks #5,513,250 among tracked YouTube videos by views.
Key facts about 실시간으로 먹튀 당하는 기자 (방송사고 레전드)
- Total views
- 803K
- Total likes
- 12.0K
- Total comments
- 186
- Published
- November 26, 2021
- Global rank by views
- #5,513,250
Frequently asked questions
How many views does 실시간으로 먹튀 당하는 기자 (방송사고 레전드) have?
실시간으로 먹튀 당하는 기자 (방송사고 레전드) has 803,515 views, 12,038 likes and 186 comments, ranking #5,513,250 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.