CricRhino publishes every batter-versus-bowler matchup in Nepal Premier League history. Here is how to use them honestly.
Read the ball count first, always
Most matchups in a two-season competition are tiny. Two players might have met for eleven deliveries across three matches. A strike rate calculated on eleven balls is not a strike rate; it is an anecdote with a decimal point.
This is why the ball count sits first in our matchup display, before the runs and before the rate.
Dismissals carry more signal than runs
A bowler who has dismissed a batter twice in thirty balls has a real claim on that contest, even if the runs column looks ordinary. Wickets are rarer than runs, so each one carries more information.
Beware the survivorship trap
A batter who has faced a bowler 60 times has, by definition, usually survived him. Large samples in head-to-head data are themselves evidence of something.
What a matchup is genuinely good for
Two things. Spotting a bowler a batter demonstrably cannot get away — low strike rate over a real sample. And spotting the reverse, where a captain should keep a bowler well away from a particular batter at the death.
Everything beyond that is a story you are telling yourself.
Where the numbers come from
Every matchup is counted from the ball-by-ball record — the actual deliveries, not a summary table. That is the only reason these exist for Nepali cricket at all.
