DemoSynthetic data, not a real runner.Sign up

Generated 19 October 2026

Thames Valley Marathon

Targeting 3:21:00 on 14 December 2026 · 18% probability · 75 sessions analysed

Iteros is writing your personalised sections. The full analysis is already below — the written commentary will appear here in a few seconds.

Your first reading
75runs read.Not yet: runs are not grouped into routes, so there is no most-run route to draw.
Reading 75 runsDone
Scoring six axesDone
Your profile is ready below
Your type and class

No finding is read from an archive yet, so nothing leads yet.

Your shape

This report was made before the radar existed, so it has no shape to draw.

Not yet: runners like you are not drawn: no cohort’s shape is stored to draw beside yours.
Your bests, honestly

Each best against what today’s fitness says. The softer it is, the more is there to take.

5Ka race, 14 August · about 65% age grade21:21
Today’s fitness gives no estimate at this distance.
10Kinside a longer run, 29 August · about 63% age grade44:43
Today’s fitness gives no estimate at this distance.
Half marathoninside a longer run, 29 August · about 65% age grade1:34:20
Today’s fitness gives no estimate at this distance.
Marathona race result you entered · about 65% age grade3:15:36
Today’s fitness gives no estimate at this distance.
● your bestdashed: today’s fitness, estimated
Your races

Found in your archive: the runs your files mark as races, and any race result you entered.

5K11 October21:21about 65%
Marathon29 August3:15:36about 65%
5K14 August21:21about 65%
Not yet: each race is graded against the forecast made before it, and no forecast from before these races is stored. The pattern across them waits on the same.
Your limiter
Not yet: your limiter is the one thing most holding your racing back. Nothing ranks your axes against a race yet, so none is named.
ShareNothing posts until you tap.
Not yet: the share card and your next block, which come with a type and a level to put on it and Your next block's plan.
Not yet: your card is read from your runs, and none is read yet.

Set a race and the next block is built around this.

Thames Valley Marathon, Monday 14 December, is already set.
Not yet: your next block is built around your race with its focus and aims, and blocks are not built yet.
Your first focusWhat kind of runner are you? · 19 Oct
Not yet: Your focus is the one thing most holding your racing back, priced in race time. Nothing ranks your axes against a race yet, so there is no focus to name.

Fitness snapshot

Where you are now against what a 3:21:00 Marathon requires. What the goal demands comes from Daniels' equivalent-performance tables; your current fitness is measured from your own data.

Your threshold pace is 4:16/km. A 3:21:00 Marathon requires sustaining approximately 4:46/km, implying a threshold of about 4:27/km. You have a 10 second buffer — comfortable but not excessive.

How it was worked out: Measured from your fastest sustained 21-minute effort — 4:16/km at 185bpm.

A weekly 20-30 minute continuous effort at threshold pace moves this faster than any other single session.

How this has moved

The fastest sustained tempo or threshold block in each session — a direct measurement of what you can hold, rather than a value inverted from VO2max.

Only 2 sessions carry this metric, which is enough to report where you are but not enough to say how it has changed.

Against the population

77th percentile

Your measured threshold pace against the threshold pace implied by the race times of 500 men aged 35 - 54.

Economy scores 62/100 overall, 72/100 at easy pace (6:08/km). Each pace band is scored against your own range at that band, not against an absolute standard — so this tracks whether you're getting more efficient, rather than ranking you against other runners.

How it was worked out: Scored across 3 pace bands from heart-rate cost at pace, cadence, ground contact time, vertical oscillation.

Economy responds to cadence work, hill sprints and strength rather than to more aerobic volume.

Lactate thresholds

Two thresholds, not one. LT1 is where easy stops being easy; LT2 is the pace you could hold for about an hour. Almost every training decision is really a decision about which side of these two lines to run on.

LT1 · Aerobic threshold

low confidence

159bpmat5:37/km

83% of max HR · Cardiac drift onset

The ceiling of true Zone 2. Below this, a steady pace costs a steady heart rate and you can run for hours; above it, heart rate climbs through the run even when pace doesn't.

Across 32 runs over an hour, heart-rate drift crossed 5% at 159bpm. Every one of those runs stayed on the same side of 5%, so the crossing is projected beyond your data — treat it as a direction, not a number.

LT2 · Anaerobic threshold

low confidence

171bpmat4:16/km

89% of max HR · Threshold pace, modelled HR

The hardest effort you can hold for 40-60 minutes. Above it, lactate accumulates faster than you clear it and the clock starts.

Your sustained threshold blocks averaged 185bpm — 96% of max, which is race effort rather than threshold, so those blocks were harder sessions than their pace suggested. 171bpm is used instead, placed at 85% of your heart-rate reserve. Measured from your fastest sustained 21-minute effort — 4:16/km at 185bpm.

Your productive training zone: 159-171bpm (5:37-4:16/km)

Sessions in this zone drive the most adaptation. Below LT1 you are building base without much stimulus; above LT2 you are accumulating fatigue faster than fitness.

How LT1 was located

Each point is one run over an hour: the heart rate it was held at, against how much your efficiency fell between its first and second halves. Runs below the 5% line held together; runs above it drifted. LT1 is where the two behaviours meet.

Running economy by pace band

BandScorePaceHR costGCTCadence
Easy (>5:00/km)726:08/km146bpm236ms178spm
Moderate (4:30-5:00/km)644:38/km180bpm215ms183spm
Marathon pace (4:10-4:30/km)504:16/km192bpm200ms191spm

HR cost is the heart rate this band costs after correcting for heat and climbing. Each band is scored against your own range within it, not against other runners — a hard session naturally costs more heartbeats than an easy one, so one shared scale would say nothing. The overall economy figure above is the average across the bands with data.

Badges earned from this data

