Frequently Asked Questions: Beeptest
Some questions useres (or would be users) have asked us in the past...
1. I am running Windows Vista and have no access to the help page, is there any way I can see a copy of this?
Let us know, we will email a pdf document, covers all the team beeptest usage & functions .
2. When I select save results, where are they saved?
Into the players.txt file, same directory as your team beeptest exe file.
3. How do I see the results in table format rather than just the graph?
The players.txt can be viewed in any text editor, or word processing (which can convert to a table). Martin of rugbycoach converts the players.txt to excel but cannot see any real advantage unless excel is already being used.
4. How can I run this for several teams? I've tried to add a team but all it did was cancel out the first team results.
Just copy the whole beeptest directory to another name i.e.. xyzU18BeepTest, TeamBBeepTest any name and as many teams as you need. The whole application and associated files only come upto around 1Mb so your not using much disk space, then you can have separate players.txt files (upto 25 players) for each team.
5. Is putting the weight of each player in relevant?
Yes/No, I used to show that the percentage body fat correlates very well with beeptest scores! It motivated my front row to loose some weight. But it is of no influence on how the software records scores.
6. Can I use the software for the 30-15 IFT test?
There are some coaches using the 30-15 IFT test on our team beeptest software, have just dug out the papers to remind myself of the details, please let me know if you are interested in these documents....
The major change is pushing out the lap distance to 40m, and bringing down the activity time to 30 seconds with a 15 second rest, giving a 45 second overall stage time. The strange part is that the stages do not complete at the 40m markers, this makes testing awkward.
Please have a look at the a standard beeptest script in full below, this is not usually seen in this form as the beeptest software does not need a script for the standard beeptest. In this case it's a very useful starting point for the 30-15 IFT script. Basically the stages are half the number of laps (ie. from 60s to 30s of activity) with a 15s rest after each stage.
See below for a 30-15 IFT draft script file developed by & sent out to other coaches.
The lap distance is set at 20m to get the beep at the mid point. Text files sometimes get messed up by the email system, check they look correct (have pasted the 30-15 IFT below as a reference), before copying to your beeptest folder.
repeat 6 run 4 rest 15
repeat 3 run 5 rest 15
repeat 4 run 6 rest 15
repeat 8 run 7 rest 15
Stage1Speed = 8.0
Stage2Speed = 8.5
Stage3Speed = 9
Stage4Speed = 9.5
Stage5Speed = 10
Stage6Speed = 10.5
Stage7Speed = 11
Stage8Speed = 11.5
Stage9Speed = 12
Stage10Speed = 12.5
Stage11Speed = 13
Stage12Speed = 13.5
Stage13Speed = 14
Stage14Speed = 14.5
Stage15Speed = 15
Stage16Speed = 15.5
Stage17Speed = 16
Stage18Speed = 16.5
Stage19Speed = 17
Stage20Speed = 17.5
Stage21Speed = 18
7. On the site it says it will take about 90 minutes to test an entire team. Why is it that it takes so long?
How is it that you've set up the test? Are you only doing a couple players at a time? We're looking at running this as part of our initial testing trials with a large number of players trying out and being tested.
I want to know how exactly our increased number of players would affect the time it takes to administer the test. We currently have the players go in two different groups with each player paired up with another one who keeps track of the level achieved and reports to the coaching staff who record the results on a spreadsheet. I just want to make sure this isn't any less efficient than what we currently have in place.
Duration: the test length depends on the fitness of your team of course. My experience is to make two groups of 15 players, with their warm-up and all that makes up the 90 minutes.
With the software you can devote more attention to the players rather than looking up and down the list on your clipboard and run the test perhaps with more players.
You want to test a large group, perhaps it is a good idea to have somebody focussing on the how the players perform the test and make the beeps. He can call out the name to another person just focussing on the clicking the software buttons.
The paring up is an interesting idea! Never heard of this before. The idea of the software is that no seperate paperwork needs to be done.
8. Can I create my own version of the beeptest? Like the Yoyo test?
With the Team Beep Test software you can script your own specific test. This shows the huge flexibility the software of Bitworks gives you.
Create a txt file with this contents:
repeat 91 run 2 rest 10
More information on the YoYo test on this page:
9. Differences in shuttle run / beep test timings!
A while ago I entered a beep test run and managed 13.2. Another beep test in the UK gave about the same result. I then used an iphone application for a third test and managed 15.2 with no additional training. This prompted me to check the timings.
I searched the web and found only a handful of sites with beep test timings. Bewilderingly, not one of the sites agreed with the timings of another!!! I tried contacting various sport authorities around the world and nobody could tell me, for absolute certain, what the official timings were. To cut a long story short I managed to get in contact with Luc Leger who is the creator of the beep test. He explained that his original version started at 8.5 km/hr and increased by 0.5 km/hr for each level thereafter. He also told me that a similar version had been made in another country which started at 8.0 km/hr but immediately increased to 9.0 km/hr for level 2 and then by 0.5 km/hr for each level thereafter. As far as VO2 max goes there is no difference in results between the two tests so either can be used.
I ordered the multi-stage fitness CD from the National Coaching Foundation (NCF) in the UK and recorded the timings. The NCF use the altered timings – starting speed of 8.0, and then 9.0 for level 2. It seems to me that somewhere along the line someone took the starting speed of 8.0 and assumed that the speed increases by 0.5 per level after that… which would give completely different results… hence me getting to level 15.2.
The attached spreadsheet shows you a) the timings of the NCF CD, b) the timings of the official original beep test by Luc Leger, and c) the copy of the table that Luc Leger sent to me.
I’ve also attached the PDF that Luc Leger emailed me which makes interesting reading.
I have updated Wikipedia (which was also incorrect) but I don’t know how long it will stay. Luc Leger told me that he updated the site himself a few times with bits of information and within days someone had changed it back!!
My hope now is that everyone can update their sites and apps so that we are all using the same timings and therefore make the beep test an accurate benchmark for fitness assessment that it was designed for.
Both the pdf document and the mentioned spreadsheet are in the Free Downloads section.