Taurus Leader
Car carrier · built 2015
In short
Taurus Leader (Car carrier) has no AIS position on record with Voydar.
- Vessel type
- Car carrier
- Flag
- —
- Year built
- 2015
- Gross tonnage
- 69,931
- Size (length × beam)
- 199 m × 36 m
- Registered owner
- —
Watch this ship
Get an email when Taurus Leader 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 Taurus Leader.
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.
Last reported position
No AIS position on record for this vessel. Identity and particulars are below.
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)
Try the live demo, no sign-upIdentity & particulars
- Name
- Taurus Leader
- IMO numberWhat is an IMO number?
- 9700550
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Gross tonnageGross tonnage vs deadweight
- 69,931
- Deadweight (DWT)
- Source: Wikidata, record Q104034364. Added to Voydar on September 23, 2026. Licence: CC0 1.0.19,278 t
- Length overall
- 199 m
- Beam
- 36 m
- Year built
- 2015
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.
| Date | Event | Source |
|---|---|---|
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported departure from New YorkAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at New YorkAuthority-reported | USACE 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.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 4,687 t | 1,492 t | 50 days | 297 kg |
| 2019 | 2,542 t | 812 t | 26 days | 281 kg |
| 2020 | 5,335 t | 1,704 t | 58 days | 278 kg |
Technical efficiency: EEDI (15.6 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | May 12, 2018, 18:15 UTC | KC20 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| New York USNYC | Departure | Oct 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Oct 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILG | Arrival | Sep 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILG | Departure | Sep 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Sep 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Departure | Sep 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Departure | Sep 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Arrival | Sep 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: September 23, 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 Taurus Leader now?
- Voydar has no displayable AIS position for Taurus Leader in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Taurus Leader?
- Taurus Leader is a car carrier, built in 2015 by Shin Kurushima Dockyard. The vessel is 199 m long with a beam of 36 m and has a gross tonnage of 69,931.
- What sanctions and inspection records does Voydar hold for Taurus Leader?
- Voydar has no matched sanctions record displayed for Taurus Leader 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 Taurus Leader. 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/9700550Using 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.