3 badges from 75 sessions. Every one is checked against metrics already calculated above — tap any badge to see exactly what earned it.

Closest to earning

Thousand Club

153km to go.

Century

25 more sessions.

Elastic

Needs 3+ sessions at marathon pace with ground contact recorded; you have 2.

No GOAT tier reached yet.

All six axes must reach 70, and Terrain could not be scored from this upload.

GOAT tiers require every one of the six profile axes to clear the threshold at the same time, which is why they are rare — a single weak axis holds back the whole tier.

Full collection

3 of 25 earned

Locked badges show what they need. Rarity figures are current estimates and will be measured from real data as more runners generate reports.

Earned

Your form holds up when it matters most. Past 25km, your mechanics barely change.

Durability score
95
Session date
2026-08-06
Distance km
28.0

You finish faster than you start. Smart pacing and the fitness to back it up.

Negative split rate
0.9
Qualifying sessions
7

Every runner starts somewhere. This is where your data begins.

Sessions
75

Closest 3

A thousand kilometres on the clock.

153km to go.

85% of the way there

One hundred sessions analysed. The picture of you as a runner is properly detailed now.

25 more sessions.

75% of the way there

Springs for tendons. Your ground contact time at race pace is what elite coaches dream of.

Needs 3+ sessions at marathon pace with ground contact recorded; you have 2.

67% of the way there

Training analysis

75 sessions across 55 weeks, 2 October 2025 to 19 October 2026.

Total distance

847km

75 sessions

Recent volume

31km

per week, last 8 weeks

Sessions per week

2.1

1.4 across the full period

Longest run

42.2km

single session

  • You averaged 31km/week across 2.1 sessions over the last 8 weeks. Your longest run was 42.2km.
  • 75 sessions and 847km in total, from 11 September 2025 to 28 September 2026.
  • Peak week: 54km beginning 31 August.
  • 6 of 75 sessions (8%) were tempo or interval work. That's low — most successful builds sit around 15-20% quality.

Weekly volume

Session mix by distance

TypeSessionsDistanceShare
Easy49438km52%
Tempo224km3%
Interval444km5%
Long run17289km34%
Race352km6%

Long run progression

Kilometres by heart-rate zone

Measured per second of running, not per session — so a session that alternates hard reps with easy recovery contributes to both, rather than averaging into the middle. Zones are shares of heart-rate reserve. Session labels are a judgement; kilometres are not.

ZoneDistanceTimeShare
Z1 Recovery0.0km0:000%
Z2 Base717.2km74:07:3985%
Z3 Aerobic7.6km48:121%
Z4 Threshold42.2km3:36:185%
Z5 Above79.9km6:04:149%

Training load — fitness, fatigue and form

Fitness (CTL) is a 42-day weighted average of training load; fatigue (ATL) a 7-day one. Form (TSB) is the difference — positive means fresher than your recent training, which is what a taper is for.

Your progress

What actually changed across 13 months of training. Starting and current values are averages of the first and last quarter of the block, not single sessions — one Tuesday is not a baseline.

What actually worked

For each metric that moved, the training in the fortnight before its biggest gains, measured against your own typical fortnight. This is the part of the report that is about you specifically rather than about running.

Easy-pace HR improved most after fortnights with 2.0 long runs against your usual 0.9.

Gain seenRunsDistanceQualityLong runsClimb
6 Aug8110km22187m
20 Aug8111km12191m
your usual6.374km0.70.9126m

Based on the 2 largest improvements in this metric — an association across a single training block, not a controlled comparison. Fitness rises through a block whatever the runner does, so anything that trended upward alongside it will appear here.

Late-run contact-time drift improved most after fortnights with 1.0 long runs against your usual 0.7.

Gain seenRunsDistanceQualityLong runsClimb
6 Aug782km21138m
3 Oct782km21138m
29 Aug458km1199m
your usual5.463km1.30.7108m

Based on the 3 largest improvements in this metric — an association across a single training block, not a controlled comparison. Fitness rises through a block whatever the runner does, so anything that trended upward alongside it will appear here.

Ground contact time improved most after fortnights containing 1.3 quality sessions (interval, tempo, threshold or race) against your usual 0.9.

Gain seenRunsDistanceQualityLong runsClimb
4 Aug782km21138m
22 Aug894km21161m
21 Jan547km0079m
your usual6.168km0.90.6115m

Based on the 3 largest improvements in this metric — an association across a single training block, not a controlled comparison. Fitness rises through a block whatever the runner does, so anything that trended upward alongside it will appear here.

Cadence improved most after fortnights containing 2.0 quality sessions (interval, tempo, threshold or race) against your usual 0.9.

Gain seenRunsDistanceQualityLong runsClimb
4 Aug782km21138m
22 Aug894km21161m
your usual6.168km0.90.6115m

Based on the 2 largest improvements in this metric — an association across a single training block, not a controlled comparison. Fitness rises through a block whatever the runner does, so anything that trended upward alongside it will appear here.

Weekly volume improved most after fortnights containing 1.0 quality sessions (interval, tempo, threshold or race) against your usual 0.3.

Gain seenRunsDistanceQualityLong runsClimb
10 Aug798km12167m
12 Oct784km21144m
6 Jul00km000m
your usual2.730km0.30.350m

Based on the 3 largest improvements in this metric — an association across a single training block, not a controlled comparison. Fitness rises through a block whatever the runner does, so anything that trended upward alongside it will appear here.

Every metric, start to now

The fastest sustained tempo or threshold block in each session — a direct measurement of what you can hold, rather than a value inverted from VO2max.

Only 2 sessions carry this metric, which is enough to report where you are but not enough to say how it has changed.

Against the population

77th percentile

Your measured threshold pace against the threshold pace implied by the race times of 500 men aged 35 - 54.

