The graphic appears for four seconds between overs, covered in coloured lines, and then vanishes. Almost nobody reads it, which is unfortunate, because it usually contains the explanation for everything that just happened.
Wagon wheels and pitch maps are the two most useful tools in broadcast match analysis, and both are straightforward once you know what each axis represents.
This guide explains how to read them, what patterns to look for, and how teams use the same data to build plans against individual players.
What a Wagon Wheel Shows
A wagon wheel plots where a batter’s runs were scored, drawn as lines radiating from the centre of the ground.
Each line represents a scoring shot, with the direction showing where the ball travelled and the length usually indicating whether it reached the boundary.
Colour coding varies by broadcaster but commonly separates boundaries from other scoring shots, or distinguishes between bowler types.
The crucial detail is that a wagon wheel shows runs, not shots. Deliveries that produced nothing are absent entirely, which means the graphic shows success rather than approach.
That omission matters, because a batter may be attempting a shot repeatedly and only occasionally connecting, and the wheel will show only the connections.
What a Pitch Map Shows
| Element | What it represents |
|---|---|
| Vertical position | Length, from full to short |
| Horizontal position | Line, relative to the stumps |
| Dot colour | Outcome, such as runs or a wicket |
| Dot size | Sometimes runs conceded |
| Cluster density | Consistency of the bowler |
| Outliers | Deliveries that missed the plan |
| Shaded zones | Broadcaster-defined good length areas |
A pitch map shows where deliveries bounced, which is the bowling equivalent of the wagon wheel, and unlike the wheel it includes every delivery regardless of outcome.
Cluster density is the single most useful feature. A tight group indicates a bowler executing a plan, while a scattered map indicates one searching for a method.
Reading Them Together
The two graphics answer different halves of the same question and are far more informative combined.
If a batter’s runs come overwhelmingly on one side of the ground, check the pitch map to see whether bowlers are still delivering into the area that allows it.
If a bowler’s map is tightly clustered but runs are flowing, the batter has found a scoring option against the plan and the plan needs changing rather than repeating.
If the map is scattered and runs are low, the bowler is surviving rather than controlling, and the situation is less stable than the figures suggest.
And if both are tight, with few runs and consistent lengths, you are watching a genuine contest where neither side has solved the other yet.
Patterns Worth Looking For
- A quadrant of the wheel with almost no lines
- Boundaries concentrated against one bowler type
- Pitch map clusters that drift shorter as a spell continues
- Deliveries straying to the leg side under pressure
- A batter scoring square but not straight, or the reverse
- Wickets clustered in one zone of the map
- Runs concentrated in the final two balls of overs
- Changes in pattern after a drinks break
The empty quadrant is the most actionable. A batter with no runs in one area either cannot play there or is choosing not to, and either way the bowling side has a plan available.
Scoring Zones and What They Reveal
Dividing the field into zones turns a wagon wheel into something closer to a diagnosis.
| Zone | Heavy scoring suggests | Bowling response |
|---|---|---|
| Straight down the ground | Full deliveries, good driving | Pull the length back |
| Square on the off side | Width available, strong cut | Bowl closer to the stumps |
| Behind square on the off side | Short deliveries, good upper cut | Reduce the bouncer frequency |
| Square on the leg side | Straying line, strong pull | Correct the line immediately |
| Fine on the leg side | Deflections and glances | Often acceptable, low risk |
| Evenly spread | A batter in complete control | Change bowler or angle |
An evenly spread wheel is the most ominous pattern for a bowling side, because it means no single field adjustment will contain the batter and the plan has to change entirely.
Heavy scoring square on the leg side is the easiest problem to fix and the most embarrassing to allow, since it almost always indicates a line error rather than a batter’s strength.
Fine leg-side scoring is frequently tolerated deliberately, as those shots carry low risk for the batter but also produce few boundaries, which is an acceptable trade for the bowling side.
Frequently Asked Questions
Does a wagon wheel show where the ball was hit or where it was fielded?
Where it travelled, plotted as a straight line from the batting position, which means deflections and edges can appear misleading.
Why do pitch maps differ between broadcasters?
Because the shaded length zones are defined by each production rather than by a standard, so the same delivery can appear in different categories.
Are these graphics accurate?
The tracking data is accurate within small margins. The interpretation layered on top, particularly length categories, is where the variation occurs.
Can I see them for past matches?
Yes. Most detailed scorecard services retain both graphics, and reviewing them after a match is considerably more useful than glimpsing them live.
The Short Version
A wagon wheel plots where runs were scored and omits unsuccessful shots. A pitch map plots where every delivery bounced, with vertical position showing length and horizontal showing line. Read them together: empty quadrants on the wheel and tight clusters on the map are the two most useful signals.
Using Them Yourself
Pick one batter and one bowler per match and check both graphics at each interval.
Within a few matches the patterns become visible without the graphics at all, which is the point at which watching cricket changes noticeably.
How Teams Use the Same Data
Analysts work with far more detail than broadcasts show, and the methods are an extension of the same two graphics.
Wagon wheels are filtered by bowler type, by phase of the innings and by delivery length, which produces a separate picture for each situation a batter faces.
That filtering is where plans come from. A batter may score freely against pace square of the wicket and almost nothing against spin in the same area, and only the filtered view shows it.
Pitch maps are overlaid with outcome data, showing which zones produced dot balls, which produced boundaries and which produced wickets against a specific player.
The intersection of those two views is a bowling plan, defined as a target zone with a field set to the batter’s established scoring pattern.
Players are given this in simplified form before a match, usually as two or three instructions rather than a dossier, because more detail than that stops being useful on the field.
Limitations of Both Graphics
Neither tool is complete, and knowing the gaps prevents overreading them.
Wagon wheels ignore deliveries that produced no runs, so a batter playing and missing twenty times appears identical to one leaving confidently.
They also plot lines from a fixed point, which distorts shots played from well outside the crease or after significant movement.
Pitch maps show where the ball bounced but not what it did afterwards, so a delivery that seamed sharply and one that went straight on appear in the same place.
Neither captures pace, which is frequently the decisive variable, and a slower ball and a quick one in the same zone are entirely different propositions.
And both aggregate across time, which hides the sequence, even though the order of deliveries is often the thing that produced the result.
Other Graphics Worth Understanding
Broadcasts carry several related displays, and a few are more useful than the two headline ones.
Beehive charts plot where deliveries passed the stumps rather than where they bounced, which captures bounce and movement in a way a pitch map cannot.
Manhattan charts show runs per over as a bar graph, which makes the phases of an innings immediately visible and highlights the overs that changed a match.
Worm graphs compare two innings as cumulative lines, which is the quickest way to see where a chase fell behind or pulled ahead.
Speed and spin charts show how a bowler’s pace or revolutions varied through a spell, which is where fatigue becomes visible before it appears in the figures.
Control percentage, shown by some broadcasters, records the proportion of deliveries a batter met as intended, and it is probably the single most underrated number available publicly.
Building a Habit
Reading graphics well is a practised skill, and a simple routine develops it quickly.
At each interval, look at one batter’s wagon wheel and ask where the empty space is and whether the bowling side has noticed it.
Look at one bowler’s pitch map and ask whether the cluster is tighter or looser than it was in their previous spell.
Make one prediction based on each, such as which shot will produce the next boundary or which length will produce the next wicket.
Check afterwards whether the prediction held, which is the only way to calibrate how much weight these tools deserve.
Within a season that routine produces a genuinely better read on a match than most of what is said about it in real time, and it takes a couple of minutes per interval.
Field Settings and the Graphics
The clearest practical use of both tools is understanding why a field looks the way it does.
A captain who has seen a batter’s wheel will place fielders in the populated zones and leave the empty ones open, which is why fields sometimes appear unbalanced.
That creates a specific invitation. The gap left open is usually the area where the batter is least effective, and taking it is exactly what the bowling side wants.
Good batters recognise this and refuse the invitation, working instead to score in their strong areas despite the fielders placed there, which requires precision rather than power.
Watching a field change after a boundary tells you the bowling side has updated its picture, and watching it stay the same tells you they are prepared to concede that shot.
Once that exchange becomes visible, the quiet periods between deliveries become as interesting as the deliveries themselves.
Analysing a Dismissal
The graphics are at their most useful immediately after a wicket.
Check where the dismissal delivery sits on the pitch map relative to the rest of the spell, since an outlier suggests a mistake by the batter and a cluster member suggests a plan working.
Check the batter’s wheel for that area, as a dismissal in a zone where they had been scoring freely usually indicates a field change rather than a technical failure.
Look at the preceding deliveries, because most planned dismissals are set up by two or three balls that established a pattern before it was broken.
Note whether the bowler had just changed angle or pace, which is the most common trigger for a wicket in an otherwise stable spell.
Doing this for a handful of dismissals makes the difference between a good delivery and a poor shot far easier to judge, which is the hardest call in match analysis and the one most often got wrong.
Where the Data Is Heading
The public versions of these graphics are improving steadily as tracking technology becomes cheaper and more widely deployed.
Shot-by-shot control data is now available in some coverage, and it tends to contradict the eye more often than any other metric.
Release point and seam position tracking are becoming standard in elite competitions, which will eventually make bowling variation visible to supporters rather than only to analysts.
The main constraint is presentation rather than measurement, since the quantity of data available already exceeds what can be shown in a four-second graphic between overs.
Whatever arrives next, the wagon wheel and the pitch map will remain the foundation, because they answer the two questions every passage of play comes down to: where the runs went, and where the ball landed.
Everything else is detail layered on top of those two answers.