절 비웃던 그녀에게 제대로 보여줬습니다 ..
Published February 11, 2020
At a glance
Views
502,208
Likes
14,559
Comments
1,312
Performance vs. channel
All-time outlier score
Engagement rate
More features coming
We're working on new analytics and tools. Stay tuned.
About
이게 나야 [업로드] 월,화,(목),금,토 저녁 9시 업로드 [문의메일] [email protected] [인스타그램] @hxxax_
- Published
- February 11, 2020
- Made for kids
- No
More features coming
We're working on new analytics and tools. Stay tuned.
How 절 비웃던 그녀에게 제대로 보여줬습니다 .. is doing
It has 502K views in total. It ranks #7,076,756 among tracked YouTube videos by views.
Key facts about 절 비웃던 그녀에게 제대로 보여줬습니다 ..
- Total views
- 502K
- Total likes
- 14.5K
- Total comments
- 1.31K
- Published
- February 11, 2020
- Global rank by views
- #7,076,756
Frequently asked questions
How many views does 절 비웃던 그녀에게 제대로 보여줬습니다 .. have?
절 비웃던 그녀에게 제대로 보여줬습니다 .. has 502,208 views, 14,559 likes and 1,312 comments, ranking #7,076,756 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.