Heart rate on easy and long runs, corrected for heat and climbing. Falling at the same pace is the clearest single sign of an improving aerobic base.

Starting

143bpm

Current

142bpm

Change

no material change

Sessions that drove this

  • 23 Jul 2026 · 8.0km easy — 6:10/km at 140bpm−14bpm
  • 27 Jul 2026 · 10.0km easy — 6:10/km at 140bpm−12bpm
  • 20 Aug 2026 · 9.0km easy — 6:10/km at 140bpm−9bpm

Measured against the four sessions before each one, so a strong session after a poor one isn't credited with the poor one's recovery.

Against the population

The population dataset records training volume, pace and consistency — no heart rate, no running dynamics and no elevation — so there is no like-for-like comparison for this metric.

How far your ground contact time rises above its fresh cost once form starts giving way, per long run. This is the measurement the Durability axis scores — the axis turns it into a 0-100 position, and this is the raw quantity moving underneath it.

Starting

0.7%

Current

0.7%

Change

no material change

Sessions that drove this

  • 3 Oct 2026 · 28.0km — +0.6% contact-time drift after the trajectory turned−0.1%

Measured against the four sessions before each one, so a strong session after a poor one isn't credited with the poor one's recovery.

Against the population

The population dataset records training volume, pace and consistency — no heart rate, no running dynamics and no elevation — so there is no like-for-like comparison for this metric.

The heart-rate cost of your easiest sustained effort in each session, corrected for heat and climbing — how much of your range easy running takes. This is a different measurement from the economy figure in the fitness snapshot, which is how much of your aerobic ceiling converts into race performance and is computed once from a race result.

Starting

54/100

Current

38/100

Change

−15/100

Sessions that drove this

  • 5 Oct 2026 · 8.0km easy — 6:10/km+14/100
  • 19 Sept 2026 · 8.0km easy — 6:10/km+12/100
  • 8 Aug 2026 · 8.0km easy — 6:10/km+12/100

Measured against the four sessions before each one, so a strong session after a poor one isn't credited with the poor one's recovery.

Against the population

The population dataset records training volume, pace and consistency — no heart rate, no running dynamics and no elevation — so there is no like-for-like comparison for this metric.

Milliseconds each foot spends on the ground. Shorter usually means a more elastic, less braking stride.

Starting

236ms

Current

227ms

Change

−9ms (−4.0%)

Sessions that drove this

  • 14 Aug 2026 · 5.0km race — 4:16/km−33ms
  • 11 Oct 2026 · 5.0km race — 4:16/km−33ms
  • 2 Aug 2026 · 11.0km interval — 5:42/km−30ms

Measured against the four sessions before each one, so a strong session after a poor one isn't credited with the poor one's recovery.

Against the population

The population dataset records training volume, pace and consistency — no heart rate, no running dynamics and no elevation — so there is no like-for-like comparison for this metric.

Steps per minute, excluding walk-pace sections. Higher cadence at the same pace usually means less overstriding.

Starting

178spm

Current

181spm

Change

+3spm (+1.8%)

Sessions that drove this

  • 14 Aug 2026 · 5.0km race — 4:16/km+12spm
  • 11 Oct 2026 · 5.0km race — 4:16/km+12spm
  • 2 Aug 2026 · 11.0km interval — 5:42/km+10spm

Measured against the four sessions before each one, so a strong session after a poor one isn't credited with the poor one's recovery.

Against the population

The population dataset records training volume, pace and consistency — no heart rate, no running dynamics and no elevation — so there is no like-for-like comparison for this metric.

Kilometres per week. More volume is the single strongest predictor of endurance performance, up to what you can absorb.

Starting

21.7km

Current

32.2km

Change

+10.4km (+48.1%)

Sessions that drove this

  • 27 Jul 2026 · Week of 6 Jul — 4 sessions, longest 24.0km+48.0km
  • 21 Sept 2026 · Week of 31 Aug — 4 sessions, longest 24.0km+41.4km
  • 28 Sept 2026 · Week of 7 Sept — 3 sessions, longest 28.0km+32.5km

Measured against the four sessions before each one, so a strong session after a poor one isn't credited with the poor one's recovery.

Against the population

19th percentile

Your current weekly volume against the average weekly volume of 500 men aged 35 - 54.

What you can run

Your best efforts at every distance, what each level of effort buys you right now, and whether those bests still describe you.

Personal records

DistanceTimePaceDateWhere it came from
1km4:154:15/km14 Aug 26segment inside a longer run (from km 1.0)
5km22:214:28/km29 Aug 26segment inside a longer run (from km 0.1)
10km44:434:28/km29 Aug 26segment inside a longer run (from km 9.3)
Half marathon1:34:204:28/km29 Aug 26segment inside a longer run (from km 0.0)
Marathon———never covered this distance

Best continuous effort at each distance, found anywhere inside a session — a hard 5km buried in a long run counts, which is why some of these are segments rather than races. Distances you have never covered are left blank rather than estimated. The population line is the median for your cohort, converted between distances through measured race results rather than a formula.

Pace at every effort

Measured on the first ten minutes of every session, so this is what each effort buys you FRESH. The shaded band is the productive zone between your two thresholds. The pale markers are the intensities each race distance is typically run at — where they cross your curve is the pace that distance should cost you.

How it all fits together

Heart rate

Ground contact

At 6:00/km you run 138bpm (72% of max) with 236ms of ground contact.

Hover any chart to move the marker on all of them. Both curves are measured on fresh running, so this is what each pace costs you before fatigue, not averaged across it. No gradient band cleared its sample minimum, so there is no climb figure here.

Were these well executed?

1K4:154:15/km

not assessable

Set when your VO2max was 44.1; it is now 48.4, so this time is probably 23s soft.

5K22:214:28/km

under-executed

