• Welcome to the Cricket Web forums, one of the biggest forums in the world dedicated to cricket.

    You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join the Cricket Web community today!

    If you have any problems with the registration process or your account login, please contact us.

How to measure bowling speed

thierry henry

International Coach
Strangely I seem to have lost that extra pace I was talking about in that other thread, but my bouncers are still quick. Everything else is pretty gentle. Can't work it out.
 

Arutha

Cricket Spectator
SOrry, but I've done that. The digits on the stopwatch divided by 72 to get km. Doesn't work, I get something under 0
 

Son Of Coco

Cricket Web: All-Time Legend
Pfft, what was wrong with the car method?
The easiest way to get an accurate reading is to bowl it while you're standing on the hood. My quickest delivery is 240kph on the south-eastern freeway. Reckon I could have gone quicker too but I swallowed a bug as I hit my delivery stride.

A word of warning, at those speeds you have to keep an eye out for the ball coming back at you as it loses velocity.
 

PhoenixFire

International Coach
Work what out? The speeds?

Finally, we've got everything sorted out - so how fast do you actually bowl? Naturally, the best thing possible to use would be a radar gun - however they're not generally widely available to clubs and schools - but there is a simple way that needs just a stopwatch and a calculator (or maths geek) to provide approximate results. Start the stopwatch when the ball is released, and then stop it again when either the batsman hits (or misses) it, then divide 45 (or 72) by your answer to get your answer in miles per hour (or kilometres). For example, a delivery timed at 1 second has travelled at about 45mph (72kph). To break the magical 100mph (160kph) barrier, the clock must register at 0.45 seconds. Once you get used to working the timer, you will get surprisingly consistent results. I've found that standing at the back of the net, either directly behind or just to the side, gets the best results.

Stolen from CW, I haven't seen the article in ages, but found this on the forum in another thread.
Pretty sure that won't work because it gives you the average speed rather than the speed as soon as it leaves the hand. If you are really bothered..

You can set up 2 checkpoints (one half-way down the wicket and one at the batsman) by the side of the wicket and get a person with a stopwatch to measure the time it takes the ball to travel from your hand to each of the checkpoints. You'd be able to measure the deceleration of the ball by dividing the change in speed by the time it takes for the ball to slow down.

Then you'd use the equation s=ut+(at^2)/2 to calculate the inital speed of the ball, where:
s=displacement (or distance)
u=initial speed
t=time
a=acceleration

Rearrange that equation to make u the subject, which gives you (s-1/2at^2)/t=u, just plug the numbers you have in and you should be able to find the intial velocity of the ball.
 

Jakester1288

International Regular
SOrry, but I've done that. The digits on the stopwatch divided by 72 to get km. Doesn't work, I get something under 0
You're obviously doing it wrong then. Do it the opposite way.

When I did it with my friends one day at school, we got around 80-90kph, which is about right, so it works.
 

daghetto

Cricket Spectator
If you use a stopwatch, and start it when the ball leaves the bowlers hand and then passes the wickets.

Then:

0.50 - 90mph/144.85kph
0.55 - 81.8mph/131.6kph
0.60- 75mph/120kph
0.65 - 69mph/11kph
0.70 - 64mph/103kph
0.75 - 60mph/96kph
0.80 - 56mph/90kph
0.85 - 52mph/85kph
0.90 - 50mph/80kph
0.95 - 47mph/77kph
1.00 - 45mph/72kph
1.10 - 40.9mph/65kph
1.20 - 37.5mph/60/35kph

These happen to be fairly accurate as i tried it at a Yorkshire Durham county game and seemed to come out within 5 mph of the speed that came up on the screen which was probably down to human error.

I then tried this on myself and realised I could just about hit 70mph which I was delighted with as i consider myself a medium pace and I'm 15

i clocked myself at 0.45 doing this with a tape-ball lol, thats around 100mph
 

Jim2109

