Abstract:
In response to the brake pedal controversy, today Zunjie Auto released the "Zunjie V800 Brake Pedal Testing Instructions." The description shows that on October 11, 2026, a nationally recognized third-party testing agency inspected the Zunjie V800 brake pedal. The Zunjie V800 complies with the requirements of the industry standard QC/T 788-2018 (longitudinal force 1500N, displacement <5mm), and after strict inspection to a longitudinal force of 3000N, no cracks or damage occurred.

The Securities Times reporter exclusively learned that the test was conducted by the China Automotive Engineering Research Institute Co., Ltd. Testing Center.
On the morning of October 13, a Securities Times reporter called the China Automotive Engineering Research Institute Co., Ltd. Testing Center, and the person connected was a staff member of the archives. When the reporter told her the report number and made an inquiry, she told the reporter: "According to the report number you provided, we did find this report, which was issued by our company, but we only tested it based on the prototype car provided by the company at the time, and we cannot guarantee whether the report circulated by the outside world has been tampered with."

On the morning of October 13, JAC’s stock price rose sharply.

Previous reports showed that on October 8, Chedi released a test video stating that the brake pedal brackets of three new cars with extremely short mileage (one of which had a mileage of no more than 3km) broke during the 100km/h to 0 emergency braking test in a closed venue.
On the same day, Zunjie Auto released a statement on issues related to the brake pedal bracket base. The description stated that Zunjie Automobile’s braking system has completed the entire process development and verification in accordance with requirements that are higher than national standards (GB 216702025/ GB 72582026) and higher than industry standards (QC/T 7882018). Since the delivery of the first batch of vehicles, no breakage of the brake pedal bracket base has occurred in actual user scenarios.
Comments