Why autocorrect is so bad with names 🤯 #shorts
Published March 22, 2024
At a glance
Views
133,804
Likes
0
Comments
204
Performance vs. channel
All-time outlier score
Engagement rate
More features coming
We're working on new analytics and tools. Stay tuned.
About
- Published
- March 22, 2024
- Made for kids
- No
More features coming
We're working on new analytics and tools. Stay tuned.
How Why autocorrect is so bad with names 🤯 #shorts is doing
It has 133K views in total. It ranks #11,096,912 among tracked YouTube videos by views.
Key facts about Why autocorrect is so bad with names 🤯 #shorts
- Total views
- 133K
- Total likes
- 0
- Total comments
- 204
- Published
- March 22, 2024
- Global rank by views
- #11,096,912
Frequently asked questions
How many views does Why autocorrect is so bad with names 🤯 #shorts have?
Why autocorrect is so bad with names 🤯 #shorts has 133,804 views and 204 comments, ranking #11,096,912 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.