
Kenseth focuses on playoffs, not 2018
Matt Kenseth said Friday he still does not have anything lined up for the 2018 season.
"No plans right now," Kenseth said at Bristol Motor Speedway when asked about driving in the Monster Energy NASCAR Cup Series next year. "Just raise kids, hang out with my family."
The 2003 Cup champion will not return to Joe Gibbs Racing next season as Erik Jones takes over the No. 20 Toyota. That news was announced last month after Kenseth revealed at Kentucky Speedway he didn't have a job after this season. Since then, Kenseth has been at the center of a few rumors in the garage.
Related Stories
So, has he been talking to other teams and looking around?
"I'll let you know when I know something," said Kenseth. "But to be honest with you, I'm not worried about it even really one percent anymore, to be honest with it. Not concerned about it."
What about being approached by other owners?
"When I have something to tell you, I'll let you know," Kenseth reiterated. "I just don't have anything for next year to talk about at the moment."
Projecting a calmness about it all, Kenseth said his focus is on contending for this year's championship. Kenseth, who is still looking for his first win of the season, continues to hold down the final spot on the playoff grid with three races left in the regular season.
"I'm really [more] concerned about 2017, and that's the truth," Kenseth said. "We've got 13 races left, three to try and get into the playoffs. We're not in there yet. Kind of got ran over at the end of the race last week by the 24 (Chase Elliott) trying to race him and the 1 (Jamie McMurray), at least for points, try to get a cushion if we don't get a win.
"But, hopefully, we get a win and get in the playoffs and try to race for a championship. That's our goal every year and really that's what I'm concentrating on at this time."
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.




