|
|
Post by adamiata on Jan 30, 2014 9:47:08 GMT -5
|
|
|
|
Post by Anthony McCauliff on Jun 30, 2016 0:58:14 GMT -5
I just ran the white dot today and my garmin timed me at 20:18.8 with an average pace of 16:14, the ascent was 1.25 miles with an elevation increase of 3,128. Not sure how to make it official or if anyone has a better time. I was told to post here and see. thanks
|
|
|
|
Post by Peter Bakwin on Jun 30, 2016 8:05:50 GMT -5
I just ran the white dot today and my garmin timed me at 20:18.8 with an average pace of 16:14, the ascent was 1.25 miles with an elevation increase of 3,128. Not sure how to make it official or if anyone has a better time. I was told to post here and see. thanks You should post a link to you GPS track for verification. Good show, thanks. |
|
|
|
Post by Anthony on Jun 30, 2016 13:06:09 GMT -5
How do I post a link?
|
|
|
|
Post by Anthony on Jun 30, 2016 13:07:24 GMT -5
|
|
|
|
Post by Campton Man on Jun 30, 2016 14:37:12 GMT -5
Hi Anthony,
It appears this data was collected over the span of more than an hour, while the watch only ran for 20:18. In other words it looks like you started and stopped your watch multiple times while making your way up the mountain. Can you explain the discrepancy between your claimed time (20:18) and the elapsed time (1:03:21) or moving time (58:49)?
|
|
|
|
Post by Anthony on Jun 30, 2016 14:51:43 GMT -5
I have my pace set to a 7:40 pace and it auto pauses when the pace goes down lower then a certain time. Otherwise I'm not sure, I'm new to using the garmin technology and the app. But if it gets lower then I think 11 or something it will auto pause. I'll double check and if I gotta run it again I definitely can do that. I'll keep you posted and if you have any advice I'm open to it. Thanks  |
|
|
|
Post by bennephew on Jun 30, 2016 19:22:21 GMT -5
It looks like there were 20 minutes of running at 7:40 pace during a run of about an hour up the mountain. It would probably be best to run it again without the auto pause on. Elapsed time needs to be under the current FKT.
|
|
|
|
Post by finnski on Aug 5, 2016 20:31:56 GMT -5
none of this makes any sense. First of all it is a little over 1.9 miles(not 1.25) up the white dot. Secondly it is about 1800 feet of elevation gain not 3128 feet. I don't think anybody is gonna do a 20:18 any time soon but I could be wrong.
|
|
|
|
Post by David Kilgore on Aug 13, 2017 22:27:41 GMT -5
|
|
|
|
Post by Jim on Aug 14, 2017 12:22:19 GMT -5
That GPS record looks pretty sketchy, looks like it's missing the first 2/3 and stops just before the summit.
|
|
neil
New Member
Posts: 13 
|
Post by neil on Aug 14, 2017 19:37:06 GMT -5
Yeah, quite sure the FKT route is supposed to start at the bottom and end at the top...there's a clear start to the trail at the sign and there's summit marker at the top... just follow the crowds!
|
|
|
|
Post by diego on Aug 14, 2017 20:43:53 GMT -5
|
|
|
|
Post by David Kilgore on Aug 14, 2017 21:21:41 GMT -5
I mean it's fine I ran over the "correct" distance running from the rangers station. I'll go back and run it again and get the rangers involved and try to improve the time🤙🏽
|
|
|
|
Post by David Kilgore on Aug 14, 2017 21:32:55 GMT -5
Or if any of you are residents of New Hampshire I invite you out to go up it with me or be around when I do, will be a fun time
|
|