Held at 90% of max heart rate, your fresh curve says that effort buys 8s/km faster than you ran. That gap is pacing, conditions or fatigue on the day rather than a fitness ceiling.

10K44:434:28/km

under-executed

Held at 93% of max heart rate, your fresh curve says that effort buys 14s/km faster than you ran. That gap is pacing, conditions or fatigue on the day rather than a fitness ceiling.

Half Marathon1:34:204:28/km

under-executed

Held at 92% of max heart rate, your fresh curve says that effort buys 12s/km faster than you ran. That gap is pacing, conditions or fatigue on the day rather than a fitness ceiling.

Which way you are heading

No fitness trend available, so the prediction range is left symmetric.

Your pace decays 1.0% per doubling of distance, against 2.3% for the population over the same range.

Weekly review · week 8Sunday 18 October
Not yet: a week's verdict reads it against your plan, and no plan is stored, so the week is described and not judged.
The week in a line
Mon–No run
Tue8easyRun
Wed–No run
Thu30long runRun
Fri–No run
Sat9easyRun
Sun–No run

47km. 3 runs.

Aims this week
Not yet: Aims are set with a block, each with a start, a target and a check date. None is set yet.
Intensity splitDerived
85% easy6% moderate9% hard
Time in each heart-rate zone, as fractions of your heart-rate reserve: easy is Z1 and Z2, moderate Z3, hard Z4 and Z5. Runs with no heart-rate stream are not counted.
LoadDerived
This week47kmRuns3Four-week average36kmFreshnessSteady
29% above your four-week average.
Heart-rate costEstimated
Not yet: the heart-rate cost at the same pace compares the fresh heart-rate curve across two three-week windows, and that comparison is not built.
One change waiting
Not yet: the change waiting, next week's key session and sending the week to your watch all come with a plan, and none is stored.
The week’s key sessionThursday 15 October, 30km long run in 3:04:29 at 149bpm.
What moved
Not yet: the forecast's move this week, the aims' progress and the change waiting for you, which come with a forecast frozen run by run, a block with its aims set and a plan.
Not yet: the forecast's move this week comes with a forecast frozen run by run.
Not yet: the aims' progress comes with a block with its aims set.
Not yet: the change waiting for you comes with a plan.
Focus reviewWeek 8
Not yet: Your focus is the one thing most holding your racing back, priced in race time. Nothing ranks your axes against a race yet, so there is no focus to name.
Month in reviewThursday 1 October 2026

September.

The month
73Kilometres
7Hours
6Runs

August: 184 kilometres.

The month’s start against its end
Not yet: your radar as it stood on 1 September and on its last day is not drawn: the radar is built for today, and the weekly replay keeps each axis's score, not a radar.
Your aims
Not yet: Aims are set with a block, each with a start, a target and a check date. None is set yet.
Weekly volume12 weeks to 27 September
0
0
20
53
45
36
50
42
0
0
8
54
Four-week average, 15.5km · longest run 24km, 25 SeptemberTotals are never judged.
Bests and soft bests

No new bests in September. Your 1K best, 4:15, is about 23 seconds soft against your current fitness.

1K4:15
● your best · dashed: your current fitness, estimated
The session of the monthFriday 25 September
24km long run in 2:26:39.

The highest load of the month.

What the month held

6 runs, among them 1 interval session, 1 tempo or threshold run and 1 long run, and runs up to 24km.

NotableYour longest run since Saturday 29 August.
Next month
Not yet: October's focus comes with a ranking of your axes against your goal.
ShareNot yet: every number a card from this would carry is provisional, and a card is an image that travels without the sentence that says so.
Focus reviewSeptember
Not yet: Your focus is the one thing most holding your racing back, priced in race time. Nothing ranks your axes against a race yet, so there is no focus to name.
Year in reviewThursday 1 January 2026

2025.

Not yet: the type you ended the year as is not drawn: a type is read for today, and the weekly replay keeps each axis's score, not a type.
31Runs
30Hours
293Kilometres
457Metres up (source not stored)
Weekly volume14 weeks · 293km
JanAprJulOctDec
Totals are never judged.
The shape of the year
JFMAMJJASONDNot yet: the blocks of your year are not drawn: nothing names a block but the sixteen weeks before a race goal, so only the races are marked.
So who did you become?
January against December
Not yet: your radar as it stood at the year's start and at its end is not drawn: the radar is built for today, and the weekly replay keeps each axis's score, not a radar.
Your shape, March and October
Not yet: your shape at two points in the year is not drawn: the radar is built for today, and the weekly replay keeps each axis's score, not a radar.
And the races?
Every race
Not yet: no run in 2025 is a race: a race is what its source marks, or what you confirm.
The best-executed race
Not yet: the best-executed race is not named: it needs an execution score for every race, and there is none yet.
How the forecasts did
Not yet: how the forecasts did is not shown: no forecast is stored before its race, so none can be checked against the result.
What were you aiming at?
Every aim this year
Not yet: Aims are set with a block, each with a start, a target and a check date. None is set yet.
The aim that mattered most
Not yet: the aim that mattered most needs aims, and none is set yet.
And the best day?
The session of the year
Saturday 11 October11km easy run in 1:07:49.The highest load of the year.
The year’s bests
Not yet: no best was set in 2025.
So what's next?
Badges earned this year
Not yet: no badge is shown as earned: a badge is awarded only once the quantities it reads are proved, and every one is provisional.
Where you sit
Not yet: where you sat over the year is not drawn: the cohort ranks your weekly volume as it is now, and the comparable runners are read against today's goal.
Next year’s question
Not yet: next year's question is not asked: it is your focus priced for next year, and nothing ranks your axes against a race yet.
The share set
Not yet: the year's cards rest on what is not built yet: the best-executed race, the aims and the runners like you. The year in one card carries your type and level, and they are provisional, so it would travel as a claim nobody can check.
Focus review2025
Not yet: Your focus is the one thing most holding your racing back, priced in race time. Nothing ranks your axes against a race yet, so there is no focus to name.
Built on 1 measured, 2 derived and 7 estimated numbers
Before the race

