
GP2: Rosenqvist joins test with Prema
Formula 3 European champion and double Macau Grand Prix winner Felix Rosenqvist will make his GP2 debut in the December post-season test in Abu Dhabi with Prema Powerteam.
The 24-year-old, who clinched back-to-back Macau wins last weekend, will test for the team that helped take him to glory in F3 this year. Italian outfit Prema will also be making its GP2 debut, replacing the outgoing Lazarus squad for 2016.
"GP2 is something I've been wanting to try for the last couple of years, so finally getting this opportunity is fantastic," said Rosenqvist.
"It will certainly be an exciting experience. A new car, new tyres and a new track, but I honestly couldn't feel more ready for it. The GP2 car has roughly three times the power of what I'm used to from F3, which should be interesting, but hopefully it won't take too long to adapt.
"I'm particularly pleased to be doing this test with Prema, and to contribute in their early preparations for next year."
Prema team boss Rene Rosin believes Rosenqvist will be a "great asset" to the team.
"Felix has done an incredible job for us this year, winning the European championship and the Macau Grand Prix," he said. "He thoroughly deserves this opportunity in Abu Dhabi.
"He will be part of our very first acquaintance with GP2, and we have an extensive programme to cover as we prepare to enter the championship next season.
"We all understand the kind of challenge ahead of us, but I'm absolutely convinced that Felix will find his feet very quickly and be a great asset to us in this exciting new project."
Former GP3 frontrunner Andrea Caldarelli, who left that series during the 2011 campaign to pursue a Toyota-backed career in Japan, will return to test for Russian Time's GP2 outfit in Abu Dhabi. Jimmy Eriksson, currently fifth in GP3, will spend one day testing for Status GP, and two days with Trident.
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.





