Ghostboard pixel

Cup Series Recap: 2020 Season Finale 500 (Phoenix Raceway)

Chase Elliott secured a dominant win, leading 217 of 312 laps, with Brad Keselowski finishing second. Jimmie Johnson's impressive climb from 26th to 5th and solid performances from Joey Logano and Denny Hamlin highlighted the race.

Cup Series Recap: 2020 Season Finale 500 (Phoenix Raceway)

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.

Chase Elliott started on pole and capitalized, leading 217 of the 312 laps to secure a win. Despite an ARP of 3.65, Elliott maintained consistent control. His net gain rating of 6.40 reflects efficient driving, translating his starting position into a bonanza of laps led. Brad Keselowski followed, finishing second with an ARP of 4.25 and a GR of 3.51, showing solid performance though he briefly led during the mid-segments.

Jimmie Johnson’s climb from 26th to 5th was notable, his ARP of 8.43 and net gain rating of 3.75 showcasing a strong race. Joey Logano led for an extended period early on and recorded an ARP of 2.23, finishing third with a net GR of 1.79. His GR-LR indicates effective management of race position while battling for the lead. Denny Hamlin, finishing fourth, had an ARP of 3.16, consistently maintaining his top-five position.

Overall, the race saw a wild shuffling of positions due to different strategies and some late-race cautions impacting the ARPs of several drivers. Instances such as Erik Jones, starting 14th but finishing 22nd with an ARP of 16.65, can be attributed to incidents like the one at lap 162, causing position losses. Drivers who adapted to the changes held steady, translating a strong ARP into a competent race finish.

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