Cricket Spectator
the stopwatch method doesnt really work. firstly, it will give you average speed which isnt the same measurement method as you see on television for the pros. secondly, its HUGELY inaccurate!! even at an average speed of 50mph, the total measurement time is going to be 0.9 secs over 22 yards. the average human reaction time is 0.2 secs, and that applies to both the start and stop of the stopwatch. so potentially your measurement could be as low as 0.5 or as high as 1.3 secs. meaning your calculated speed could vary from 35-90mph!!

and that ignores the fact that the ball will most likely bounce, and thus lose quite a lot of speed. so its just not a good method at all.

the best method is to use a speed gun since thats how the pros are measured, and thus you have a more direct comparison. the second best method is to use a slow motion video camera, but thats more expensive than a speed gun, but some people might already own a camera that is capable of this.

its still not perfect since it has to average speed over the first few yards. but you can measure the delivery from side on with 2 known distance markers, then use freeze frame to calculate the speed from the video. it will be very close to the result of a speed gun.
 

Neil Pickup

Cricket Web Moderator
the stopwatch method doesnt really work. firstly, it will give you average speed which isnt the same measurement method as you see on television for the pros. secondly, its HUGELY inaccurate!! even at an average speed of 50mph, the total measurement time is going to be 0.9 secs over 22 yards. the average human reaction time is 0.2 secs, and that applies to both the start and stop of the stopwatch. so potentially your measurement could be as low as 0.5 or as high as 1.3 secs. meaning your calculated speed could vary from 35-90mph!!
That would be the first known instance of a human reaction time causing an incident to be recorded before it happened, then? You have either completely misunderstood, or wilfully misinterpreted, the logic behind the method. The same person is stopping the watch as is starting it, therefore their reaction time is likely to cancel itself out.

0.00s - ball released
0.20s - human starts watch
0.90s - ball reaches wicket
1.10s - human stops watch

The time elapsed between the start and end of the ball's journey is the same as the time elapsed between the start and stop on the watch. There is no chance that will end up as 0.5 or 1.3 seconds. I am not denying there will be human error, but it cannot be to that extent.

Here's a few examples off Mitchell Johnson's current over.
Ball 1: timed at 0.47s (96mph) - Sky say 87mph
Ball 2: timed at 0.54s (83mph) - Sky say 86mph
Ball 3: timed at 0.43s (105mph) - Sky say 87mph
Ball 4: timed at 0.48s (94mph) - Sky say 89mph
Ball 5: timed at 0.61s (74mph) - Sky say 82mph [slower ball]
Ball 6: timed at 0.50s (90mph) - Sky say 87mph

My calculation of average speed: 90mph
Sky's calculation of average speed: 86mph

Over a period of time, and crucially with sensible averaging/discarding of outliers, you do get a pretty good idea. Obviously it would make a good deal of sense for me to ignore the measurement for ball 3 as 105mph is clearly crap, which then gives an average of 87mph... which ain't bad.
 

Jim2109

Cricket Spectator
its less likely that someone would hit the button before the event has happened, so in theory yes, you should be out by similar amounts on both pushes. but theres no guarantees there, and its hard to judge a ball hitting the pitch at 60+ mph from close range. watching cricket on TV you have the added benefit of seeing it from an elevated distance in high quality, at ground level youre going to need to be timing from roughly where the ball lands so that you can then also accurately measure the distance.

your average speed is fairly close. but that 3rd ball is still a long way off. 21% in fact. and as said, through ideal timing conditions watching from a distance on TV. executed well there is every possibility that real life timing COULD be within 2-3mph every time. but theres every chance it will be highly inaccurate. youre not going to know either way really, youve had the added benefit in your example of seeing the actual speeds on the TV to verify your measurements. in real life you dont have that (if you did then you wouldnt need the stopwatch lol). Johnsons actual speed spread was 7mph. yours is 31mph, which illustrates my point. even without the wayward measurement, its still 22mph. imagine thats a club bowler at 75mph and youre measuring anything from 65-85mph. thats a massive difference in speed from a batting perspective!

