Net result
1:37:30
Linz Half Marathon 2026
Linz Half Marathon 2026: 1:37:30, controlled to the line.
On April 12, 2026, the official result, the planned PaceMaker workout, and the Garmin execution all point in the same direction: the race stayed controlled long enough to keep late reserve available.
Gross result
1:37:52
Placement
595 overall
Verdict
Controlled to the line
The important part is not that the day was perfect. It is that the race never had to be rescued from a pacing collapse.
This retrospective keeps the evidence together: the plan, the official outcome, the watch-recorded execution, and the comparison that shows where the late reserve came from.
April 12, 2026Net 1:37:30595 overallFinal 5K held in reserve
Outcome snapshot
Official result
1:37:30
Net time, controlled rather than desperate.
Planned finish
1:37:44
The plan left enough reserve to finish faster than target.
Garmin activity
1:37:35
Recorded trace stayed close to the planned execution.
Verdict
Controlled to the line
No late-race rescue needed; the finish still had a gear.
Plan
What the plan was
The target was 1:38:00 from a recent 10K of 44:12, with light wind and a course that rewarded staying honest instead of chasing pace.
Target time
1:38:00
Recent 10K
44:12
Wind
3.3 kph at 193°
Planned finish
1:37:44
The job was not to win minutes early. It was to keep the final 5K honest enough that a finish move would still be optional.
Reality
What actually happened
The race felt controlled rather than desperate, with effort living near the edge of Zone 3 and Zone 4 for most of the run.
Official result
Net 1:37:30, gross 1:37:52, 595 overall
Official splits
5K 23:08, 10K 45:54, 20K 1:32:30, finish 1:37:30
Race feel
Controlled rather than desperate, with effort hovering around the edge of Zone 3 / Zone 4.
Noise in the data
Autolaps fired about 50m early, so the handwritten milestone fallback kept the pacing honest after 10K.
Comparison
Plan vs reality
The checkpoints tell the story cleanly: slightly behind early, almost exact at 10K, slightly ahead at 20K, and ahead again at the finish.
| Checkpoint | Planned | Actual | Delta |
|---|---|---|---|
| 5K | 22:54 | 23:08 | 14s behind |
| 10K | 45:51 | 45:54 | 3s behind |
| 20K | 1:32:34 | 1:32:30 | 4s ahead |
| Finish | 1:37:44 | 1:37:30 | 14s ahead |
Takeaways
What future Linz runners should do
The best part of the result is the part another runner can reuse in a Linz Half Marathon pacing plan. These are the practical rules the page should leave behind.
Takeaway 1
Start slightly more conservative than your ego wants so the final 5K still has a job to do.
Takeaway 2
Treat the pace band as the decision rule, not one exact number that has to be defended all race.
Takeaway 3
Keep a manual milestone fallback in reserve if watch laps drift away from the official markers.
Takeaway 4
On a flat, light-wind course, the product value is discipline, mental offload, and reserve management.
Proof
Proof: plan vs execution
The official result anchors the race outcome, the Garmin trace shows what the watch recorded, and the PaceMaker workout explains what was planned step by step.
Official anchors
- Net result: 1:37:30
- Gross result: 1:37:52
- Placement: 548 M/W, 65 AK, 595 overall
- Key splits: 5K 23:08, 10K 45:54, 20K 1:32:30, finish 1:37:30
Plan evidence
- Target time: 1:38:00
- Planned finish: 1:37:44
- Workout length: 16 distance-based steps
- QA summary: 13 inside band, 3 faster than band, 0 slower than band
Trust notes
- Garmin activity: 1:37:35 and 21.23 km
- Autolaps fired about 50m early
- Manual milestone fallback kept the pace honest after 10K
- Light wind and a flat course made discipline the main value
| Step | Planned segment | Cue | Planned band | Actual pace | Margin | Read |
|---|---|---|---|---|---|---|
| 01 | 0.000-1.200 km | Keep it smooth | 4:45-4:34 /km | 4:40 /km | 5 s/km inside band | Controlled start, comfortably on script |
| 02 | 1.200-2.597 km | Keep it smooth | 4:36-4:30 /km | 4:35 /km | 1 s/km inside band | Stayed patient near the conservative edge |
| 03 | 2.597-3.680 km | Keep it smooth | 4:35-4:30 /km | 4:35 /km | 0 s/km inside band | Hit the slow edge exactly, still on plan |
| 04 | 3.680-5.650 km | Keep it smooth | 4:38-4:32 /km | 4:35 /km | 3 s/km inside band | Centered well inside the target band |
| 05 | 5.650-7.650 km | Stay controlled | 4:38-4:32 /km | 4:34 /km | 2 s/km inside band | Controlled, leaning slightly assertive |
| 06 | 7.650-8.100 km | Stay controlled | 4:39-4:33 /km | 4:33 /km | 0 s/km inside band | Touched the fast edge without overreaching |
| 07 | 8.100-9.950 km | Keep it smooth | 4:41-4:32 /km | 4:33 /km | 1 s/km inside band | Still disciplined as the race settled |
| 08 | 9.950-10.900 km | Stay controlled | 4:41-4:35 /km | 4:37 /km | 2 s/km inside band | Stayed controlled through the checkpoint step |
| 09 | 10.900-12.750 km | Keep it smooth | 4:41-4:35 /km | 4:39 /km | 2 s/km inside band | Slightly conservative, no sign of collapse |
| 10 | 12.750-13.850 km | Stay controlled | 4:43-4:37 /km | 4:39 /km | 2 s/km inside band | Back toward the quicker side of the band |
| 11 | 13.850-14.200 km | Keep it smooth | 4:49-4:37 /km | 4:44 /km | 5 s/km inside band | Short reset segment stayed composed |
| 12 | 14.200-16.100 km | Keep it smooth | 4:42-4:36 /km | 4:36 /km | 0 s/km inside band | Touched the fast edge cleanly |
| 13 | 16.100-16.450 km | Keep it smooth | 4:47-4:38 /km | 4:36 /km | 2 s/km faster than fast edge | First clear move above plan, still controlled |
| 14 | 16.450-18.200 km | Keep it smooth | 4:43-4:37 /km | 4:37 /km | 0 s/km inside band | Held the fast edge rather than backing off |
| 15 | 18.200-20.100 km | Keep it smooth | 4:51-4:40 /km | 4:38 /km | 2 s/km faster than fast edge | Pressed slightly faster with reserve still available |
| 16 | 20.100-21.154 km | Keep it smooth | 4:45-4:39 /km | 4:25 /km | 14 s/km faster than fast edge | Committed finish surge, well beyond plan band |
This was controlled execution with late reserve, not dramatic route optimization. On a flat, light-wind day, PaceMaker's value was discipline, mental offload, and a finish that still had a gear left.
Next start line
If you want to race Linz with the same control
Use the same planner flow to build a Linz plan that stays honest when the final 5K starts asking questions. It works as a Linz half marathon pacing strategy, not just a flat half marathon pace calculator.
FAQ
Frequently asked questions
Was the result on target?
Yes. The plan targeted 1:38:00 and the official net result was 1:37:30, which left late reserve available instead of forcing a rescue.
Did the Garmin trace match the official result exactly?
Not exactly. The Garmin activity recorded 1:37:35 over 21.23 km, which stayed close to the official result even though the watch laps drifted a little early.
Why does the page use charts instead of only prose?
Because the pace-band table and cumulative chart make the comparison honest: you can see the plan, the execution, and the late reserve without flattening them into one synthetic number.
Can I still build a Linz plan with PaceMaker?
Yes. The same planner-entry flow is still available if you want to build your own Linz Half Marathon pacing plan for a future start.
Is this just a half marathon pace calculator?
No. A flat half marathon pace calculator gives one average number; PaceMaker turns the Linz route, target time, terrain, and conditions into a route-aware pacing strategy.