Thames Valley Marathon.

56 days. Everything here points at one number.

Monday 19 October 2026Race: Monday 14 December
Your goal · sub-3:21
The blockEight weeks
17Sessions
246Kilometres
24Hours on feet
Not yet: the block's climbing is not stated: too little of it is surveyed, and a wrist barometer over-reports it by about half again.
Race week
Not yet: your radar, the block start, what moved since and the share card, which come with a profile scored with this report, a radar scored as of the block's start and the share sheet.
Not yet: your radar comes with a profile scored with this report.
Not yet: the block start comes with a radar scored as of the block's start.
Not yet: what moved since comes with a radar scored as of the block's start.
Not yet: the share card comes with the share sheet.
Your aims, scored
Not yet: Aims are set with a block, each with a start, a target and a check date. None is set yet.
The sessions that built it
The longest runSaturday 29 August
42.2km
The one that mattered mostSaturday 29 August
42.2km race, the longest too.The highest load of the block.
Bests in the block
10KSaturday 29 August44:43Set in the block.
Half marathonSaturday 29 August1:34:20Set in the block.
Taper state
PeakDown 81%FreshnessWeek 1This week

Load down 81% from peak. Freshness falling.

Not yet: the fuel you practised on your long runs is not kept: no intake is stored with a run.
Your race.

Your race is in 56 days.

End of act 1So what are you about to face?
Built on 1 measured, 2 derived and 7 estimated numbers
The course
Not yet: the course was given as a total climb, so where the hills are is modelled rather than measured, and the profile is not drawn.
Where it will hurt
Not yet: the course was given as a total climb, so where the hills are is modelled rather than measured, and the profile is not drawn.
Conditions
Not yet: race-morning conditions need a forecast for the race, and the weather here is the past only: the temperatures your runs were run in.
End of act 2So what happens?
Built on 1 measured, 2 derived and 7 estimated numbers
The outcome: your finish range
3:003:153:303:454:004:15Goal, 3:21Top 5%Bottom 5%Strong3:34Expected3:34Tough3:35Failure3:36
about1 in 5for sub-3:21.
The exact figure

18 in 100 of your finish range is under 3:21.

Eight in ten finish between 3:16 and 3:52, most likely about 3:34. Failure is pushing on past 11km once your form goes.

This forecast hasn't yet been checked against your own races.

Ceiling: Not drawn: the aerobic ceiling is a capacity rather than a race, and no forecast reads it (decision 0056). It is in the physiology drawer.
Separately: the field200 runners started from a profile like yours. 31 broke 3:21.
The planMonday 14 December
Splits per km on an expected day, faster is tallerGoal: 4:46/km
StartHalfFinish
Heart-rate ceiling, ExpectedStay below 156bpm through the first 15km. Going over this early is the single most common way to lose time later.
FuellingNot yet: The section-by-section plan is only built for courses with published aid-station positions, and this course isn't one of them. A fuelling plan built on guessed water positions is worse than none, because a runner would act on it.
Fallback ladderNot yet: the fallback ladder steps from one scenario to the next on heart rate and pace at named kilometres, and nothing computes those triggers yet.

To break 3:21, your first half must be 1:40:30.

Not yet: race week's card sets an axis beside its score at the block start, and a report scores you once, so it has no block start to set it beside.

Good luck. The race review arrives when your file does.

Your aims
Not yet: Aims are set with a block, each with a start, a target and a check date. None is set yet.

Strengths

What your data says you're genuinely good at.

Threshold pace comfortably ahead of the goal

Your threshold pace is 4:16/km. The goal implies a threshold of about 4:27/km, so you're carrying a 10 second per kilometre buffer. That margin is what absorbs a warm day, a headwind, or a bad patch mid-race.

Long run built patiently

Your long run grew from 24.0km on 8 July to 42.2km on 8 August across 7 long runs — progressive overload done at a rate that builds tissue rather than breaking it.

Improvement areas

Ranked by how much each one actually costs you against this specific goal, at this specific distance.

#1

Structural load tolerance is still building

Accumulated lifetime load is the slowest-moving input in the model — tendon, bone and connective tissue adapt over years, not training blocks, and this is the one limiter you cannot rush.

The fix

Don't try to fix this before the race. Hold volume steady, keep the easy running genuinely easy at 5:23/km or slower, and treat consistency over the next months as the intervention.

#2

VO2max is short of what the goal needs

The goal requires a VO2max of about 47.0, and your current estimate sits below that. VO2max responds faster than any other input on this list, which is what makes it worth attacking directly.

The fix

You've done 2 interval sessions in the last 6 weeks. Add one a week: 5-6 × 3 minutes at 4:02/km with 2-3 minutes jog recovery. Expect a measurable shift in 4-6 weeks.

#3

Threshold pace is the binding constraint

Threshold work is the highest-leverage input for this distance and it's underweighted in your recent training.

The fix

You've done 1 threshold or tempo session in the last 6 weeks. Add one a week: 20-25 minutes continuous at 4:27/km, or 3 × 8 minutes at that pace with 2 minutes easy between. This is the single change that most directly closes the gap.

Race day

Kilometre by kilometre through Thames Valley Marathon, using your durability profile, cardiac drift, and the course elevation.

Predicted finish

3:33:43

3:15:37 – 3:51:48 range

Confidence

High

anchored to a real result at this distance

Versus your goal

+12:43

outside your target

Cost of the course

+0:01

80m climb, 80m descent

Cost of fatigue

+0:12

fade begins around km 32

