Red Bull Racing is expected to announce its 2026 driver line-up within the next few weeks. That decision will determine who partners Max Verstappen and which drivers will join sister team VCARB. Among those waiting anxiously are Isack Hadjar, Yuki Tsunoda, Liam Lawson, and F2 talent Arvid Lindblad.
Hadjar currently appears to be the front-runner for the seat alongside Verstappen. The Frenchman has impressed in his debut season with VCARB, even securing a podium finish. According to reports, Lindblad will likely move up to a VCARB seat next year, which means the final spot could come down to a direct fight between Tsunoda and Lawson.
Coronel Picks Verstappen’s Ideal Partner
F1 analyst Tim Coronel knows exactly who he would place next to Verstappen. “I would go for Hadjar,” he told GPToday.net. “What I really like about him is how close he always is to the limit. He has a bit of the same drive and style as Max.”
However, Coronel admits he isn’t sure the young Frenchman is mentally ready for such a challenge. “Time will tell, because Max has broken almost everyone who’s been his teammate,” he added. “Hadjar shouldn’t think he’s going to get close to him, because that won’t happen. We all know he’s got the speed, but the question is whether he has the mental strength. He’s going to learn a lot upstairs next year,” Coronel said with a grin.
“Formula 1 Comes Too Soon for Lindblad”
Meanwhile, Yuki Tsunoda’s future looks uncertain. If Lawson lands the VCARB seat, the Japanese driver could be left without a place in 2026. Coronel believes Red Bull should think carefully before letting him go. “Tsunoda has been fantastic at VCARB, so I wouldn’t want to see him dropped. People draw conclusions too quickly, like they did with Ricciardo, Pérez, Albon, and Gasly. For Lindblad, it’s definitely too early to take a Formula 1 seat.”
Red Bull initially aimed to clarify both teams’ driver line-ups earlier this season, but that announcement was postponed. The decision was expected after the Mexican Grand Prix, though it now seems to have been delayed once again.
0

Replies (0)
Login to reply