Maritime Daily, 5 October 2026: EMMA MAERSK (IMO 9321483) Left Rotterdam for Algeciras, Low Risk

Executive Summary

EMMA MAERSK, IMO 9321483, is a Singapore-flagged container ship that left Maasvlakte-Rotterdam on 30 September and was moored at Algeciras on 5 October, with no sanctions flag in the one screen I could reach, and no obfuscation signals in the limited data checked. MyShipTracking shows departure from Maasvlakte-Rotterdam at 21:35 UTC on 30 September 2026 and arrival at Algeciras at 04:18 UTC on 5 October, a trip of 1,442.26 nm. The same page's "Last Trips" table shows the times two hours later (23:35 and 06:18), which looks like local time. Its AIS destination now reads ESALG>EGSUC-N (Sokhna, Egypt), with an ETA of 10 October 19:00 UTC on the same page.

Port of Rotterdam, the second named subject, is stable but not growing. Throughput was 212.0 million tonnes in the first half of 2026, up 0.4%, with container volume flat in TEU.

Coverage caveat: only Datalastic and MyShipTracking (via its public vessel page) returned vessel data. The JSONCargo and MyShipTracking API tools returned tool_not_found in this run, so the three-provider cross-check is incomplete. Sanctions status comes from a single commercial screen, not from OFAC, EU or UN list queries.

Vessel identity and position: two sources agree on identity, differ on size

Datalastic and MyShipTracking agree on the identifiers. Both give MMSI 563254800, call sign 9VCY3, Singapore flag and a 2006 build (Datalastic result; MyShipTracking). Datalastic classes it as a container ship of 15,550 TEU with Lyngby-Taarbaek as home port.

They differ on technical specifications, and the gap is large for deadweight:

Field	Datalastic	MyShipTracking	Source
Gross tonnage	171,542	170,794	Datalastic / MST
Deadweight	174,239	156,907	same
Length	397.71 m	399 m	same
Draught	12.8 m (database average)	16.2 m (AIS-reported)	same

MagicPort's profile uses 174,239 MT deadweight and 399 m length, so MyShipTracking's deadweight is the outlier. My reading (inference): these are database differences, not spoofing, because the two draught figures measure different things (static versus live). Position data is only from MyShipTracking: 36.14628, -5.43532 as reported at 22:04 on 5 October (time zone not stated), speed 0 knots, status moored at Algeciras.

KEY TAKEAWAY: Identity matches across sources; specification differences look like database variance, and live position rests on one provider.

Rotterdam call and recent voyage pattern

The Rotterdam call was short and fits a liner rotation. MyShipTracking's port-call log lists Maasvlakte-Rotterdam arrival 29 September 07:51 and departure 30 September 21:35 (time zone not stated), after Hamburg (26 to 28 September), Bremerhaven (23 to 25 September) and the Thames (20 to 21 September). Before that, the log shows Tanjung Pelepas on 23 to 24 August and Qingdao on 8 to 9 August, which is consistent with an Asia-to-North Europe rotation followed by a Northern Europe loop. The page lists Algeciras as the most visited port in the last year, with 8 arrivals, and Rotterdam-Maasvlakte with 3.

A destination change was logged at 14:04 on 5 October (time zone not stated), from NLRTM>ESALG to ESALG>EGSUC-N (MyShipTracking). I could not find cargo, berth or terminal assignment data, so the cargo and Rotterdam terminal are not established.

Ownership and sanctions: clean on one screen, unverified on official lists

MagicPort lists Moller Singapore AP Pte Ltd as registered owner and Maersk A/S as commercial and ISM manager. Its screen against 300+ watchlists says the vessel is not sanctioned and not flagged as risky. This is a vendor claim and a single source. I did not query OFAC, EU or UN lists directly, and I did not find flag-change history or AIS-gap records. A Maersk-managed liner with a standard Northern Europe rotation does not fit the shadow-fleet pattern, but that is my judgement, not a tested finding.

Port of Rotterdam: flat volumes, a strike report that I could not verify

Rotterdam's half-year picture, as reported by FreshPlaza from the Port Authority release:

Cargo: 212.0 million tonnes, up 0.4%; dry bulk up 1.7%, liquid bulk up 2.4%, breakbulk down 1.1%.
Containers: down 0.1% in TEU and 2.6% in tonnage; deepsea TEU up 5.2%, transhipment down 20% on capacity constraints.
Risks: the Port Authority CEO said the closure of the Strait of Hormuz raised uncertainty and energy prices, with limited direct impact on Rotterdam (same source).

An Amsterdam Times page (site date 5 October 2026) carries a headline saying FNV Havens strikes caused supply chain delays at Rotterdam and Zeeland ports. The article body did not load in either fetch, and the outlet describes itself as AI-produced, so treat this as an unconfirmed lead. EMMA MAERSK sailed on 30 September, before that date, so no effect on this vessel is shown.

What to do next

Re-run the JSONCargo and MyShipTracking API calls once the gateway exposes them, and compare the live position and the deadweight and draught figures.
Check OFAC, EU and UN lists directly for the IMO and for Moller Singapore AP.
Confirm the strike report against Port of Rotterdam, FNV or Dutch press, and then check Algeciras and Sokhna ETAs against any schedule slips.
Change my view if AIS gaps appear on the Algeciras to Sokhna leg or the destination changes to a non-scheduled port.