
Test cricket's over-rate penalties, explained
Slow over rates get talked about constantly and understood loosely. The actual penalty structure is more specific than most broadcasts let on.
The rate itself
Teams are expected to bowl a minimum number of overs per hour of playing time in a Test — a target built around how long a fielding side's actions (walking back to mark, field changes, drinks breaks) should reasonably take. Falling short of that rate over the course of a match triggers a penalty, tracked per session and totalled at the end.
What actually gets penalized
The penalty is applied to the fielding captain and team primarily through match fees, plus World Test Championship points deductions when the shortfall is significant — a slow-over-rate breach can cost a team points off its Championship table position, not just a fine. Some allowances are built in for legitimate stoppages (injuries, DRS reviews, drinks breaks in extreme heat), so the calculation isn't a blunt overs-per-hour count — it adjusts for time that wasn't really the fielding side's to control.
Why bowling sides still fall behind
Spin-heavy attacks generally bowl overs faster than pace-heavy ones, since pace bowlers need a longer run-up and more recovery between deliveries — which is part of why over-rate breaches cluster around fast-bowling-heavy teams, especially in longer spells during hot conditions, even when there's no deliberate time-wasting involved.


