Bayer stock trades on the latest Bayer update

Bayer (DE000BAY0017) shares are tied to the companys latest investor context, with the most recent annual figures showing 2025 sales of EUR 46.6 billion and EBITDA before special items of EUR 10.1 billion, alongside a net loss of EUR 2.6 billion.

2025 figures set the base

The 2025 annual report gives the clearest read-through for Bayer stock: sales were EUR 46.6 billion, EBITDA before special items was EUR 10.1 billion, and the company reported a net loss of EUR 2.6 billion for the year. Those figures frame the market view until the next reported quarter or update lands.

Margin pressure remains visible

Bayer also reported that EBITDA before special items of EUR 10.1 billion in 2025 sat against the EUR 46.6 billion sales base, while the net loss of EUR 2.6 billion underlines how sharply litigation and restructuring charges still affect earnings quality. The comparison is clear in the annual numbers themselves, where profit remained negative even with a multi-billion-euro operating base.

Investor focus stays on cash and legal costs

For investors, the key question is whether Bayer can stabilize earnings and cash generation after the 2025 loss. The companys next material numbers will matter more than broad commentary, because the 2025 report already shows the scale of the turnaround challenge.

Crop science matters most

The crop science division remains one of Bayers most important business areas because it links revenue, pricing, and farm-cycle demand. In the 2025 figures, the division remains part of the operating mix that must carry a large share of future recovery.

Stock level and market context

Bayer stock is identified here by its ISIN DE000BAY0017 and should be read alongside the companys reported 2025 figures of EUR 46.6 billion in sales, EUR 10.1 billion in EBITDA before special items, and a EUR 2.6 billion net loss. A current dated market quote was not available in the source set for this call, so the article uses the latest evidenced operating and market context instead.