Friday, August 26, 2016

Subaru Trademarks BRZ tS For The U.S.


Japanese automaker Subaru filed a trademark application for the "BRZ tS" name for use here in the United States back in January 2016, and now a new report claims that the moniker was recently registered to the company’s U.S. division.

According to AutoGuide, the trademark was applied for use on “Vehicles; apparatus for locomotion by land, air or water.” And while these kind of trademarks are generally applied for companies to protect their property, Subaru might have other intentions for this one. Specifically, the automaker may be preparing an U.S. version of the BRZ tS that it launched in Japan in 2015.

Why do I think this is not another case of keeping intellectual property safety policies? Well, the timing of the trademark is rather unusual. Given that the BRZ tS was launched a year ago, Subaru would have filed such a trademark back in 2015. Not to mention that a new version of the coupe would be more than welcome on the U.S .market, despite not having the highly anticipated drivetrain updates.

As a brief reminder, the BRZ tS is basically a standard model enhanced with STI parts inside and out. While the upgrade is pretty much about new badges and upholstery options, the chassis employs a sportier suspension system, while the unique 18-inch wheels benefit from 17-inch Brembo brake disks at all four corners. The drivetrain remains unchanged, but since it will be released after Subaru update for the 2017 model year, the 2.0-liter boxer engine should get five extra horses and five additional pound-feet with the six-speed manual transmission. Specifically, drivers who prefer to row their own will get 205 horsepower and 156 pound-feet, while those who favor automatics get the standard 200 ponies and 151 pound-feet.

There’s no word as to when the BRZ tS will hit U.S. dealerships, but if Subaru really wants to offer it here, it could break cover by the end of 2016.

Continue reading for the full story.





from Top Speed http://ift.tt/2bry0za
via IFTTT

0 comments:

Post a Comment