[홍유진의 범죄심리분석 36화] - 광현803호 선장·기관장 살인사건
Published October 26, 2026
At a glance
Views
236,800
Likes
7,841
Comments
399
Performance vs. channel
All-time outlier score
Engagement rate
More features coming
We're working on new analytics and tools. Stay tuned.
About
인도양 한가운데서 선장과 기관장이 살해됐다? 2016년, 광현803호에서 어떤 일이? 살인은 끝났지만, 배는 멈출 수 없었다.
- Published
- October 26, 2026
- Made for kids
- No
More features coming
We're working on new analytics and tools. Stay tuned.
How [홍유진의 범죄심리분석 36화] - 광현803호 선장·기관장 살인사건 is doing
It has 236K views in total. It ranks #9,702,334 among tracked YouTube videos by views.
Key facts about [홍유진의 범죄심리분석 36화] - 광현803호 선장·기관장 살인사건
- Total views
- 236K
- Total likes
- 7.84K
- Total comments
- 399
- Published
- October 26, 2026
- Global rank by views
- #9,702,334
Frequently asked questions
How many views does [홍유진의 범죄심리분석 36화] - 광현803호 선장·기관장 살인사건 have?
[홍유진의 범죄심리분석 36화] - 광현803호 선장·기관장 살인사건 has 236,800 views, 7,841 likes and 399 comments, ranking #9,702,334 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.