Lapis Arrow
Car carrier · Bahamas · built 2006 · AIS Class A
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)
- Vessel type
- Car carrier
- Flag
- Bahamas
- 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°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
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.
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-upIdentity & particulars
Length overall 176 mone tick every 25 m
Beam 31.1 mPlan outline, to scale
- Name
- Lapis Arrow
- IMO numberWhat is an IMO number?
- 9361809
- MMSIWhat is an MMSI?
- 308808000
- Call signWhat is a call sign?
- C6VH5
- Flag
- Bahamas
- Vessel type
- Detailed type from WikidataCar carrier
- Gross tonnageGross tonnage vs deadweight
- 41,000
- Deadweight (DWT)
- Source: Wikidata, record Q105765897. Added to Voydar on October 23, 2026. Licence: CC0 1.0.12,105 t
- 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.
| Date | Event | Source |
|---|---|---|
| Left San DiegoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at San DiegoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BeniciaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BeniciaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left IncheonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at IncheonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from BaltimoreAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at BaltimoreAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from San DiegoAuthority-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 | 30,472 t | 9,735 t | 232 days | 352 kg |
| 2019 | 30,653 t | 9,773 t | 214 days | 395 kg |
| 2020 | 9,347 t | 2,958 t | 80 days | 367 kg |
| 2021 | 9,202 t | 2,909 t | 89 days | 291 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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| San Diego USSAN | Nov 12, 2026, 01:23 UTC | Nov 12, 2026, 13:09 UTC | 11 h 46 min |
| Benicia USBNC | Nov 9, 2026, 09:41 UTC | Nov 10, 2026, 07:58 UTC | 22 h 18 min |
| Incheon KRINC | Oct 19, 2026, 20:43 UTC | Oct 20, 2026, 10:38 UTC | 13 h 54 min |
| Incheon KRINC | Oct 12, 2026, 18:54 UTC | Oct 13, 2026, 23:52 UTC | 28 h 58 min |
| Chermside AUCHE | Sep 29, 2026, 18:35 UTC | Sep 30, 2026, 06:23 UTC | 11 h 48 min |
| Port Melbourne AUPOR | Sep 23, 2026, 04:25 UTC | Sep 24, 2026, 19:12 UTC | 38 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Baltimore USBAL | Departure | Nov 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Nov 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Departure | Apr 20, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Diego USSAN | Arrival | Apr 19, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Hueneme USNTD | Departure | Apr 18, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Hueneme USNTD | Arrival | Apr 17, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CARQUINEZ STRAIT, CA | Departure | Apr 16, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CARQUINEZ STRAIT, CA | Arrival | Apr 16, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tacoma USTIW | Departure | Apr 12, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tacoma USTIW | Arrival | Apr 12, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Hueneme USNTD | Departure | Sep 8, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Hueneme USNTD | Arrival | Sep 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.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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.
| When | What we observed | Confidence |
|---|---|---|
| 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.
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.
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
More Car carriers
Other car carriers with full Voydar profiles. A different set each day. All car carriers
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/9361809Cite 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.