Race DNS Statistics 2026: Key Data

DNS - Did Not Start - means a runner registered, paid the entry fee, and then never crossed the starting line. At the Boston Marathon, the DNS rate averages around 9-10% in normal conditions, representing approximately 2,579 runners in 2011 alone. During the extreme heat of 2012, the DNS rate surged to 15.7% as 3,803 entrants never collected their bibs. Across the broader US running market, RunSignup's analysis of 97,000+ events found that just 3.1% of 2024 races with more than 500 participants did not take place in 2025 - the lowest event cancellation rate since tracking began in 2018. Injury and illness are the most frequently cited personal reasons for DNS decisions, but weather, travel disruptions, and deliberate strategic choices all contribute.

The gap between registration numbers and actual starters is a fixture of race planning that most runners never think about until they face the decision themselves. Understanding the DNS landscape helps race directors set expectations, helps runners make better decisions under pressure, and helps the running community understand how many people who want to race are being stopped from starting.

These 15 statistics map the DNS reality across road marathons, ultramarathons, and the broader running events industry.

1. Boston Marathon DNS Rate Was 9.5% in 2011

At the 2011 Boston Marathon, 2,579 of the 26,907 accepted entrants did not start. The 9.5% DNS rate was described as "fairly consistent across age groups," suggesting no single demographic carries a disproportionate dropout risk at registration. With fields at major marathons numbering in the tens of thousands, even a 10% DNS rate represents thousands of registered runners who never reach the start. For race operations, this means field size planning always builds in a DNS buffer.

Source: RunTri - Boston Marathon Entrants DNS DNF and Finishers

2. Extreme Heat Pushed Boston DNS Rate to 15.7% in 2012

The 2012 Boston Marathon was run in abnormally hot conditions. DNS climbed from 9.5% to 15.7% year-over-year, with 3,803 entrants not collecting their bibs or appearing at the start. Of 26,656 total entries, only approximately 22,480 started, compared to a more typical 24,000+ starters in normal weather years. Heat serves as both a direct deterrent (runners who decide conditions are too dangerous) and an indirect one, as it amplifies injury and illness in the training weeks before race day.

Source: RunTri - Boston Marathon Entrants DNS DNF and Finishers

3. Canadian Boston Entrants Showed a 9.9% DNS Rate in 2024

Detailed analysis of the 2024 Boston Marathon field found that Canadian participants had a DNS rate of 9.9%, with 1,537 of approximately 1,705 registered Canadian runners not starting the race. This was roughly two percentage points higher than previous years, suggesting some year-to-year variation even within a stable overall trend. The figure is consistent with the long-run Boston average of 9-10% DNS across all nationalities, reinforcing that the rate is a structural feature of major marathon participation rather than an anomaly.

Source: Running with Rock - 2025 Boston Marathon Data Insights

4. Just 3.1% of 2024 Races Were Cancelled Before They Ran in 2025

RunSignup's 2025 Race Trends Report - covering 97,000+ race events and 12.2 million registrations - found that just 3.1% of races with more than 500 participants that were listed in 2024 did not take place in 2025. This was the lowest event cancellation (and de facto mass DNS) rate since RunSignup began tracking it in 2018. For individual runners, this is good news: the risk of registering for a race and having the event cancelled is at a historic low.

Source: RunSignup - 2025 Race Trends Report

5. Race Week Registrations Declined to 23.7% in 2025

In 2025, only 23.7% of registrations occurred in the week before a race - the lowest percentage RunSignup has recorded. Race-day registrations ticked up to 3% of all sign-ups. This shift toward earlier registration has DNS implications: runners who commit months in advance have more exposure to the life events, injuries, and schedule changes that create DNS situations. The longer the gap between registration and race day, the more DNS opportunities arise.

Source: RunSignup - 2025 Race Trends Report

6. Injury Is the Most Commonly Cited DNS Reason

Across running communities and coach surveys, pre-race injury is consistently the top reason runners give for a DNS decision. A runner who trains through pain often crosses from a manageable DNS into a race-day DNF or aggravated injury. Sports medicine practitioners broadly recommend DNS over racing on a fresh or recovering injury, particularly for high-impact distances like the half marathon and marathon. The decision to DNS is often framed as a protective one that preserves long-term running health over short-term race completion.

Source: yournext.run - What Does DNS Mean in Running Events

7. Global Road Race Participation Grew 17.1% in 2024

A survey of 600 established road races in 44 countries covering 4,668,261 finishers found a 17.1% year-over-year increase in race finishers in 2024. Half marathon finishers grew 20.9% and marathon finishers climbed 14.6%. This growth context matters for DNS: more runners registering means more absolute DNS numbers even if the DNS percentage stays constant. A 10% DNS rate on a field of 50,000 is 5,000 people who never start - a meaningful figure for race operations, charity fundraising commitments, and course logistics.

Source: Road Race Management - Global Road Running Finishers Up 17% in 2024

8. 53% of 2025 Race Participants Were Female

RunSignup's 2025 data from 12.2 million registrations found that 53% of race participants identified as female. Women now outnumber men as registered race participants in the US endurance running market. DNS patterns by gender are less well-documented than DNF patterns, but the shift in the registration gender balance has changed race-day logistics across start corrals, projected finish windows, and field size planning at race organizations.

Source: RunSignup - 2025 Race Trends Report

9. Illness in the Week Before a Race Is a Leading DNS Trigger

