CreatorsPublishersAdvertisers
View more in
Motorsports

Brad Keselowski had a hilarious response to reports of him leaving Team Penske, joining Roush Fenway Racing

USA TODAY Sports Media Group
USA TODAY Sports Media Group
 2021-06-26
https://img.particlenews.com/image.php?url=0XrKWt_0ag9L8gl00

With NASCAR driver Brad Keselowski in the final year of his contract with Team Penske, reports, rumors and speculation about his future have been circulating all season.

Will the 2012 Cup Series champion re-sign with Team Penske and stay behind the wheel of the No. 2 Ford, or will he be with another team by 2022?

Well, according to multiple reports Friday, Keselowski is set join Roush Fenway Racing in 2022 as a driver and co-owner.

The Sports Business Journal‘s Adam Stern reported Friday afternoon that “Roush Fenway Racing informed its partners that it has a done deal with Brad Keselowski to become a driver and co-owner starting in ’22, according to sources” but hasn’t announced it out of respect for Team Penske. And then FOX Sports’ Bob Pockrass confirmed the news later in the day.

No official announcement has been made yet about Keselowski leaving Team Penske or joining Roush Fenway Racing. And the NASCAR season will only be halfway over after Saturday’s race at Pocono Raceway, so there’s no real rush.

But Keselowski had a hilarious reaction to all of this less than an hour after the Sports Business Journal‘s report.

Just perfect, because even if Keselowski wanted to confirm or deny the reports, he might not be in a position to do so and probably wants to remain focused on this season as much as possible.

The 37-year-old driver has been racing full-time for Team Penske since the 2010 season, and 34 of his 35 career wins have been with the organization.

Going into this weekend’s doubleheader at Pocono, he’s 10th in the driver standings with one win at Talladega Superspeedway so far this year. He’ll start Saturday’s Pocono Organics CBD 325 in 18th.

List

Gallery

https://img.particlenews.com/image.php?url=423DWJ_0ag9L8gl00

Comments / 0

Comments / 0