This was the first time I'd been up to Newland's corner since I got lost. I wasn't going to make that mistake again.
4th April 2013
Distance (miles): 2.66
Time (mm:ss): 26:04
Pace (min/mile): 9:45
The first mile on this was good, taking under 8 mins. Then there is a stop, I can't remember what for or why but I'm sure it was very important. After that it averages about 10 minute miles until 2.1 miles, althout it starts off quicker and ends up slower.
After this point the only way I can describe the graph is weird. There's a spike to 35 minutes per mile, but that usually just means I've stopped to tie a shoe lace. It then goes down to 3:52 pace, which I'm pretty sure I can't run. After a couple more starts and stops I seem to have given up and stopped the watch.
The only other time I've had numbers like this is when I tried to use the mapmyrun app on my phone and got an average speed of 2 miles per hour, but a finishing pace of 28 miles per hour. Please note this is not a comment on the app, more likely just the GPS on my phone not dealing with the trees. Admittedly I've never noticed this issue with the Ultrasport though, but then as GPS is what it does you'd hope not.
No comments:
Post a Comment