Skip to content

Maersk Newhaven

General cargo ship · Singapore · built 2001 · AIS Class A

IMO9215880MMSI565475000Call sign9VPY4Last AIS position Oct 6, 2026, 16:25 UTC

In short

Maersk Newhaven (General cargo ship, Singapore flag) was last seen on AIS on , under way at 11.8 kn, in the North Pacific Ocean. Its crew-entered AIS destination is MXLZC (Lazaro Cardenas), with an ETA of Oct 12, 2026, 05:00 UTC; its reported draught is 8.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:38 UTC).

Current voyage: from Prince Rupert (departed Sep 24, 2026, 08:52 UTC) to MXLZC (Lazaro Cardenas)

Year built
2001
Gross tonnage
26,718
Size (length × beam)
209 m × 30 m
Registered owner
—

Watch this ship

Get an email when Maersk Newhaven reaches Lazaro Cardenas, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

Free forever. No card. A free account follows up to 5 ships and ports.

Photo of MAERSK NEWHAVEN
Photo: Reisender X from Germany · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

received
Position
27.6416° N, 117.8552° W
Area
North Pacific Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11.8 kn
Course
131°
Heading
131°
27.6416° N, 117.8552° W
Open the full live map →

Last 30 days: 1 port call (Prince Rupert).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name
Maersk Newhaven
IMO numberWhat is an IMO number?
9215880
MMSIWhat is an MMSI?
565475000
Call signWhat is a call sign?
9VPY4
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
26,718
Length overall
209 m
Beam
30 m
Year built
2001

A tag next to a value names the register that supplied it (hover or tap it for the record and date). Values without a tag come from the ship's own AIS broadcasts or from Wikidata. Position and identity are derived live from AIS.

Ownership & management

Each line shows where the fact comes from. Links backed by an identifier point to the company page.

Builder
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026

Timeline

Dated events for this ship from every source Voydar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Left Prince RupertAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Prince RupertAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from Los AngelesAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Los AngelesAuthority-reportedUSACE foreign traffic vessel entrances & clearances

Owner, operator and manager changes found by comparing yearly EU MRV reports are dated to the reporting year ("during 2025"), not to a day. Port calls here are the most recent only; the full lists are further down.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
201840,882 t13,102 t255 days416 kg
201926,299 t8,440 t159 days434 kg

Technical efficiency: EEDI (19.17 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

Port calls

Two kinds of evidence, kept apart: calls Voydar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Prince Rupert CAPRRSep 22, 2026, 20:35 UTCSep 24, 2026, 08:52 UTC36 h 16 min

Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalMar 13, 2021, 23:50 UTCSAHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Los Angeles USLAXDepartureNov 18, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalNov 18, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureOct 16, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalOct 14, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureJan 9, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalJan 9, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureDec 11, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalDec 11, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureNov 5, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXArrivalNov 5, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Los Angeles USLAXDepartureOct 1, 2012(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: November 16, 2008.

Behaviour at sea Voydar-derived

Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.

WhenWhat we observedConfidence
Sep 23, 2026, 02:08 UTC
Draught change

Reported draught went from 10.4 m to 8.3 m while in port at Prince Rupert. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

High (75%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.

How these are computed →

Frequently asked questions

Where is Maersk Newhaven now?
Maersk Newhaven (General cargo ship, Singapore flag) was last seen on AIS on Oct 6, 2026, 16:25 UTC, under way at 11.8 kn, in the North Pacific Ocean. The crew-entered destination was MXLZC (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 15:38 UTC). This report does not confirm the ship’s current route.
What kind of ship is Maersk Newhaven?
Maersk Newhaven is a general cargo ship sailing under the flag of Singapore, built in 2001 by HD Hyundai Heavy Industries. The vessel is 209 m long with a beam of 30 m and has a gross tonnage of 26,718.
What sanctions and inspection records does Voydar hold for Maersk Newhaven?
Voydar has no matched sanctions record displayed for Maersk Newhaven from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Maersk Newhaven. Missing records do not establish whether the ship has been detained.

Use this data

This page is also available as JSON, free, with the source and licence of every section. Sections whose sources do not permit redistribution are listed as withheld.

GET /api/v1/vessels/9215880
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro adds internal business use; API plans add building the data into your own products.

See plans