Skip to content

Tauranga

Cargo ship · Norway · built 2001 · AIS Class A

IMO9249714MMSI258232000Call signLLLVLast AIS position Oct 1, 2026, 21:35 UTC

In short

Tauranga (Cargo ship, Norway flag) was last seen on AIS on , not moving, in the North Sea. Its crew-entered AIS destination is CH.16+90562689; its reported draught is 5 m (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:00 UTC). Registered owner: Napier (source: Wikidata).

Current voyage: from Hjelmeland (departed Sep 30, 2026, 02:59 UTC) to CH.16+90562689

Vessel type
Cargo ship
Flag
Norway
Year built
2001
Gross tonnage
886
Size (length × beam)
47 m × 10 m
Registered owner
Napier

Watch this ship

Get an email when Tauranga arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

We email you a link and a code. That creates a free account, no password or card, and follows Tauranga.

Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.

By continuing you accept the Terms and the Privacy policy.

Photo of TAURANGA
Photo: Cavernia · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

received
Position
59.2207° N, 6.1203° E
Area
North Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
0 kn
Course
183°
Heading
25°
59.2207° N, 6.1203° E
Open the full live map →

Last 30 days: 11 port calls (Hjelmeland, Agotnes, Langevag, Haugesund, Jelsa, and Espevik).

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)

Try the live demo, no sign-up

Identity & particulars

Name
Tauranga
IMO numberWhat is an IMO number?
9249714
MMSIWhat is an MMSI?
258232000
Flag
Norway
Vessel type
Cargo ship
AIS ship type
Cargo
Length overall
46.5 m
Beam
9.5 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.

Registered owner
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 HjelmelandAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at HjelmelandAIS-detectedVoydar port-call detector (AIS geofence)
Left AgotnesAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at AgotnesAIS-detectedVoydar port-call detector (AIS geofence)
Left LangevagAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at LangevagAIS-detectedVoydar port-call detector (AIS geofence)

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.

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
Hjelmeland NOHJLSep 29, 2026, 04:18 UTCSep 30, 2026, 02:59 UTC22 h 41 min
Agotnes NOAGOSep 28, 2026, 06:22 UTCSep 28, 2026, 18:46 UTC12 h 24 min
Langevag NOLAGSep 27, 2026, 09:19 UTCSep 28, 2026, 00:38 UTC15 h 20 min
Haugesund NOHAUSep 26, 2026, 21:29 UTCSep 27, 2026, 08:26 UTC10 h 57 min
Hjelmeland NOHJLSep 24, 2026, 05:55 UTCSep 25, 2026, 01:48 UTC19 h 54 min
Langevag NOLAGSep 20, 2026, 13:42 UTCSep 20, 2026, 23:01 UTC9 h 19 min
Hjelmeland NOHJLSep 14, 2026, 23:10 UTCSep 15, 2026, 23:33 UTC24 h 23 min
Jelsa NOJELSep 13, 2026, 11:16 UTCSep 14, 2026, 06:09 UTC18 h 53 min
Espevik NOESPSep 11, 2026, 12:53 UTCSep 13, 2026, 11:03 UTC46 h 10 min
Hjelmeland NOHJLSep 10, 2026, 00:26 UTCSep 10, 2026, 15:44 UTC15 h 18 min
Hjelmeland NOHJLSep 2, 2026, 21:01 UTCSep 3, 2026, 00:59 UTC3 h 58 min
Espevik NOESPAug 24, 2026, 07:33 UTCAug 24, 2026, 22:45 UTC15 h 12 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.

Frequently asked questions

Where is Tauranga now?
Tauranga (Cargo ship, Norway flag) was last seen on AIS on Oct 1, 2026, 21:35 UTC, not moving, in the North Sea. The crew-entered destination was CH.16+90562689 (voyage report via BarentsWatch AIS API, received Oct 1, 2026, 21:00 UTC). This report does not confirm the ship’s current route.
What kind of ship is Tauranga?
Tauranga is a cargo ship sailing under the flag of Norway, built in 2001. The vessel is 46.5 m long with a beam of 9.5 m and has a gross tonnage of 886.
Who is recorded as the owner or manager of Tauranga?
Napier is recorded as Registered owner for Tauranga (source: Wikidata). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for Tauranga?
Voydar has no matched sanctions record displayed for Tauranga from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Tauranga. 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/9249714
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