Your weekly km and your training pace predict your marathon. See your time today, what more km would be worth, and a safe week-by-week build to get there.
Both are averages over all your runs in the last 8 weeks: total km ÷ 8, and total time ÷ total km. Strava's and Garmin's training totals give you both.
Pop your email in to see it. We'll send you a short guide to building mileage without getting hurt. Your numbers aren't sent anywhere: they're worked out on this device.
Diminishing returns: the first km you add are worth the most. It assumes your training pace stays the same, and anyone adding a lot of volume needs months to build it.
Each build week is within 10% of your last full week. Every fourth week is easier, so your body catches up. Then a 3-week taper.
Athlete OS reads your runs from your watch, tracks your weekly load against your build, flags it when a week jumps too far, and aims every session at what's holding your marathon back.
Your marathon from your training uses Tanda's formula (2011): marathon pace = 17.1 + 140 × e−0.0053 × weekly km + 0.55 × training pace, in seconds per km. It was built on a small group of experienced marathoners, so treat it as an estimate. Above 150 km a week it's stretched past most of the runners it came from. Your race uses Riegel's formula (time × distance ratio1.06), which tends to be optimistic for the marathon on low mileage. That's why the two can disagree. The build keeps each week within 10% and adds an easier week every fourth: a coaching rule, not a guarantee against injury. If something hurts, stop.