Ghostboard pixel

Xfinity Series Recap: 2018 Boyd Gaming 300 (Las Vegas Motor Speedway)

Kyle Larson clinched victory after 200 laps, while Christopher Bell snagged second from pole position. The race saw notable gains and setbacks, making it an exciting, unpredictable event.

Xfinity Series Recap: 2018 Boyd Gaming 300 (Las Vegas Motor Speedway)

Basic stats | Advanced stats | Loop data | All laps

What follows is an AI-generated commentary based on the race results and statistics. I find it useful to glance at. You can view more statistics at the Lap Raptor race page for this race. For more data, head over there.

Kyle Larson clinched the win from the second position, finishing first after 200 laps. He maintained a strong presence, leading in average running position and net gain rating a perfect zero, indicating consistent results in terms of gain and loss. Christopher Bell, who started from pole position, managed to secure second place. Justin Allgaier exhibited notable progression, closing in from 12th to 3rd place.

The race saw significant movement particularly from Brandon Jones who moved from 16th to 7th place, and Michael Annett advancing from 19th to 13th. These gains illustrate a wild fluctuation in positions during the race. However, there was also prominent regression observed in Tommy Joe Martins, who fell from 8th to 25th position, and Austin Cindric who dropped drastically from 15th to 34th following an accident.

The bonanza of incidents impacted several drivers. At Lap 135, Austin Cindric and Tommy Joe Martins were involved in an incident in Turn 2, attributing to their results. The final caution at Lap 191 involved Ross Chastain and Kaz Grala in an incident on the backstretch, likely spoiling their ARP, as both finished in poorer positions than expected, at 18th and 16th respectively. The cumulative impact of these incidents influenced race outcomes significantly.

Subscribe to Lap Raptor Commentary

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe