
Jared C. Tilton/Getty Images
NASCAR’s Clash tipped for Daytona return
Daytona International Speedway is tipped to be returning as the host of the Clash, NASCAR's preseason exhibition event, in 2027.
The Athletic is reporting that a confirmation announcement could come within a few weeks that the event will run the week before the Daytona 500, which is scheduled for Feb. 21.
The shift back to Daytona would not be all that surprising, as the industry had been discussing the possibility of the event being held at Daytona or Bowman Gray Stadium for quite some time. Bowman Gray, the historic quarter-mile in Winston-Salem, N.C., had hosted the event the last two years. It was held in Los Angeles from 2022 through '24 at a quarter-mile track built inside the Los Angeles Memorial Coliseum.
Daytona, however, is where the Clash was born. The specialty event debuted in 1979 and was used as a hype-up race for the season-opening Daytona 500 with major sponsorship from Busch.
A sprint race, the Clash, in its prime, was one of the most popular events on the calendar. But over time, through on-track chaos of a superspeedway event and ever-changing eligibility rules, it lost some of its luster. And when NASCAR began moving the event around, it faced questions about its purpose.
The last time the Clash was held at Daytona was in 2021, but that race was run on the road course. It has not been held on Daytona's trioval since 2020 (pictured above).
Kelly Crandall
Kelly has been on the NASCAR beat full-time since 2013, and joined RACER as chief NASCAR writer in 2017. Her work has also appeared in NASCAR.com, the NASCAR Illustrated magazine, and NBC Sports. A corporate communications graduate from Central Penn College, Crandall is a two-time George Cunningham Writer of the Year recipient from the National Motorsports Press Association.
Read Kelly Crandall's articles
Latest News
Comments
Comments are disabled until you accept Social Networking Cookies. Update cookie preferences
If the dialog doesn't appear, ad-blockers are often the cause; try disabling yours or see our Social Features Support.


