This Man Was Supposed To Be Dead… 😰#creepy
Published April 23, 2026
At a glance
Views
652,386
Likes
28,200
Comments
768
Performance vs. channel
All-time outlier score
Engagement rate
More features coming
We're working on new analytics and tools. Stay tuned.
About
- Published
- April 23, 2026
- Made for kids
- No
More features coming
We're working on new analytics and tools. Stay tuned.
How This Man Was Supposed To Be Dead… 😰#creepy is doing
It has 652K views in total. It ranks #6,229,868 among tracked YouTube videos by views.
Key facts about This Man Was Supposed To Be Dead… 😰#creepy
- Total views
- 652K
- Total likes
- 28.2K
- Total comments
- 768
- Published
- April 23, 2026
- Global rank by views
- #6,229,868
Frequently asked questions
How many views does This Man Was Supposed To Be Dead… 😰#creepy have?
This Man Was Supposed To Be Dead… 😰#creepy has 652,386 views, 28,200 likes and 768 comments, ranking #6,229,868 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.