by Manal Barakat, SeaNewsEditor
Update: 13.10.2025
An update by the Port of Rotterdam announced that the strike carried out by lashing companies has been temporarily suspended, effective Monday, 13 October at 7:00 AM local time.
The decision to suspend the strike was initiated by a court order that was issued this weekend.
Kuehne+Nagel reports that workers are allowed to strike again next weekend if there is no progress in the negotiations by Friday, 17 October.
Update: 10.10.2025
The Port of Rotterdam is currently experiencing significant operational disruption due to an extended strike by container lashers, which has now been prolonged until further notice.
This industrial action continues to affect cargo handling and logistics operations across key terminals.
In parallel, activist group GeefTegengas staged a blockade on Friday, 10 October, targeting the APM2 and RWG terminals.
Further escalation is anticipated, as GeefTegengas has announced a “mass blockade” for Saturday, 11 October, aiming to halt all transport to and from the port.
The organisation expects participation from hundreds of activists, raising concerns about broader logistical delays and security implications.
Original article: 08.10.2025
According to an advisory by logistics service provider Contargo, lashing companies at the Port of Rotterdam plan to strike for 48 hours starting Wednesday, 8 October.
Talks to reach a new labour agreement for the workers stalled yesterday, pushing the unions to issue an ultimatum that expired on Wednesday morning.
Contrago reports that the strike will halt container vessel handling, ultimately impacting container transport on the land-side.
Furthermore, demonstrations are planned to take place on 11 October in the port of Rotterdam in protest against the war in Gaza.
While the demonstrators plan to block the port's tracks, the extent of the protests remains unclear. The action is likely to impact port operations and cause delays in container movement.
For the latest port and vessel statuses or situation updates, please refer to the seaexplorer alert map.
