Flat does not mean free
Small early surges feel harmless on a fast profile until the final 10K asks for the bill.
BMW BERLIN-MARATHON 2026
Build your BMW BERLIN-MARATHON 2026 pacing plan.
Berlin is flat enough to invite overconfidence. PaceMaker turns the official course context, your target time, and race-day wind/weather inputs into route-aware pacing you can take to Garmin.
Use the PaceMaker-recreated Berlin route preload, replace it with your own GPX if needed, and execute the generated plan with Garmin-ready workout export plus the PaceMaker Race Field custom Data Field.
Build my Berlin pacing planSeptember 27, 2026Race-day wind inputsGarmin-ready exportPaceMaker Race Field
What you get
More than a finish-time split table
A PaceMaker plan shows where to hold back, where wind or route context changes the cost, and how much margin to protect before the final 10K.
Pacing risk
Why Berlin needs more than even splits
The official course page describes Berlin as the flattest Abbott World Marathon Major and gives the marathon distance as 42.195 km with very little elevation gain.
On a flat, fast profile, the pacing risk is less about surviving big climbs and more about spending small surges before they look expensive.
The historical weather read is similar: Berlin in September is usually breezy rather than extreme. Recent marathon race-window samples averaged about 10.5 km/h wind and leaned from SSW, about 199 deg, when speed-weighted across sampled hours; direction still varied by edition, with 2019 standing out as the gustier exception.
Course as of August 2025; historical weather is a planning baseline, not a race-day forecast.
Breezy still changes cost
Berlin is not a wind-tunnel story, and historical direction varies by edition, but race-day wind direction can still change the effort cost on a flat course.
The watch should help
The goal is a plan you can follow while racing, not an article you read once and forget.
Plan quality
What your PaceMaker plan gives you
PaceMaker is not a flat pace calculator. It builds the plan from the PaceMaker-recreated Berlin route, target, weather, wind, elevation context, and runner capability so the pacing guidance stays executable. For Berlin, wind should be an input, not the whole story.
Route-aware pacing
Start from the PaceMaker-recreated Berlin route, replace it with your own GPX if needed, then generate guidance that follows the course instead of one average pace.
Weather and wind context
Use race-day conditions so the plan can account for directional wind, route exposure, and effort cost.
Execution cues
Get segment-by-segment guidance for when to hold back, stay controlled, or spend effort deliberately.
Garmin execution
Execute the plan on Garmin
Your Berlin pacing plan should not stay in a browser tab. Export it as a Garmin-ready workout, then use PaceMaker Race Field for the watch-glance context that matters during the race.
Garmin workout export
Export the generated plan as a Garmin-ready workout so race guidance travels with you.
PaceMaker Race Field
With the custom Data Field, a PaceMaker Garmin FIT workout can show target pace, ahead/behind delta, cue, remaining distance, and next-step preview.
Native Garmin Run
Keep Garmin responsible for recording and familiar race controls while PaceMaker adds the pacing context Garmin does not show.
Source check
Course and weather sources
Berlin race and weather information can change, so PaceMaker keeps the facts source-backed, links organizer material rather than redistributing the official route file here, preloads a PaceMaker-recreated route with independent elevation data, and treats historical wind as context rather than a forecast. The official organizer GPX is linked for reference and does not embed elevation values.
Race date
September 27, 2026
Official distance
42.195 km
Course profile
Flat, fast, and low-elevation by official course framing
September wind
Usually breezy, not extreme: around 15-16 km/h climate average
Recent race window
Open-Meteo sample averaged about 10.5 km/h from 09:00-13:00
Sampled direction
Speed-weighted direction leaned from SSW, about 199 deg
Start planning
Build my Berlin pacing plan
Start PaceMaker with the Berlin route preload, replace it with your own GPX if needed, add race-day conditions, and create a plan you can export for Garmin race-day execution.
FAQ
Frequently asked questions
What official Berlin sources does this page use?
It uses the official BMW BERLIN-MARATHON home and course pages plus organizer-hosted GPX and elevation-profile links.
What route does PaceMaker preload for Berlin?
PaceMaker preloads a PaceMaker-recreated Berlin route with independent elevation data. It is not the official BMW BERLIN-MARATHON GPX file, and the official GPX source linked here does not embed elevation values.
How do weather and wind affect the pacing plan?
PaceMaker uses route, weather, wind, elevation context, target time, and runner capability so the plan can adjust effort where conditions change the cost.
Is the Berlin Marathon usually windy?
Usually it is better described as breezy than extreme: September climate averages sit around 15-16 km/h, while a recent race-window sample averaged about 10.5 km/h and leaned from SSW, about 199 deg, when speed-weighted across sampled hours. Direction varied by edition, so race-day forecast should drive pacing decisions.
Can I execute the plan on a Garmin watch?
Yes. PaceMaker exports Garmin-ready workouts, and PaceMaker Race Field can show target pace, ahead/behind delta, cue, remaining distance, and next-step preview on supported Garmin setup.