Common cold, flu, and gastrointestinal illness in the days immediately before a race prompt large numbers of DNS decisions. Medical guidance consistently recommends not racing with symptoms below the neck (chest tightness, body aches, fever), and many runners DNS after developing upper respiratory infections during taper. Unlike injury, which often builds over weeks, race-week illness creates a last-minute DNS that leaves no room for alternative planning. Entry insurance and deferral policies exist specifically to manage this common scenario.

Source: myfirst5kandmore.com - When to DNS a Race

10. 18-29 Year-Olds Represented 17.9% of 2025 Race Participants

RunSignup reported that 18-29 year-olds made up 17.9% of 2025 race participants - the highest percentage since 2017. The return of younger runners to organized racing has been one of the notable post-pandemic trends. Younger runners tend to have shorter training histories, which can increase their pre-race DNS risk from injury or overtraining. However, they also have fewer work and family scheduling conflicts, which reduces the life-events category of DNS triggers.

Source: RunSignup - 2025 Race Trends Report

11. 74% of Race Website Views Came From Mobile in 2025

RunSignup found that 74% of race website views and 63% of transactions in 2025 came from mobile or tablet devices. While this is a registration and race communication statistic rather than a DNS figure directly, it reflects how race information - including start time updates, weather alerts, and logistics changes - reaches registered runners. Runners who miss critical race-day information via mobile notifications face a higher risk of logistical DNS (arriving late, missing start waves, or not knowing bib pickup locations).

Source: RunSignup - 2025 Race Trends Report

12. Strategic DNS Is an Accepted Practice at Elite Level

Elite runners routinely make DNS decisions based on injury risk, season prioritization, and competitive strategy. A runner targeting a major championship may DNS a tune-up race rather than risk aggravating a minor injury. This strategic DNS is documented across the running literature and accepted by coaches as sound race management. For recreational runners, the same logic applies: completing a target race healthy often requires the discipline to DNS a preparatory event when conditions aren't right. Our race finisher statistics post shows that globally, 4.67 million runners crossed race finish lines in 2024 - a number built on both who starts and who doesn't.

Source: myfirst5kandmore.com - 5 Reasons to DNS

13. 87% of US Races Have Fewer Than 500 Participants

RunSignup data shows that 87% of races in their system have fewer than 500 participants, with small races accounting for 38% of all finishers. DNS at small local events has different consequences than at large majors - small events have tighter margins on staffing, permits, and course aid, meaning even modest DNS rates can shift the logistics of what the race director planned. For runners, small events also tend to have no deferral or refund options, making the DNS cost more purely financial.

Source: RunSignup - 2025 Race Trends Report

14. Travel Disruptions Create Unexpected DNS Situations

Destination race DNS rates include a travel logistics component that local races do not. Flights cancelled, bags lost with race gear, cars that break down, and hotel errors all appear in DNS accounts from major destination events like marathons in major cities. Our race travel statistics post shows that 59% of race-traveling runners stay 3-5 nights, indicating that destination racing involves significant pre-race commitment - and multiple points of failure that can prevent a registered runner from reaching the start.

Source: myfirst5kandmore.com - When to DNS a Race

15. Races Grew 5% Per Event in 2025 vs 2024

Among races tracked by RunSignup across both years, per-race participation grew 5% in 2025 compared to 2024. This growth pressure means start corrals are fuller, packet pickup queues are longer, and the logistical complexity of reaching the start line has increased at many events. More crowded starts with tighter bib pickup windows can create new DNS scenarios for runners who arrive late or face longer-than-expected pre-race processes. Race directors are managing this by extending packet pickup hours and shifting to race-day bib collection at many events.

Source: RunSignup - 2025 Race Trends Report

What These Numbers Tell Runners

The DNS rate at major marathons - sitting at roughly 9-10% under normal conditions and climbing toward 15% in adverse weather - is not a failure of commitment. It is a structural feature of large-scale race registration. Runners register months ahead of time, and life intervenes. Injury, illness, weather, travel, and strategic recalculation all create DNS outcomes that are, in many cases, the right call.

The broader market data shows something encouraging: actual race events are being cancelled at the lowest rate on record (3.1%), which means the DNS burden is falling almost entirely on individual runner decisions rather than event-level failures. Runners face a more reliable event landscape than at any point since tracking began.

Where DNS data converges with race DNF data is on the injury question. Physical constraints are the top driver of both DNS and DNF outcomes. Runners who arrive at race week with an undertreated injury face a binary choice - and the DNS choice, while disappointing, prevents the compounding damage of a forced race finish on a compromised body.

Every DNS is a data point: the most common reason registered runners don't start is the same reason they don't finish - physical breakdown that better training periodization could have prevented.

Building Consistency That Gets You to the Start Line

The gap between registration and start line is bridged by consistent, measured training. Runners who log every workout, track weekly load, and honor recovery weeks are better positioned to arrive at race week healthy enough to start.

Runify turns that consistency into something you can see. Each run logged from Apple Watch, Garmin, or Strava earns XP and advances your tier ranking - making the habit of showing up to training as visible and rewarding as showing up to the race itself. More consistent weeks mean fewer DNS decisions made from an injured starting position.

Ready to make your runs count? Download Runify on the App Store and turn every mile into XP across leaderboards from 800m through the marathon.

4.8 stars on the App Store, 626+ reviews worldwide.