Skip to content
voydar.com

Lapis Arrow

Car carrier · Bahamas · built 2006 · AIS Class A

IMO9361809MMSI308808000Call signC6VH5Last AIS position Nov 12, 2026, 21:40 UTC

In short

Lapis Arrow (Car carrier, Bahamas flag) was last seen on AIS on , under way at 16.2 kn, in the North Pacific 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 KR USN (Ulsan), with an ETA of Dec 1, 2026, 12:00 UTC; its reported draught is 7.5 m (voyage report via AISstream.io global terrestrial AIS, received Nov 12, 2026, 15:11 UTC).

Current voyage: from San Diego (departed Nov 12, 2026, 13:09 UTC) to KR USN (Ulsan)

Data: AISHub contributors

Vessel type
Car carrier
Year built
2006
Gross tonnage
41,000
Size (length × beam)
176 m × 31 m
Registered owner
—

Last reported position: 30.936° N, 118.5676° W · North Pacific Ocean · See on the map

Shipping a car on this vessel?

Lapis Arrow has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.

What you would have been told

Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.

Detected from AIS, as of Nov 17, 2026, 17:39 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Lapis Arrow reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans

Get alerts on your phone: Voydar for iPhone

Last reported position

received
Position
30.936° N, 118.5676° W
Area
North Pacific Ocean
Status
Under way using engineWhat do AIS statuses mean?
Speed
16.2 kn
Course
236°
Heading
236°
Compass: course over ground 236°, heading 236°
NArrow: course. Hull: heading. As broadcast on AIS.
30.936° N, 118.5676° W. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
30.936° N, 118.5676° W
See it live in 3D →

Last 30 days: 3 port calls (San Diego, Benicia, and Incheon).

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

Data: AISHub contributors

Pro shows Lapis Arrow's track before the last 30 days. Voydar has recorded its port calls since September 23, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Length overall 176 mone tick every 25 m

Beam 31.1 mPlan outline, to scale

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
Lapis Arrow
IMO numberWhat is an IMO number?
9361809
MMSIWhat is an MMSI?
308808000
Call signWhat is a call sign?
C6VH5
Gross tonnageGross tonnage vs deadweight
41,000
Length overall
176 m
Beam
31.1 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.

Builder
Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026

Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →

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 San DiegoAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at San DiegoAIS-detectedVoydar port-call detector (AIS geofence)
Left BeniciaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BeniciaAIS-detectedVoydar port-call detector (AIS geofence)
Left IncheonAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at IncheonAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from BaltimoreAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at BaltimoreAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from San DiegoAuthority-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.

CO₂ emitted per reporting year, tonnes (EU MRV, as reported and verified). The table below has every figure.
YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
201830,472 t9,735 t232 days352 kg
201930,653 t9,773 t214 days395 kg
20209,347 t2,958 t80 days367 kg
20219,202 t2,909 t89 days291 kg

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

Compared with ships of its type

Where this ship’s reported CO₂ intensity for 2021 sits among the ships EU MRV lists as “Vehicle carrier”. Lower is less CO₂.

CO₂ per tonne of cargo carried one nautical mile74.44 g per tonne-nautical mile
Lowest reportedHighest reported

70% of the 466 ships in this group reported a lower figure.

Group: lower quartile 47.95 · median 59.95 · upper quartile 84.04

CO₂ per nautical mile sailed291.1 kg per nautical mile
Lowest reportedHighest reported

31% of the 466 ships in this group reported a lower figure.

Group: lower quartile 282.4 · median 325.1 · upper quartile 360.8

Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated

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

Time in port over the last 57 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
San Diego USSANNov 12, 2026, 01:23 UTCNov 12, 2026, 13:09 UTC11 h 46 min
Benicia USBNCNov 9, 2026, 09:41 UTCNov 10, 2026, 07:58 UTC22 h 18 min
Incheon KRINCOct 19, 2026, 20:43 UTCOct 20, 2026, 10:38 UTC13 h 54 min
Incheon KRINCOct 12, 2026, 18:54 UTCOct 13, 2026, 23:52 UTC28 h 58 min
Chermside AUCHESep 29, 2026, 18:35 UTCSep 30, 2026, 06:23 UTC11 h 48 min
Port Melbourne AUPORSep 23, 2026, 04:25 UTCSep 24, 2026, 19:12 UTC38 h 48 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
Baltimore USBALDepartureNov 25, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Baltimore USBALArrivalNov 23, 2016(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANDepartureApr 20, 2015(date only)—USACE foreign traffic vessel entrances & clearances
San Diego USSANArrivalApr 19, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Port Hueneme USNTDDepartureApr 18, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Port Hueneme USNTDArrivalApr 17, 2015(date only)—USACE foreign traffic vessel entrances & clearances
CARQUINEZ STRAIT, CADepartureApr 16, 2015(date only)—USACE foreign traffic vessel entrances & clearances
CARQUINEZ STRAIT, CAArrivalApr 16, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Tacoma USTIWDepartureApr 12, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Tacoma USTIWArrivalApr 12, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Port Hueneme USNTDDepartureSep 8, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Port Hueneme USNTDArrivalSep 8, 2014(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: September 28, 2006.

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
Nov 10, 2026, 08:09 UTC
Draught change

Reported draught went from 8.9 m to 7.9 m after leaving Benicia. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Oct 13, 2026, 08:02 UTC
Draught change

Reported draught went from 7.8 m to 8.5 m while in port at Incheon. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

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

What kind of ship is Lapis Arrow?
Lapis Arrow is a car carrier sailing under the flag of Bahamas, built in 2006 by Uljanik. The vessel is 176 m long with a beam of 31.1 m and has a gross tonnage of 41,000.
What sanctions and inspection records does Voydar hold for Lapis Arrow?
Voydar has no matched sanctions record displayed for Lapis Arrow 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 Lapis Arrow. Missing records do not establish whether the ship has been detained.

Full Vessel Report

A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.

See a sample report (PDF)

Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.

Every fact on this page stays free.

Know this ship?

Help other readers. Member posts are shown as member content, never as sourced data.

  • Date, place and an optional note
  • Members who know her can answer
  • Suggest a correctionChecked against sources before anything changes

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/9361809
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite this page

Lapis Arrow. Voydar (voydar.com). https://www.voydar.com/vessel/9361809-lapis-arrow. Retrieved November 17, 2026.

Each fact above names its own source and date. Cite that primary source too when you rely on a fact.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.

See plans

Sources and attribution

  • Data: AISHub contributors (AISHub Terms of Use (2026-10-08))
  • Wikidata (CC0 1.0)

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9361809-lapis-arrow

Generated from voydar.com on Nov 17, 2026, 17:39 UTC