⏵ Course guide · Altitude, waves, a stadium finish
BOLDERBoulder runs rolling through Boulder at roughly 5,280 feet of elevation, self-seeded across nearly 95 waves, finishing inside Folsom Field. I will walk you through the altitude and the wave system first, then give you a pacing plan that respects both, plus free tools to dial in your own numbers.
These facts come from bolderboulder.com, including a confirmed 2027 registration cycle. The exact 2027 first-wave clock time was not separately confirmed; confirm the current schedule on bolderboulder.com.
The terrain itself is rolling, not brutal, but it runs the entire way at roughly 5,280 feet of elevation, which is the real story of this course for most visiting runners.
Boulder sits a mile above sea level, and reduced oxygen availability at that elevation slows most unacclimated runners more than the rolling terrain itself. If you are traveling in from lower elevation, expect this race to feel harder at your normal effort than a 10K at home, even before accounting for the hills.
The course finishes inside Folsom Field, the University of Colorado's football stadium, closing out with a lap on the actual field in front of a crowd. It is a genuinely festive event too, with bands, slip-n-slides, and costumes along the way, plus a major Memorial Day military tribute.
Registration is open, but placement is not automatic: you seed yourself.
You choose your own wave by predicted finish time out of roughly 95 waves running from elite to walking pace. Be realistic, and if you are not altitude-acclimated, seed a bit more conservatively than your sea-level 10K time would suggest, since starting in a wave too fast for your actual race-day pace creates a worse experience than starting a wave back.
There is no reliable single number to translate a sea-level 10K pace to 5,280 feet; effort is the more honest guide.
Use the training-pace calculator to know your effort-based training zones, then hold those same effort levels on race day rather than chasing a specific time goal built at sea level. Accept that your actual pace may run slower here, and treat that as the honest cost of the altitude, not a fitness problem.
⏵ Free tools to pace this course
⏵ Train for it with Summit Line
Get a race-day plan built around YOUR fitness and an honest read on altitude. Summit Line reads your real training, builds a plan around effort rather than a stale sea-level pace, and helps you dial in race-day pacing so race day is something you execute, not guess at.
Yes, meaningfully, if you are not acclimated. Boulder sits at roughly 5,280 feet, and for visitors coming from sea level, reduced oxygen availability at that elevation typically slows race pace noticeably, often in the range of a slower-than-sea-level 10K time even at what feels like a normal effort. There is no reliable way to fully offset this in a few days of travel; the honest approach is to run by effort on race day rather than chasing your sea-level 10K pace.
You self-seed by predicted finish time when you register, choosing from roughly 95 waves that run from the fastest runners down to walkers. Be honest about your predicted pace, including an altitude adjustment if you are not acclimated, since seeding yourself too fast puts you in a wave that will pull you out faster than you should go, and seeding too slow means weaving through a lot of traffic.
It is one of the most memorable finishes in road racing: the course brings you into Folsom Field, the University of Colorado's football stadium, for the final stretch, with the crowd and the stadium atmosphere as a genuine payoff after the rolling, altitude-affected miles that came before it.
Run by effort, not by a flat pace target carried over from sea level. Use the training-pace calculator to understand your normal effort zones, then apply that same effort on race day and accept that your resulting pace may run slower than a sea-level 10K, especially if you arrive in Boulder within a day or two of the race rather than acclimating longer.
There is no single confirmed answer that fits every runner, since altitude acclimation varies by individual and by how much time you can spare. General altitude-training guidance suggests either racing within about 24 hours of arrival (before some of the worst effects set in) or arriving at least one to two weeks ahead for meaningful acclimation; a middle ground of two to four days often leaves runners feeling the effects without having adapted yet. Plan your travel with that tradeoff in mind rather than assuming a short trip removes the altitude penalty.
Link this guide
Race directors and clubs: link or embed this guide anywhere. It stays current.
<a href="https://runsummitline.com/guides/bolderboulder">The BOLDERBoulder course guide</a><iframe src="https://runsummitline.com/embed/race/bolderboulder" style="width:100%;max-width:420px;height:180px;border:0;" loading="lazy" title="BOLDERBoulder course guide by Summit Line"></iframe>This guide is independent and for planning only. The course details and entry rules come from public sources and can change year to year, so confirm the current specifics with the official race before you register or run. The pacing advice is general and not medical advice.