top | item 32898511

(no title)

ryannevius | 3 years ago

Aleksandr's training is public on his Strava: https://www.strava.com/athletes/26934035

Something to remember is that this is his pace _after_ pit stops, so his actual running pace was faster. Also notable is that this course was kind of terrible, with four 90 degree turns and three 180 degree turns each lap for 209 laps. There's little doubt that he could run > 200 miles on a course with fewer turns.

discuss

order

milansuk|3 years ago

I downloaded .gpx of the run and it's 6.7MB. He started with 4min/km pace, held it for 130km(9 hours) and then He "slowed down" almost linearly to 5min/km when he finished.

sirsinsalot|3 years ago

Wow, my best ever 10k pace was 6min/km. 9 hours ag 4min/k is insane.

mytailorisrich|3 years ago

I've taken to running during my lunch break in March this year and I can now run a 5k most days of the week at a 5:30 per km pace.

So I can't even imagine how he does that.

MuffinFlavored|3 years ago

4min/km = 6:27/mile roughly, I think? If I did the math correctly?

folli|3 years ago

Where did you get the GPX file from?

c-fe|3 years ago

Strava also shares the latitude/elevation during the run. (Screenshot in case you dont have Strava https://imgur.com/PuuKo5r) What I find interesting and don't really understand is why the elevation keeps going down during the run, even though he stayed on the same track. Anyone have an idea why that could be?

hammock|3 years ago

It’s probably based off of a barometer in a watch, not GPS, and the air pressure was changing

gorkish|3 years ago

The elevation in this case is just a proxy for storing the barometric pressure, which is because the actual air pressure is the important thing to track if you are trying to normalize against athletic performance. If the watch logged the GPS altitude, it would be a lot more accurate, but less useful as the air density would only be estimated..

grsmvg|3 years ago

This is his actual running pace. Strava only calculates pace including the stops when you set the activity type to ‘race’, which he didn’t.

speedgoose|3 years ago

I didn’t know you could get a watch with more than 24 hours of battery life including GPS tracking (COROS APEX Pro). The accuracy is a bit weird though, the elevation chart doesn’t make sense.

dfc|3 years ago

I don't think it's that big of a deal for good running watches. I ran the JFK50 with a three year old Garmin 935 with a heart strap (HRM-Tri) in a little under 11 hours. My watch was close to 50%. That was with GPS updates every second. It would have been much better if I left it at the default, not the ultratrac or whatever they call the endurance battery mode.

bakuninsbart|3 years ago

All of the higher-end Garmin watches can do this, it is one of their main selling points. In normal use, I charge mine around once a week.

djsavvy|3 years ago

A sibling comment to yours asked about the elevation --- apparently it's actually a measure of air pressure.

groby_b|3 years ago

High-end Garmin watches as well. The fenix 7 can do 48+h including tracking, the Enduro2 will likely go 3 days.

And yes, elevation is bonkers, because GPS elevation via watch is about as precise as you guessing. (+/- 400 feet on Garmins, but I'm not sure there are any watches significantly better than that. )

jeltz|3 years ago

I ran for 8:30 with my ancient Forerunner 235 and it still had some batteries left. Modern watches can easily do 24 hours, even the mid range Forerunner 255 can do 30 hours and the larger 955 can do 42 hours.

ezfe|3 years ago

The Apple Watch Ultra is rated for 36 hours so long as cell service isn't enabled.