Ask any fantasy cricket player which stat they check first, and strike rate is usually near the top of the list. It’s the number that tells you how fast a batter scores, not just how many runs they get.
## The Formula
Strike rate is calculated as:
**Strike Rate = (Runs Scored ÷ Balls Faced) × 100**
So a batter who scores 60 runs off 40 balls has a strike rate of 150. That means, on average, they score 1.5 runs every ball they face.
## Why It Matters More in Some Formats
In Test cricket, a batter can afford to graft through a slow patch because time isn’t as scarce. In T20 cricket, every ball is precious, so a high strike rate often matters more than a big total. A batter who scores 30 runs off 15 balls can be more valuable to a T20 side than one who scores 60 off 55.
This is exactly why our piece on how cricket scoring works is worth reading first if you’re still getting familiar with overs and formats — strike rate only makes sense once you understand how limited the balls are.
## Strike Rate Isn’t the Full Picture
A high strike rate looks great on paper, but it doesn’t measure consistency or how often a batter gets out. That’s where batting average comes in as a companion statistic. Some of the most complete batters — from finishers to top-order anchors — are judged on a blend of both numbers. We break this comparison down fully in batting average vs strike rate.
## Strike Rate in Action
Explosive T20 innings routinely push strike rates above 200. It’s the same instinct for speed that produced some of the fastest hundreds ever scored in the sport’s history — innings where batters didn’t just score fast, they redefined what fast looks like.
Whether you’re setting your fantasy XI or just trying to understand a scorecard, strike rate is one of the simplest yet most revealing numbers in the sport.