Saga Enterprise
General cargo ship · Bahamas · built 2006 · AIS Class A
In short
Saga Enterprise (General cargo ship, Bahamas flag) was last seen on AIS on , under way at 11.6 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 PABLB (Balboa), with an ETA of Nov 20, 2026, 12:00 UTC; its reported draught is 11.2 m (voyage report via AISstream.io global terrestrial AIS, received Nov 11, 2026, 05:24 UTC). ISM manager: SAGA SHIPHOLDING (NORWAY) AS (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Port Hueneme (departed Nov 9, 2026, 14:16 UTC) to PABLB (Balboa)
- Vessel type
- General cargo ship
- Flag
- Bahamas
- Year built
- 2006
- Gross tonnage
- 29,758
- Size (length × beam)
- 200 m × 30 m
- ISM manager
- SAGA SHIPHOLDING (NORWAY) AS
Last reported position: 27.2528° N, 115.4359° W · North Pacific Ocean · See on the map
Watch this ship
Saga Enterprise 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.
Voydar last heard Saga Enterprise on November 11, 2026. Our receivers cover coasts and busy waters, so alerts resume when it is next in range.
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 19, 2026, 19:06 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Saga Enterprise 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: the Voydar app
Last reported position
received- Position
- 27.2528° N, 115.4359° W
- Area
- North Pacific Ocean
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 11.6 kn
- Course
- 146°
- Heading
- 147°
- Compass: course over ground 146°, heading 147°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 3 port calls (Port Hueneme and Los Angeles).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Saga Enterprise's track before the last 30 days. Voydar has recorded its port calls since October 4, 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 200 mone tick every 25 m
Beam 30 mPlan outline, to scale
- Name
- Saga Enterprise
- IMO numberWhat is an IMO number?
- 9343481
- MMSIWhat is an MMSI?
- 311001606
- Call signWhat is a call sign?
- C6HY9
- Flag
- Bahamas
- Gross tonnageGross tonnage vs deadweight
- 29,758
- Length overall
- 200 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
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · high confidence · retrieved Nov 16, 2026
- 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 Port HuenemeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Port HuenemeAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Los AngelesAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Los AngelesAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Los AngelesAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Los AngelesAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from SavannahAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at SavannahAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from BaltimoreAuthority-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 | 11,882 t | 3,810 t | 171 days | 258 kg |
| 2019 | 8,480 t | 2,712 t | 121 days | 299 kg |
| 2020 | 6,849 t | 2,162 t | 95 days | 276 kg |
| 2021 | 3,299 t | 1,052 t | 38 days | 288 kg |
| 2022 | 0 t | 0 t | 0 days | — |
| 2023 | 2,640 t | 833 t | 42 days | 239 kg |
| 2024 | 3,387 t | 1,079 t | 52 days | 244 kg |
| 2025 | 11,020 t | 3,527 t | 174 days | 244 kg |
Technical efficiency: EEXI (6.04 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 2025 sits among the ships EU MRV lists as “General cargo ship”. Lower is less CO₂.
- CO₂ per nautical mile sailed243.8 kg per nautical mile
- Lowest reportedHighest reported
89% of the 2,956 ships in this group reported a lower figure.
Group: lower quartile 74.8 · median 110.6 · upper quartile 185.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 |
|---|---|---|---|
| Port Hueneme USNTD | Nov 8, 2026, 14:26 UTC | Nov 9, 2026, 14:16 UTC | 23 h 49 min |
| Los Angeles USLAX | Nov 3, 2026, 17:23 UTC | Nov 8, 2026, 05:16 UTC | 4 d 11 h |
| Los Angeles USLAX | Oct 26, 2026, 05:41 UTC | Nov 3, 2026, 17:23 UTC | 8 d 11 h |
| Vancouver CAVAN | Oct 4, 2026, 01:38 UTC | Oct 9, 2026, 19:34 UTC | 5 d 17 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 |
|---|---|---|---|---|
| Savannah USSAV | Departure | Jul 7, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Jul 6, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Departure | Jul 1, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Jun 27, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Arrival | Nov 2, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Departure | Nov 2, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Nov 12, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Nov 6, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Oct 27, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Arrival | Oct 23, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Francisco USSFO | Departure | Oct 20, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Francisco USSFO | Arrival | Oct 20, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 4, 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 6, 2026, 12:26 UTC | Draught change Reported draught went from 10.3 m to 11.3 m while in port at Los Angeles. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 28, 2026, 09:25 UTC | Draught change Reported draught went from 10.2 m to 8.6 m while in port at Los Angeles. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 9, 2026, 17:16 UTC | Draught change Reported draught went from 10.1 m to 6.2 m while in port at Vancouver. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | High (75%) |
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 Saga Enterprise?
- Saga Enterprise is a general cargo ship sailing under the flag of Bahamas, built in 2006 by Oshima Shipbuilding. The vessel is 200 m long with a beam of 30 m and has a gross tonnage of 29,758.
- Who is recorded as the owner or manager of Saga Enterprise?
- SAGA SHIPHOLDING (NORWAY) AS is recorded as ISM manager for Saga Enterprise (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 Saga Enterprise?
- Voydar has no matched sanctions record displayed for Saga Enterprise 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 Saga Enterprise. 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
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/9343481Cite this page
Saga Enterprise. Voydar (voydar.com). https://www.voydar.com/vessel/9343481-saga-enterprise. Retrieved November 19, 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.