Skip to content

SV WAKILI

Chemical tanker · Liberia · built 2012 · AIS Class A

IMO9590711MMSI636023794Call sign5LPL5Last AIS position Sep 30, 2026, 17:12 UTC

In short

SV WAKILI (Chemical tanker, Liberia flag) was last seen on AIS on , under way at 1.9 kn, in the North Atlantic Ocean. 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 USHOU (Houston), with an ETA of Oct 15, 2026, 12:00 UTC; its reported draught is 7.6 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 10:17 UTC). ISM manager: LSC (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Current voyage: from Zandvliet (departed Sep 13, 2026, 06:04 UTC) to USHOU (Houston)

Vessel type
Chemical tanker
Year built
2012
Gross tonnage
29,762
Size (length × beam)
183 m × 32 m
ISM manager
LSC

Watch this ship

Get an email when SV WAKILI 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 SV WAKILI.

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

received
Position
34.1941° N, 9.4175° W
Area
North Atlantic Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
1.9 kn
Course
101°
Heading
21°
34.1941° N, 9.4175° W
Open the full live map →

Last 30 days: 1 port call (Zandvliet).

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
SV WAKILI
IMO numberWhat is an IMO number?
9590711
MMSIWhat is an MMSI?
636023794
Call signWhat is a call sign?
5LPL5
AIS ship type
Tanker
Gross tonnageGross tonnage vs deadweight
29,762
Length overall
183 m
Beam
32 m
Year built
2012

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
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
Source: EU MRV (THETIS-MRV) emissions · reporting year 2024 · reported · confidence 0.9 · retrieved Sep 28, 2026
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 ZandvlietAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ZandvlietAIS-detectedVoydar port-call detector (AIS geofence)
ISM manager: LSC (previously Latsco Marine Management Inc.)Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions)
Reported departure from Baton RougeAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Baton RougeAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from Corpus ChristiAuthority-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
20189,018 t2,866 t110 days312 kg
20202,546 t804 t36 days249 kg
20214,922 t1,557 t61 days273 kg
202210,782 t3,409 t121 days303 kg
20233,023 t957 t32 days343 kg
20247,728 t2,459 t92 days296 kg
20255,918 t1,869 t68 days298 kg

Technical efficiency: EEXI (4.8 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
Zandvliet BEZVTSep 4, 2026, 14:09 UTCSep 13, 2026, 06:04 UTC8 d 15 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

PortRecordDate (UTC)BerthSource
Baton Rouge USBTRDepartureMay 26, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Baton Rouge USBTRArrivalMay 24, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureMay 3, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalMay 3, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)DepartureApr 17, 2016(date only)—USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)ArrivalApr 16, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOADepartureApr 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Port Arthur USPOAArrivalApr 11, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVDepartureMar 31, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVArrivalMar 30, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYDepartureMar 21, 2016(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalMar 19, 2016(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: March 30, 2013.

Frequently asked questions

Where is SV WAKILI now?
SV WAKILI (Chemical tanker, Liberia flag) was last seen on AIS on Sep 30, 2026, 17:12 UTC, under way at 1.9 kn, in the North Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was USHOU (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 10:17 UTC). This report does not confirm the ship’s current route.
What kind of ship is SV WAKILI?
SV WAKILI is a chemical tanker sailing under the flag of Liberia, built in 2012 by HD Hyundai Mipo. The vessel is 183 m long with a beam of 32 m and has a gross tonnage of 29,762.
Who is recorded as the owner or manager of SV WAKILI?
LSC is recorded as ISM manager for SV WAKILI (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for SV WAKILI?
Voydar has no matched sanctions record displayed for SV WAKILI 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 SV WAKILI. 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/9590711
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