Estimated from your races and your running

3:30:06

4:59/km

high confidence

Range 3:15:36 – 3:44:42, from your race and training projections.

What it rests on

Your fastest race and your fastest sustained running, each carried to this distance. A race stands unless your training says faster, and then the race still carries five-eighths of the figure.

SourceSuggestsWeightWhy it carries that weight
Your training datahigh3:44:4230%The pace you hold at 83% of heart-rate reserve, carried out to race duration.
Your race historyhigh3:15:3650%Your Marathon in 3:15:36, converted using ratios measured from population athletes who raced both distances.
Economy-adjusted ceilinglow3:44:2920%VO2max 48.4 multiplied by an assumed 85% economy, since yours cannot be measured without a race result, giving an effective 41.1. The conservative bound.

How it was carried to the distance

StepCostWhat it means
Pace you hold at 83% of heart-rate reserve—5:01/km, measured across 135 minutes of your own sustained efforts either side of this intensity. That is 3:31:21 for 42.20km before anything else.
Holding it for race duration+13:20Those efforts lasted about 27 minutes; this race asks for 225. Pace at a fixed heart rate decays about 1.9% per hour for you, from 6.5bpm/hour of measured cardiac drift, adjusted by your durability of 64/100.

Checked against your race history

Training data predicts 3:44:42. Your Marathon in 3:15:36 suggests 3:15:36 — faster than your current training supports. Racing brings out more than training does, but a gap this way round can also mean the training block has been easier than the one that produced the race.

Your pace at each intensity

Every sustained effort in your training, grouped by how hard it was as a share of your heart-rate reserve. Shown beside the estimate rather than inside it: the estimate rests on what you have run, and this curve on what each heart rate costs you.

Where the hard parts are

No route geometry for this course. Upload the race GPX to see the course on a map — the elevation profile below is modelled from the total climb you entered.

Course elevation

Hovering the map highlights the same point on the charts, and vice versa. Elevation and pace share a kilometre axis rather than being stacked on two y-scales, which would distort both. The pace axis is inverted so a falling line means slowing down.

The five hardest kilometres, and what to do in them

  • km 35 · 5:16/km (+19s vs your opening km)

    accumulated fatigue — ground contact rising to 229ms.

    Hold cadence above 165spm through this section. Form goes before fitness does, and cadence is the part you can consciously keep.

  • km 36 · 5:20/km (+23s vs your opening km)

    accumulated fatigue — ground contact rising to 230ms.

    Hold cadence above 165spm through this section. Form goes before fitness does, and cadence is the part you can consciously keep.

  • km 37 · 5:21/km (+23s vs your opening km)

    accumulated fatigue — ground contact rising to 230ms.

    Hold cadence above 165spm through this section. Form goes before fitness does, and cadence is the part you can consciously keep.

  • km 38 · 5:18/km (+21s vs your opening km)

    accumulated fatigue — ground contact rising to 229ms.

    Hold cadence above 165spm through this section. Form goes before fitness does, and cadence is the part you can consciously keep.

  • km 42 · 5:17/km (+20s vs your opening km)

    accumulated fatigue — ground contact rising to 227ms.

    Hold cadence above 165spm through this section. Form goes before fitness does, and cadence is the part you can consciously keep.

Predicted splits

Tap any kilometre to see why it's predicted at that pace.

KmPaceHRGCTElevationElapsedNote
14:57156232ms+1m4:57
25:00157233ms+3m9:57
35:01158233ms+4m14:58
44:58158231ms+2m19:57
54:54158229ms−1m24:51
64:51159227ms−3m29:41
74:50159226ms−4m34:31
84:52160227ms−2m39:23
94:56161229ms+0m44:20
105:01161230ms+3m49:20
115:03162231ms+4m54:23
125:02163230ms+3m59:25
134:58163228ms+0m1:04:23
144:54163226ms−2m1:09:17
154:52164225ms−4m1:14:09
164:54164225ms−3m1:19:03
174:57165226ms−1m1:24:00
185:02166228ms+2m1:29:03
195:06166230ms+3m1:34:09
205:06167229ms+3m1:39:15
215:04167228ms+2m1:44:19
225:00168226ms−1m1:49:19
234:57168224ms−3m1:54:17
244:57169224ms−4m1:59:14
255:01169225ms−2m2:04:15
265:06170227ms+0m2:09:20
275:10170229ms+3m2:14:31
285:13170229ms+4m2:19:43
295:12170229ms+3m2:24:55
305:08170227ms+0m2:30:03
315:05170225ms−2m2:35:08
325:04170224ms−4m2:40:11
335:06170225ms−3m2:45:17
345:11170227ms−1m2:50:28
355:16170229ms+2m2:55:44
365:20170230ms+4m3:01:04
375:21170230ms+3m3:06:24
385:18170229ms+1m3:11:42Fatigue starting to bite — hold form, not pace
395:15170227ms−1m3:16:57Fatigue starting to bite — hold form, not pace
405:12170225ms−3m3:22:10Fatigue starting to bite — hold form, not pace
415:13170225ms−4m3:27:23Fatigue starting to bite — hold form, not pace
425:17170227ms−2m3:32:40Fatigue starting to bite — hold form, not pace
final 195m5:20170228ms−0m3:33:43Fatigue starting to bite — hold form, not pace

