| Hoegh Manila |
188 |
07.07.2026 |
|
12.07.2026 |
11.07.2026 |
17.07.2026 |
31.07.2026 |
website (sailed) | re-confirmed 2026-08-26 (25th pull, live vessel-rotation API) | re-confirmed 2026-08-27 (26th pull, live vessel-rotation API) | 2026-09-01 (30th pull, live vessel-rotation API via the Windows-MCP PowerShell bridge, fleet + 40/40 hulls HTTP 200): sailed, outside the live rotation window; retained as history |
| Hoegh Yokohama |
152 |
25.07.2026 |
23.07.2026 |
|
30.07.2026 |
02.08.2026 |
|
website 2026-08-14 (17th pull) - Cartagena call absent at every pull since; re-checked on the full live rotation at the 24th pull (2026-08-25) and voyage 152 has no Cartagena call. Drop reconfirmed. | re-confirmed 2026-08-26 (25th pull, live vessel-rotation API) | re-confirmed 2026-08-27 (26th pull, live vessel-rotation API) | 2026-09-01 (30th pull, live vessel-rotation API via the Windows-MCP PowerShell bridge, fleet + 40/40 hulls HTTP 200): voyage 152 NOW HAS a Cartagena call (arr 03-Sep) but it is the ex-MEXICO leg (Veracruz dep 27-Aug -> Kingston 01/02-Sep -> Cartagena 03-Sep). There is still NO European load call on voyage 152, so the Europe->Colombia drop STANDS |
| Hoegh Oslo |
142 |
19.08.2026 |
11.08.2026 |
|
21.08.2026 |
24.08.2026 |
19.09.2026 |
website 2026-08-25 (24th pull) - VESSEL ROTATION API, full rotation read live. Cartagena arrival 2026-09-21 -> 2026-09-20 (-1d). Le Havre and Vigo departures CONFIRMED unchanged. The live rotation carries NO Antwerp or Bremerhaven call on voyage 141 - those two dates are carried forward from earlier port-pair pulls and have already passed; do not offer them. | re-confirmed 2026-08-26 (25th pull, live vessel-rotation API) | re-confirmed 2026-08-27 (26th pull, live vessel-rotation API) | re-confirmed 2026-08-28 (27th pull, website Vessel-tab sweep, rotation API down): Cartagena arrival unchanged | re-confirmed 2026-08-31 (28th pull, Windows-MCP/Playwright bridge, rotation API down, full rotation re-read): exactly unchanged | 2026-09-01 (30th pull, live vessel-rotation API via the Windows-MCP PowerShell bridge, fleet + 40/40 hulls HTTP 200): VOYAGE LABEL SETTLED - relabelled 141 -> 142. The 29th pull flagged this and deferred it to 'one deliberate pass next run'; this is that pass. TWO independent carrier sources now agree against the old label: the live rotation API numbers the 20-Sep Cartagena call voyage 142, and the carrier's own HASA Wk35/2026 PDF also lists it as Hoegh Oslo /142 (Veracruz 11-Sep, Cartagena 21-Sep). Every DATE is unchanged. The European dates in this row are the physical voyage-141 calls and have all sailed; the live 142 rotation publishes NO European load call, so do not offer them | re-confirmed 2026-09-09 (37th pull, live rotation API via browser page-context fetch): Cartagena arrival unchanged at 20-Sep | 2026-09-10 (38th pull, built-in Claude browser pane, in-page fetch()): REAL CHANGE - Cartagena arrival 2026-09-20 -> 2026-09-19 (-1d). [EVIDENCED: Src https://www.hoeghautoliners.com/api/vessel?vesselCode=OSLO&departureDate=2027-09-10&arrivalDate=2026-09-10 | Fetched 2026-09-10 | HTTP 200] |
| Hoegh Manila |
190 |
12.09.2026 |
01.09.2026 |
03.09.2026 |
14.09.2026 |
17.09.2026 |
01.10.2026 |
website 2026-08-25 (24th pull) - VESSEL ROTATION API, full rotation read live. All six legs read off one continuous rotation (the Antwerp/Bremerhaven/Le Havre calls are logged by the carrier under voyage 189, same hull, same call). Every date is 1 day earlier than the 23rd pull because the port-pair search this cache used ran +1d against the vessel basis; that offset is now read directly and is gone. Treat as a basis correction, not a schedule slip. | re-confirmed 2026-08-26 (25th pull, live vessel-rotation API) | re-confirmed 2026-08-27 (26th pull, live vessel-rotation API) | 2026-08-28 (27th pull, website Vessel-tab sweep): Cartagena arrival CONFIRMED unchanged (2026-09-28). This voyage's rotation showed TWO consecutive Antwerp calls (arr 2026-09-03/dep 2026-09-10, then arr 2026-09-10/dep 2026-09-11) - the second Antwerp departure reads one day earlier than this cache's 2026-09-11, within the same +/-1-day basis noise flagged at the 24th pull. NOT changed on this evidence; re-check with a single clean Manila-only pull. | 2026-08-31 (28th pull, Windows-MCP/Playwright bridge): this voyage's rotation dump this pull reads Cartagena arr 2026-10-01 (+3d) with Vigo dep 2026-10-17 (+2d) - a THIRD different figure across three consecutive pulls for this vessel's voyage-boundary numbers (see 26th and 27th pull notes above). NOT changed on this evidence - now treated as evidence the site's OWN rendering is unstable for this hull, not the schedule. Carried forward at these figures. | 2026-08-31 (29th pull, live vessel-rotation API RESTORED - fleet endpoint + 40/40 hulls all HTTP 200): MANILA INSTABILITY RESOLVED. It was NOT a site rendering fault. The structured rotation API separates the two consecutive Antwerp calls BY VOYAGE NUMBER: arr 2026-09-04 / dep 2026-09-10 is the NORTHBOUND voyage 189 discharge call, arr 2026-09-11 / dep 2026-09-12 is the SOUTHBOUND voyage 190 load call - two genuine calls on one physical rotation, not a duplicate. With that resolved, this pull AGREES with the 28th pull's independent Vessel-tab read on every disputed number. Two independent transports agreeing is the evidence that was missing at the 27th and 28th pulls; changed. Southampton 2026-09-02 -> 2026-09-03 (+1d), Vigo 2026-09-15 -> 2026-09-17 (+2d), Cartagena arrival 2026-09-28 -> 2026-10-01 (+3d). Antwerp (2026-09-11), Bremerhaven (2026-09-01) and Le Havre (2026-09-13) CONFIRMED UNCHANGED. | 2026-09-01 (30th pull, live vessel-rotation API via the Windows-MCP PowerShell bridge, fleet + 40/40 hulls HTTP 200): Cartagena arrival (01-Oct), Bremerhaven (01-Sep), Southampton (03-Sep) and Vigo (17-Sep) CONFIRMED EXACTLY UNCHANGED. BASIS CORRECTION, NOT A SCHEDULE SLIP - Antwerp 2026-09-11 -> 2026-09-12 and Le Havre 2026-09-13 -> 2026-09-14: this column is the load-port DEPARTURE (sailing) date and those two carried the call's ARRIVAL date. Live rotation: Antwerp arr 11-Sep dep 12-Sep, Le Havre arr 13-Sep dep 14-Sep |
| Hoegh Berlin |
140 |
15.09.2026 |
10.09.2026 |
18.09.2026 |
|
|
03.10.2026 |
website 2026-08-25 (24th pull) - VESSEL ROTATION API, full rotation read live. NEW - not on any previous pull. EUAF/Oceania trade, not SAMX: Livorno dep 2026-08-28, Zeebrugge dep 2026-09-05, Southampton dep 2026-09-14, then Baltimore 2026-09-24 and Jacksonville 2026-09-27 before Cartagena 2026-10-03, continuing to Auckland and Australia. A genuine UK/Mediterranean -> Cartagena option the port-pair pulls never surfaced. | re-confirmed 2026-08-26 (25th pull, live vessel-rotation API) | re-confirmed 2026-08-27 (26th pull, live vessel-rotation API) | 2026-08-28 (27th pull, website Vessel-tab sweep, full rotation): REAL CHANGE - Southampton departure 2026-09-14 -> 2026-09-18 (+4d). Baltimore/Jacksonville/Cartagena (2026-09-24/2026-09-27/2026-10-03) CONFIRMED unchanged. The rotation now also shows direct Antwerp (dep 2026-09-16, added to this row), Amsterdam (dep 2026-09-06) and Newcastle (dep 2026-09-14) calls between Zeebrugge and Southampton that this cache did not itemise before - Amsterdam and Newcastle have no column here; see the COL cache note in datastore 139874 for the full EU rotation. | re-confirmed 2026-08-31 (28th pull, Windows-MCP/Playwright bridge, rotation API down, full rotation re-read): exactly unchanged | 2026-09-01 (30th pull, live vessel-rotation API via the Windows-MCP PowerShell bridge, fleet + 40/40 hulls HTTP 200): Antwerp (16-Sep), Southampton (18-Sep) and Cartagena arr (03-Oct) CONFIRMED EXACTLY UNCHANGED. Bremerhaven departure 10-Sep now carried in its own column - it was already on the live rotation and described in the COL cache note, but this table left the column blank | 2026-09-09 (37th pull, live rotation API via browser page-context fetch, built-in Claude browser pane): REAL CHANGE - Antwerp 16-Sep -> 15-Sep (-1d); Newcastle (not columned here) also -1d. Bremerhaven/Southampton/Cartagena CONFIRMED EXACTLY UNCHANGED |
| Hoegh Yokohama |
154 |
20.09.2026 |
18.09.2026 |
17.09.2026 |
22.09.2026 |
25.09.2026 |
12.10.2026 |
website 2026-08-25 (24th pull) - VESSEL ROTATION API, full rotation read live. All legs 1 day earlier than the 23rd pull - same +1d port-pair basis correction as Manila 190, not a slip. Bremerhaven/Le Havre/Vigo are logged under voyage 153 (same hull). NO Southampton call on this rotation - now proven from the rotation itself, not inferred from the broken Southampton port-pair form. | re-confirmed 2026-08-26 (25th pull, live vessel-rotation API) | re-confirmed 2026-08-27 (26th pull, live vessel-rotation API) | re-confirmed 2026-08-28 (27th pull, website Vessel-tab sweep, rotation API down): exactly unchanged | re-confirmed 2026-08-31 (28th pull, Windows-MCP/Playwright bridge, rotation API down, full rotation re-read): exactly unchanged | 2026-09-01 (30th pull, live vessel-rotation API via the Windows-MCP PowerShell bridge, fleet + 40/40 hulls HTTP 200): REAL CHANGE, whole voyage later - Cartagena arrival 2026-10-09 -> 2026-10-12 (+3d). European load calls re-read off the live rotation on the DEPARTURE basis: Southampton 16-Sep is NEWLY PUBLISHED (this cache carried 'no Southampton call on this rotation' as PROVEN since the 24th pull - that is now withdrawn), Bremerhaven 2026-09-19 -> 2026-09-18, Antwerp 2026-09-17 -> 2026-09-20, Le Havre 2026-09-21 -> 2026-09-22, Vigo 2026-09-24 -> 2026-09-25. As with Manila 189/190, the carrier logs the Antwerp call under the preceding voyage 153 (arr 19-Sep, dep 20-Sep) - one physical call, discharge northbound and load southbound, one sailing for the customer | 2026-09-11 (40th pull, built-in Claude browser pane, in-page fetch() on hoeghautoliners.com/api/vessel - workspace bash sandbox failed to mount this session, non-transient, and Claude-in-Chrome was not connected): REAL CHANGE - Southampton (same physical call feeding the Yokohama 153 northbound row) arr/dep both now 2026-09-17 (was arr 15-Sep/dep 16-Sep) - dep +1d on this southbound leg. Antwerp/Bremerhaven/Le Havre/Vigo/Cartagena arrival CONFIRMED EXACTLY UNCHANGED, re-verified against the live rotation. [EVIDENCED: Src https://www.hoeghautoliners.com/api/vessel?vesselCode=YOKO&departureDate=2027-09-11&arrivalDate=2026-09-11 | Fetched 2026-09-11 | HTTP 200, re-confirmed on a second independent fetch] |