
【負けたら坊主】キーパーと1対1した結果…
Published July 16, 2022
At a glance
Views
1,141,057
Likes
33,507
Comments
211
Performance vs. channel
All-time outlier score
Engagement rate
More features coming
We're working on new analytics and tools. Stay tuned.
About
2023年3月31日までにYouTubeのチャンネル登録10万人いかなければ現役フットサル選手引退になります。どうかチャンネル登録お願いします🙇♂ #フットサル #キーパー1対1 #坊主
- Published
- July 16, 2022
- Made for kids
- No
More features coming
We're working on new analytics and tools. Stay tuned.
How 【負けたら坊主】キーパーと1対1した結果… is doing
It has 1.14M views in total. It ranks #4,555,625 among tracked YouTube videos by views.
Key facts about 【負けたら坊主】キーパーと1対1した結果…
- Total views
- 1.14M
- Total likes
- 33.5K
- Total comments
- 211
- Published
- July 16, 2022
- Global rank by views
- #4,555,625
Frequently asked questions
How many views does 【負けたら坊主】キーパーと1対1した結果… have?
【負けたら坊主】キーパーと1対1した結果… has 1,141,057 views, 33,507 likes and 211 comments, ranking #4,555,625 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.