What this model assumes

  • · Baseline pace comes from your own pace-to-heart-rate curve — the pace you actually hold at race intensity — rather than from a table. For reference, inverting your VO2max through Daniels' tables would have predicted 3:15:36; the difference between the two is your running economy.
  • · Fade modelled from your durability score of 64/100 across 7 long runs.
  • · Race-day 18°C against your 13°C training average: about +5bpm at the same effort, costing roughly 1.6% in pace.
  • · Heart rate column uses your measured cardiac drift of 6.5bpm per hour at steady effort.
  • · Heart rate is held at 170bpm from km 27 — 88% of your 193bpm max, about the highest anyone sustains for this distance. Drift beyond that point shows up as 0s of lost time rather than a higher number on your watch.
  • · High confidence — you have raced this distance before, so the prediction is anchored to a real result rather than extrapolated.
  • · No GPX supplied, so the 80m of climbing is spread across the course using a typical "rolling" shape. Total elevation is yours; where it falls is modelled.
  • · Goal of 12060s sits at the 18% point of this distribution.

Your pacing plan

Even split — targeting 3:21:00.

Your durability of 64/100 says your mechanics start giving way before the end of a long effort, so the plan is an even split rather than a fast finish. Going out slower to bank a negative split asks for speed at exactly the point your form is least able to produce it — hold target pace from early and spend what is left in the last kilometre.

First half

1:40:30

Second half

1:40:30

Split differential

0:00

even split

Target splits

SplitTarget paceHR ceilingElevationHow it should feel
0-5km4:46/km156+9mSettle straight onto target pace — no time to bank anything.
5-10km4:46/km159−6mSettle straight onto target pace — no time to bank anything.
10-15km4:46/km163+1mLocked on target pace. Check in on breathing rather than the watch.
15-20km4:46/km166+4mLocked on target pace. Check in on breathing rather than the watch.
20-25km4:46/km169−8mLocked on target pace. Check in on breathing rather than the watch.
25-30km4:46/km170+10mLocked on target pace. Check in on breathing rather than the watch.
30-35km4:46/km170−8mLocked on target pace. Check in on breathing rather than the watch.
35-40km4:46/km170+3mThis is where the race is decided. Hold form and cadence; the pace follows.
40-42.2km4:46/km170−5mThis is where the race is decided. Hold form and cadence; the pace follows.

Heart rate

  • · Stay below 156bpm through the first 15km. Going over this early is the single most common way to lose time later.
  • · By the closing kilometres, 170bpm is acceptable — heart rate rises at the same effort as the race goes on, so a rising number is expected, not a warning.
  • · 170bpm is the ceiling, and it does not move — that is roughly 88% of your 193bpm max, about the highest anyone holds for this distance. If you are there and still climbing, the answer is to ease the pace, not to accept the heart rate: past this point a higher number buys you nothing and costs you the finish.
  • · Your measured cardiac drift is 6.5bpm per hour on long runs. That is what these rising ceilings are built from.

When to push

  • · Do not push before km 32. That's where the model expects fatigue to start showing in your pace, and anything spent earlier comes out of that section.
  • · Final commitment point: km 38. From there it's 4.2km — close enough that going into the red can't cost you a blow-up.

Fuelling

WhenWhat
3 days beforeBegin carb loading: 8-10g carbohydrate per kg bodyweight daily while training volume drops.
3 hours before2-3g carbohydrate per kg bodyweight. Practised breakfast only.
45-60 min before3mg/kg caffeine.
From km 8, every 25-30 minGel with water — roughly 8 across the race, 60-90g carbohydrate per hour.
km 30-32Take a gel here even if you don't feel like it. This is where under-fuelled marathons end.
ThroughoutWater to thirst; electrolyte if it's warm or you're a heavy salt sweater.

The marathon is the only one of these distances where fuelling genuinely decides the outcome. Every gel timing above should be rehearsed in a long run before race day, not tried for the first time.

Comparable runners

200 male runners aged 35 - 54 with training like yours who raced a marathon, matched on weekly volume, longest run, session frequency and average pace.

Their median finish

3:57

Reached your goal

31 of 200

16% of similar runners

Achievers' average

3:07

among those who hit it

What the ones who hit the goal did differently

Weekly volume35.8 → 40.9km/week

Runners with your profile who beat this goal trained 5km/week more than you — 41km/week against your 36km/week.

Longest run42.2 → 35.6km

Their longest run averaged 36km against your 42km.

Session frequency2.6 → 3.0sessions/week

They ran 3.0 times a week against your 2.6 — the gap is frequency more than it is any single hard session.

Training disruptions0.2 → 0.1interruptions

Runners who hit this goal averaged 0.1 interruptions to their build against 0.2 for those who missed it. Consistency separated them more than volume did.

The closest 8 runners to you

Marathon timeWeekly kmLongest runSessions/wkDisruptions
3:5836432.80
3:4938422.80
4:5940432.50
3:5739432.60
4:2835432.20
4:2138423.00
4:1035362.71
3:4039422.81

Green rows reached the equivalent of your goal.

Training load and injury risk

Your acute:chronic workload ratio against the observed disruption rates of 18,000+ marathon builds.

Current ACWR

1.59

1.5-2.0 (danger)

Disruption rate in this zone

32%

of 419 runners

Week-on-week change

-77%

most recent week's volume

Volume bracket risk

8%

at 40-50km/week — your last 4 complete weeks average 46km, which is the acute window this ratio is built on

Your ACWR is 1.59 — the 1.5-2.0 (danger) zone. Across 419 runners in the population dataset, 32% of those training in this zone experienced a disruption to their build.

Reduce volume by about 10% next week. At this ratio the disruption rate is materially above baseline, and a week lost to a niggle costs far more than a week of slightly reduced training.

Acute:chronic workload ratio over time

Green band is the productive range. Amber begins at 1.3, where the observed disruption rate starts to climb; red at 1.5. The first six weeks are omitted — the chronic side of the ratio needs that long before it means anything. The lowest observed disruption rate in the dataset is 12% in the <0.8 (under) zone.

Race readiness timeline

56 days until Thames Valley Marathon on Monday 23 November — that's 8.0 weeks.

This week

Your weakest input for this goal is structural load tolerance (17% of what the goal needs). With 8 weeks to go, hold volume steady rather than increasing it — accumulated load builds over months, and pushing now buys injury risk, not fitness.

Base and buildYou are here

42-Infinity days out
  • · Grow weekly volume by no more than 10% a week, with a down week every fourth week.
  • · Two quality sessions a week maximum: one threshold, one VO2max or hills.
  • · Extend the long run steadily — this is the only window where that's still safe.
  • · Specific to you: hold volume steady rather than increasing it — accumulated load builds over months, and pushing now buys injury risk, not fitness.

Race-specific block

14-42 days out
  • · Shift quality work towards Marathon pace specifically.
  • · Practise race-pace running inside long runs, and rehearse race-day fuelling exactly as you'll do it.
  • · Peak weekly volume lands in this window, roughly 3-4 weeks before the race.
  • · Do a dress rehearsal: race kit, race shoes, race breakfast, race-morning timings.

Taper

7-14 days out
  • · Cut volume by about 25% this week while keeping intensity — the sessions stay sharp, they just get shorter.
  • · Keep session frequency identical. Dropping runs entirely feels restful and leaves you flat.
  • · Expect to feel sluggish. That is the taper working, not fitness disappearing.

Final 7 days

3-7 days out
  • · Volume down to roughly 50% of peak. One short session at race pace (about 15-20 minutes' worth) around 4-5 days out.
  • · Last genuinely hard effort: 4 days before. Nothing after that improves fitness.
  • · Sleep is the highest-value thing you can do this week — prioritise the nights from 5 days out, not just the last one.
  • · Confirm logistics: travel, start time, bag drop, where you'll warm up.

3 days out

1-3 days out
  • · Start carb loading now: 8-10g carbohydrate per kg bodyweight daily, with training volume near zero. This is worth 2-3 minutes over the marathon distance.
  • · Easy 20-30 minutes with a few strides, or complete rest. Both are fine.
  • · Hydrate steadily across the day rather than drinking heavily the night before.
  • · Lay out everything the night before: kit, number, gels, shoes, charged watch.

Race morning

-1-1 days out
  • · Wake 3 hours before the gun.
  • · Breakfast 2.5-3 hours out: 1.5-2g carbohydrate per kg bodyweight, all of it familiar.
  • · Caffeine 45-60 minutes before the start, around 3mg/kg.
  • · Short warm-up only: 10 minutes easy and a few strides. The first 3km is the rest of your warm-up.
  • · Be at the start pen 20 minutes early — rushing costs more than the warm-up gains.

Goal assessment

3:21:00 for Marathon at Thames Valley Marathon.

Probability of hitting the goal

18%

Uncalibrated: no prediction this app has made has yet been paired with a result, so nothing says how often a figure like this one is right.

For the marathon, structural readiness, durability and long-run coverage together outweigh raw VO2max — past about 30km the limiter is rarely the engine.

Predicted finish distribution

3:15:37

Best case (p10)

3:33:43

Median (p50)

3:51:48

Worst case (p90)

On this course

Your flat-course estimate
3:30:06
Climbs and descents
+1s
Surfaces
±0s
The course's cost
+1s
The day and the distance: the late fade and the temperature
+3:35
Course-adjusted finish
3:33:43

The course-adjusted figure is your flat estimate plus the course's cost, and what the day and the distance add. The course's cost is priced from your own running where it is measured: each climb and descent half from the physics of running on that slope and half from your own training pace on that gradient (physics alone where your training does not measure it), each surface at your own measured cost (the published figure where you have not run on it), and ground steeper than you walk from at your own walking pace.

What's helping and what's hurting

VO2max sufficiency18% weight42%
Threshold gap18% weight60%
Durability at race distance14% weight64%
Structural readiness18% weightweakest link17%
Long run readiness14% weight100%
Consistency5% weight100%
Time readiness5% weight60%
Terrain readiness8% weight—

Terrain readiness is unscored. No measured elevation profile for this course. Its weight has been spread across the components that could be measured rather than counted against you.

Structural readiness is the component most likely to decide this race: a goal needs every input that matters for the distance to be sufficient at the same time, not just a good average across them. The percentage above is read off the modelled finish-time distribution — it is the share of simulated races that come in under your target — so this is the input to work on rather than a penalty already applied to that number.

Against the population

  • · Your 36km/week over the last 12 weeks puts you in the 27th percentile for training volume among 500 male runners aged 35 - 54.
  • · Against 500 male runners aged 35 - 54, this goal would place you in the top 30%.

Recommendations

The specific changes worth making, ranked by impact.

Written recommendations haven't been generated for this report yet.

1

Structural load tolerance is still building

Don't try to fix this before the race. Hold volume steady, keep the easy running genuinely easy at 5:23/km or slower, and treat consistency over the next months as the intervention.

2

VO2max is short of what the goal needs

You've done 2 interval sessions in the last 6 weeks. Add one a week: 5-6 × 3 minutes at 4:02/km with 2-3 minutes jog recovery. Expect a measurable shift in 4-6 weeks.

3

Threshold pace is the binding constraint

You've done 1 threshold or tempo session in the last 6 weeks. Add one a week: 20-25 minutes continuous at 4:27/km, or 3 × 8 minutes at that pace with 2 minutes easy between. This is the single change that most directly closes the gap.

Generated by Iteros from 75 sessions. Race times come from your own races and your 3-20 minute bests; climbs and descents are priced at your own measured uphill and downhill costs, and at Minetti's cost-of-running curve scaled to what a sustained climb realises where yours are unmeasured; population comparisons draw on a dataset of marathon training builds. Predictions are models, not promises — they describe what your data suggests, not what will happen.

Generate another report

Surface and route data © OpenStreetMap contributors, licensed under the ODbL. Elevation data © Environment Agency, Open Government Licence v3.