Matt Thacker/Motorsport Images
North Wilkesboro keeps NASCAR All-Star Race for 2025
North Wilkesboro Speedway will host the NASCAR All-Star Race for the third consecutive year in 2025.
The 41st edition of the NASCAR All-Star Race, the $1 million non-points race, will be held on May 18, 2025. It will remain a doubleheader weekend with the Craftsman Truck Series, which competes in a points-paying event at North Wilkesboro Speedway.
The newly repaved 0.625-mile track will host its second NASCAR All-Star Race this weekend. Kyle Larson won the event last year on the original pavement. It was the first NASCAR Cup Series race at the facility in 26 years.
Speedway Motorsports announced its 2025 return Friday morning. In doing so, it was also announced that there would be a new pricing structure for the facility.
“Sunday grandstand tickets will start at just $49, with three-day NASCAR ticket packages starting at $95 and five-day packages -- including zMAX CARS Tour action -- starting at just $125, providing fans unmatched value at one of NASCAR’s most historic venues.”
North Wilkesboro is the fifth race to be confirmed on the 2025 schedule, which still has not been released in its entirety. However, it’s expected to be announced sooner than it was last year.
The confirmed ’25 races are: the Daytona 500 (Feb. 16), the All-Star Race (May 18), the Coca-Cola 600 (May 25), Atlanta Motor Speedway (June 28) and the season finale at Phoenix Raceway (Nov. 2).
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.