Ghostboard pixel

Xfinity Series Recap: 2018 Lakes Region 200 (New Hampshire Motor Speedway)

Christopher Bell clinched victory, with Brad Keselowski and Ryan Preece securing second and third respectively. Matt Tifft made notable progress, moving from 14th to fifth, showcasing strong strategies and adaptability.

Xfinity Series Recap: 2018 Lakes Region 200 (New Hampshire 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.

Christopher Bell started in the second position and managed to take the lead, eventually winning the race. Brad Keselowski, who led initially after starting from pole, finished in second place. While their positions remained fairly stable, Ryan Preece also maintained a consistent run, starting and finishing in third place. The performance from these drivers indicates strong race setups and strategies.

A notable performance came from Matt Tifft, who started 14th but finished fifth, showing a significant improvement in position. This type of movement is captured in his net gain rating, suggesting a calculated and effective drive through the field. Brandon Jones also showed improvements, advancing from the eighth starting position to finish sixth.

Several cautions, including incidents involving Ross Chastain, Ryan Truex, and Jeremy Clements, indicated a wild race. The caution on lap 179 involving Garrett Smithley and Chad Finchum likely disrupted potential finer average running positions for some drivers. Despite the disruptions, most drivers completed the race under the damaged vehicle policy or other mechanical failures. Overall, this race was a bonanza for statistical shifts, highlighting drivers' resilience and adaptability.

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