Boston Marathon 2026 · Race Report

I built the pace guide.
Then I ran the plan.

This page started as a Boston pacing resource: course profile, weather, fueling, spectator logistics, and grade-adjusted mile targets for a 3:05:30 goal. After race day, I pulled the Strava splits and compared each mile against the calculator.

Read the race note

Finish

3:07:05

official

Goal

3:05:30

+1:35 / 0.9%

Strava GPS

26.45 mi

3:06:52 moving

Within 3%

20/26

14/26 within 2%

Mean abs diff

2.4%

mile pace vs target

Pace control

The useful part was not one perfect pace. It was permission to vary.

Flat 7:03 pace would have been the wrong instruction for Boston. The first pass wanted to reward the opening downhill too much, so I challenged it and kept a race-day guardrail: around 7:10 for the first four miles, then judge the rest against the mile I was actually in.

Opening guardrail

7:10

First 4 actual avg 7:06 (-1.0% vs guardrail)

Most slower than target

Mile 1

7:14 vs 6:43 target (+7.7%)

Most faster than target

Mile 16

6:46 vs 7:38 target (-11.4%)

Closing miles

+1.3%

average signed pace delta, miles 22-26

Course map + elevation

Where the speed was controlled, taxed, and earned

■ faster than target■ slower than target■ restraint zone

First 4 miles

7:06 avg

The public story: restraint. The guardrail was 7:10, not banking the downhill.

Newton miles

7:12 avg

Target averaged 7:23 here, so the hill tax was expected instead of surprising.

Granularity

1-mile bins

Each shaded band is one GPS mile, so the elevation, target, actual split, and percent miss line up.

Capacity growth model

What has to become true before Chicago

Sub-3 is not proven by listing the intended workouts. It becomes believable when the same pace costs less, the body holds form late, and the mind can stay patient before choosing pressure.

Cycle runway

25 wk

Boston to Chicago: 174 days

Sub-3 ask

-7:06

3.8% faster than Boston

Per-mile shift

-16s/mi

7:08 to 6:52

Intended build

15 wk

60 mi peak is input, not proof

Late diff

2.9%

mean abs diff, miles 20-26

Belief evidence

6:44

mile 23 after Heartbreak

Max exposure

900 mi

only if every week hit 60

Finish projection ladder

Percent improvement from Boston official time

3:07:05

What must be true for sub-3

This separates planned work from the evidence that would make the attempt rational.

Feasible if the build changes cost, not just confidence

Real gap

-7:06

3.8% faster than Boston, or about 16 seconds per mile. This is plausible, not casual.

Fitness gate

6:52/mi

Marathon pace needs to feel controlled after 90-120 minutes, with less HR drift and less form decay than Boston.

Validation race

1:26:20

A tune-up near this half-marathon equivalent, or roughly 39:09 for 10K, would make the attempt more evidence-based.

Belief case

M23 6:44

You found 6:44/mi after Heartbreak. Mile 24 was 6:57/mi at 167 bpm.

Risk gate

durability

The miss mode is not speed. It is carrying the speed from 18-26 without glycogen, heat, mechanics, or confidence unraveling.

Mental skill

patient pressure

The sub-3 version is boring early, emotionally neutral through halfway, then aggressive only when the course and body have earned it.

Physiology

The science case is aerobic capacity, threshold fraction, running economy, and durability improving enough that 6:52/mi is not redline effort.

Course translation

Chicago helps because rhythm is simpler than Boston, but the flat course only matters if fueling, heat control, and late mechanics survive.

Mental execution

Belief is useful when it is rehearsed: hold back early, tolerate boring, fuel on schedule, and decide again after 20.

Practical projection: with a healthy uninterrupted cycle, a fact-forward Chicago band is roughly 3:01:28-3:03:21. The stronger claim is not "the plan says yes"; it is "the gap is only 7:06, the course is friendlier, and Boston already showed late-speed evidence." Sub-3 becomes a real attempt if the build produces lower drift, cleaner fueling, and calm decision-making at marathon pace. The 2026 Chicago Marathon date is listed by the event as October 11, 2026.

Science links

Performance predictorsVO2/vVO2, training load and pace, body composition, and lab variables show up in long-distance prediction models.DurabilityMarathoners lose threshold and economy markers under prolonged running; resisting that decay matters.Training responseLarge app-data study linking marathon outcomes to training distribution and low-intensity volume.Taper executionStrict longer tapers in recreational marathoners were associated with better race performance.Weather costTemperature was the main environmental factor associated with marathon performance.Boston cohortBoston Marathon study on training volume and frequency changes around race performance.Self-efficacySystematic review and meta-analysis on pre-event self-efficacy and sport performance.

Actual vs calculator pace

Percent difference by mile

■ slower than target■ faster than target

Body under load

The race was not just a pace story. The physiology was loud.

Strava shows the acute cost of the run. Oura shows the day-level readiness and recovery context around it. Together they make the post more credible: the tool helped control pace while the body still absorbed a very real marathon load.

Relative effort

621

Strava load score

Heart rate

173/184

avg/max bpm

GPS gain

1,619 ft

Boston course by Strava

Race-day steps

47,963

Oura daily total

Readiness

57 ms HRV race day

Sleep score

6h 19m

Peak mile HR

Mile 15

180 bpm average at 7:01/mi, right before the Newton sequence became the main limiter.

Fastest late mile

Mile 23

6:44/mi at 173 bpm after Heartbreak, which is the best evidence the course-aware plan left room to run.

Downhill reset

167 bpm

Mile 24 was 6:57/mi while average HR dropped, making the post-BC downhill visible in the data.

Two-day rebound

Oura readiness on April 22, with 72 ms HRV after the immediate post-race dip.

Oura activity

Oura calories

3,774

Active calories

2,149

Sources: Strava activity 18221431328, fetched April 24, 2026; Oura daily timeline synced April 24, 2026. Oura values are day-level aggregates, not second-by-second race telemetry.

Miles 1-10

Opening 10

+0.4%

1.9% mean absolute diff

Miles 11-15

Settle

+0.2%

1.5% mean absolute diff

Miles 16-21

Newton

-2.4%

3.5% mean absolute diff

Miles 22-26