# Thread: How to measure bowling speed

1. I am 16 years old, and I'm a pace bowler.

Some guys think I'm real fast, they tell me I'm around 125 km/h.

Thanks!

2. I was just wondering, how do you work that out on a calculator?

3. 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.

4. Pfft, what was wrong with the car method?

5. Originally Posted by slowfinger
Pfft, what was wrong with the car method?
AWTSoC

6. 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.

7. 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

8. Originally Posted by slowfinger
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.

9. Originally Posted by Jakester1288
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.

10. Nerd.

11. SS to come in and say that it's all wrong.

12. Originally Posted by Arutha
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.

13. Just hire a radar gun ffs

14. Originally Posted by jonny1408
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

15. Originally Posted by daghetto
i clocked myself at 0.45 doing this with a tape-ball lol, thats around 100mph
You're obviously very skillful to clock yourself.

Page 2 of 3 First 123 Last