What kind of ship is MSC TURIN III?

MSC TURIN III is a container ship sailing under the flag of Cyprus, built in 2006. The vessel is 210 m long with a beam of 30 m and has a gross tonnage of 26,671.

Who is recorded as the owner or manager of MSC TURIN III?

FORT PARK SHIPPING CO PTE LTD is recorded as ISM manager for MSC TURIN III (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.

What sanctions and inspection records does Voydar hold for MSC TURIN III?

Voydar has no matched sanctions record displayed for MSC TURIN III 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 MSC TURIN III. Missing records do not establish whether the ship has been detained.

MSC TURIN III

Container ship · Cyprus · built 2006 · AIS Class A

IMO9301938MMSI212803000Call sign5BTQ6Last AIS position Oct 5, 2026, 13:03 UTC

Open in Terminal

In short

MSC TURIN III (Container ship, Cyprus flag) was last seen on AIS on Oct 5, 2026, 13:03 UTC, at anchor, near Pulau Sambu, Riau (Strait of Malacca). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is SGSIN EBGC, with an ETA of Oct 5, 2026, 11:30 UTC; its reported draught is 11 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 19:35 UTC). ISM manager: FORT PARK SHIPPING CO PTE LTD (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Current voyage: from Jakarta, Java (departed Oct 3, 2026, 15:00 UTC) to SGSIN EBGC

Vessel type: Container ship
Flag: Cyprus
Year built: 2006
Gross tonnage: 26,671
Size (length × beam): 210 m × 30 m
ISM manager: FORT PARK SHIPPING CO PTE LTD

Watch this ship

MSC TURIN III has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

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

Last reported position

received Oct 5, 2026, 13:03 UTC

Position: 1.2838° N, 104.0016° E
Area: Strait of Malacca
StatusWhat do AIS statuses mean?: At anchor
Speed: 0 kn
Course: 171°
Heading: 236°

1.2838° N, 104.0016° E

Open the full live map →

Last 30 days: 1 port call (Jakarta, Java).

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: MSC TURIN III
IMO numberWhat is an IMO number?: 9301938
MMSIWhat is an MMSI?: 212803000
Call signWhat is a call sign?: 5BTQ6
Flag: Cyprus
Vessel type: Detailed type from EU MRV (THETIS-MRV) emissionsContainer ship
AIS ship type: Cargo (hazardous cat. D)
Gross tonnageGross tonnage vs deadweight: 26,671
Deadweight (DWT): Source: Wikidata, record Q105303432. Added to Voydar on September 23, 2026. Licence: CC0 1.0.34,704 t
Length overall: 210 m
Beam: 30 m
Year built: 2006

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.

ISM manager: FORT PARK SHIPPING CO PTE LTD
Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Oct 5, 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.

Date	Event	Source
Oct 3, 2026, 15:00 UTC	Left Jakarta, JavaAIS-detected	Voydar port-call detector (AIS geofence)
Oct 1, 2026, 05:44 UTC	Arrived at Jakarta, JavaAIS-detected	Voydar port-call detector (AIS geofence)
Jun 18, 2026, 05:37 UTC	Reported departure from Hong KongAuthority-reported	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Jun 17, 2026, 17:00 UTC	Reported arrival at Hong KongAuthority-reported	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Mar 15, 2026, 14:27 UTC	Reported departure from Hong KongAuthority-reported	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Mar 15, 2026, 05:24 UTC	Reported arrival at Hong KongAuthority-reported	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Feb 1, 2026, 07:03 UTC	Reported departure from Hong KongAuthority-reported	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Jan 31, 2026, 17:04 UTC	Reported arrival at Hong KongAuthority-reported	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)

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.

Year	CO₂ emitted	Fuel burned	Time at sea	CO₂ / n mile
2018	40,330 t	12,891 t	218 days	506 kg
2019	41,710 t	13,359 t	302 days	404 kg
2020	43,091 t	13,800 t	285 days	421 kg
2021	9,757 t	3,116 t	55 days	452 kg
2022	1,972 t	627 t	19 days	305 kg
2025	0 t	0 t	0 days	—

Technical efficiency: EEXI (17.1 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

Port	Arrived	Departed	Time in port
Jakarta, Java IDJKT	Oct 1, 2026, 05:44 UTC	Oct 3, 2026, 15:00 UTC	2 d 9 h

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

Port	Record	Date (UTC)	Berth	Source
Hong Kong HKHKG	Arrival(matched by call sign)	Jun 17, 2026, 17:00 UTC	KC2	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKG	Arrival(matched by call sign)	Mar 15, 2026, 05:24 UTC	KC2	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKG	Arrival	Jan 31, 2026, 17:04 UTC	KC2	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
Hong Kong HKHKG	Arrival(matched by call sign)	Dec 28, 2025, 01:49 UTC	KC1	Hong Kong vessel arrivals & departures (incl. VTMS daily reports)
New Orleans USMSY	Arrival	Oct 23, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
New Orleans USMSY	Departure	Oct 23, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Departure	Oct 21, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Arrival	Oct 21, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Los Angeles USLAX	Departure	Jul 20, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Los Angeles USLAX	Arrival	Jul 20, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Los Angeles USLAX	Departure	Jun 8, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances
Los Angeles USLAX	Arrival	Jun 8, 2016(date only)	—	USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: April 27, 2016.

Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.

Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.

Frequently asked questions

Where is MSC TURIN III now?: MSC TURIN III (Container ship, Cyprus flag) was last seen on AIS on Oct 5, 2026, 13:03 UTC, at anchor, near Pulau Sambu, Riau (Strait of Malacca). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was SGSIN EBGC (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 19:35 UTC). This report does not confirm the ship’s current route.
What kind of ship is MSC TURIN III?: MSC TURIN III is a container ship sailing under the flag of Cyprus, built in 2006. The vessel is 210 m long with a beam of 30 m and has a gross tonnage of 26,671.
Who is recorded as the owner or manager of MSC TURIN III?: FORT PARK SHIPPING CO PTE LTD is recorded as ISM manager for MSC TURIN III (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for MSC TURIN III?: Voydar has no matched sanctions record displayed for MSC TURIN III 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 MSC TURIN III. 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/9301938

View JSON API documentationFree without a key for occasional use; use an API key for more.

Follow by RSS Open data

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