if you average the results over enough deliveries youd expect to be within 10%, so its better than nothing, and its free. but just take the results with caution. its not as accurate as a speed gun or slow motion camera. and this is assuming the person with the stopwatch is good at it. id imagine most people trying this would be kids, so you can easily see one of them going home telling their parents they bowled their mate out with a 100mph delivery at the nets!!
 

Neil Pickup

Cricket Web Moderator
If you average the results over enough deliveries youd expect to be within 10%, so its better than nothing, and its free. but just take the results with caution. its not as accurate as a speed gun or slow motion camera. and this is assuming the person with the stopwatch is good at it. id imagine most people trying this would be kids, so you can easily see one of them going home telling their parents they bowled their mate out with a 100mph delivery at the nets!!
Which is exactly what I said in the first place.
 

Jim2109

Cricket Spectator
Which is exactly what I said in the first place.
but still something not one person prior to my reply had mentioned. so youll have a load of people timing individual deliveries thinking theyre as quick as Shaun Tait. if you average it over enough deliveries then sure, it gets you somewhere close to the average speed across whatever distance youre measuring. still give or take 10-15mph id say based on the average accuracy of a human response, but somewhere close. a speed gun gets you pretty much on the money, as does slow motion video (if you factor in about 3% speed loss due to drag over the pitching distance).

the other potential pitfall of the stopwatch method is whether you time the ball to the pitch, or time the ball past the stumps. its better to do it to the pitch, but then youve also got an estimated distance as a factor (a yard difference makes about 5% speed difference). if you time it past the stumps then you know the distance but youve got a bounce in there as well which is going to take speed off the ball and drop the average speed.

so like i said in the first place, it doesnt really work, compared to a speed gun. there are more accurate ways of doing it, but none of them are free unless you already own the equipment.
 
Last edited:

Matteh

Cricket Web: All-Time Legend
so like i said in the first place, it doesnt really work, compared to a speed gun. there are more accurate ways of doing it, but none of them are free unless you already own the equipment.
Exactly. Everyone has a Casio watch with a stopwatch, not everyone can fork out for a speed gun purely for bowling speed research.
 

Faisal1985

International Vice-Captain
If you use a stopwatch, and start it when the ball leaves the bowlers hand and then passes the wickets.

Then:

0.50 - 90mph/144.85kph
0.55 - 81.8mph/131.6kph
0.60- 75mph/120kph
0.65 - 69mph/11kph
0.70 - 64mph/103kph
0.75 - 60mph/96kph
0.80 - 56mph/90kph
0.85 - 52mph/85kph
0.90 - 50mph/80kph
0.95 - 47mph/77kph
1.00 - 45mph/72kph
1.10 - 40.9mph/65kph
1.20 - 37.5mph/60/35kph

These happen to be fairly accurate as i tried it at a Yorkshire Durham county game and seemed to come out within 5 mph of the speed that came up on the screen which was probably down to human error.

I then tried this on myself and realised I could just about hit 70mph which I was delighted with as i consider myself a medium pace and I'm 15
Does this work when you are analyzing a video? In full/regular speed?
 

joels344

U19 Debutant
If you use a stopwatch, and start it when the ball leaves the bowlers hand and then passes the wickets.

Then:

0.50 - 90mph/144.85kph
0.55 - 81.8mph/131.6kph
0.60- 75mph/120kph
0.65 - 69mph/11kph
0.70 - 64mph/103kph
0.75 - 60mph/96kph
0.80 - 56mph/90kph
0.85 - 52mph/85kph
0.90 - 50mph/80kph
0.95 - 47mph/77kph
1.00 - 45mph/72kph
1.10 - 40.9mph/65kph
1.20 - 37.5mph/60/35kph

These happen to be fairly accurate as i tried it at a Yorkshire Durham county game and seemed to come out within 5 mph of the speed that came up on the screen which was probably down to human error.

I then tried this on myself and realised I could just about hit 70mph which I was delighted with as i consider myself a medium pace and I'm 15
I'm not sure that works very well at all. Because on a good day, I might be able to hit somewhere in the high 70s to low 80s. Using this method of clocking, my speed on the fastest delivery on my video was around 90, occurring to this. There's no way I can hit 90.
 

Top