의리를 위해 〈태양의 후예〉 OST 거절했던 백지영ㄷㄷ
Published October 2, 2026
At a glance
Views
177,489
Likes
411
Comments
31
Performance vs. channel
All-time outlier score
Engagement rate
More features coming
We're working on new analytics and tools. Stay tuned.
About
#태양의후예 #백지영 #해방타운 의리를 위해 태양의 후예 ost 거절했었던 백지영b 좋아요&구독은 큰 힘이 됩니다👍
- Published
- October 2, 2026
- Made for kids
- No
More features coming
We're working on new analytics and tools. Stay tuned.
How 의리를 위해 〈태양의 후예〉 OST 거절했던 백지영ㄷㄷ is doing
It has 177K views in total. It ranks #10,700,188 among tracked YouTube videos by views.
Key facts about 의리를 위해 〈태양의 후예〉 OST 거절했던 백지영ㄷㄷ
- Total views
- 177K
- Total likes
- 411
- Total comments
- 31
- Published
- October 2, 2026
- Global rank by views
- #10,700,188
Frequently asked questions
How many views does 의리를 위해 〈태양의 후예〉 OST 거절했던 백지영ㄷㄷ have?
의리를 위해 〈태양의 후예〉 OST 거절했던 백지영ㄷㄷ has 177,489 views, 411 likes and 31 comments, ranking #10,700,188 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.