
The Stuttgart-based car maker said in a statement it lost 1.2 billion euros ($1.3 billion) in April-June due to one-off effects totaling 4.2 billion euros.
The last time Daimler reported a quarterly loss was in the fourth quarter of 2009.
NLC, Daimler AG sign MoU for assembly of Mercedes-Benz trucks in Pakistan
"Our second-quarter results were mainly impacted by exceptional items," newly-installed chief executive Olla Kallenius said.
By contrast, revenues rose by five percent to a higher-than-expected 42.7 billion euros, despite a one percent fall in unit sales.
Daimler also tumbled into the red on the operating level, losing 1.5 billion euros -- compared with underlying profit of 2.6 billion euros a year ago.
Looking ahead, "our focus for the second half of this year is on improving our operating performance and cash-flow generation," Kallenius said.
After cutting its annual outlook twice in recent months, Daimler left the forecast unchanged this time around, predicting operating profit "significantly below" the 11.1 billion euros booked in 2018.
The auto giant pointed to weaker-than-expected growth on global car markets, fallout from the diesel emissions cheating scandal and a mass recall over faulty Takata airbags.
German transport authority KBA ordered the recall of 60,000 Mercedes-Benz vehicles in June on suspicion they were fitted with software to cheat emissions tests -- allegations Daimler contests.
Diesel-related provisions alone are expected to reach around 1.6 billion euros, and the airbag recall should cost around one billion euros.
Mercedes joins forces with Bosch to develop self-driving taxis
The group is also looking to make massive investments in electric vehicles and autonomous driving.
Nevertheless, both unit sales and revenue should climb "slightly above" last year's levels.
Earlier this week, Daimler announced that its Chinese partner BAIC would become a shareholder with a five-percent stake.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