YES I CAME TO JAPAN TO EAT🍣🐟🍤 🍘
Published October 8, 2026
At a glance
Views
56,748
Likes
1,213
Comments
45
Performance vs. channel
All-time outlier score
Engagement rate
More features coming
We're working on new analytics and tools. Stay tuned.
About
but I never wanna leave!!! #Japan #tokyo #japantravel
- Published
- October 8, 2026
- Made for kids
- No
More features coming
We're working on new analytics and tools. Stay tuned.
How YES I CAME TO JAPAN TO EAT🍣🐟🍤 🍘 is doing
It has 56.7K views in total. It ranks #12,454,380 among tracked YouTube videos by views.
Key facts about YES I CAME TO JAPAN TO EAT🍣🐟🍤 🍘
- Total views
- 56.7K
- Total likes
- 1.21K
- Total comments
- 45
- Published
- October 8, 2026
- Global rank by views
- #12,454,380
Frequently asked questions
How many views does YES I CAME TO JAPAN TO EAT🍣🐟🍤 🍘 have?
YES I CAME TO JAPAN TO EAT🍣🐟🍤 🍘 has 56,748 views, 1,213 likes and 45 comments, ranking #12,454,380 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.