Algoma Vision
Cargo ship · Marshall Islands · built 2013 · AIS Class A
In short
Algoma Vision (Cargo ship, Marshall Islands 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 PUERTO QUETZAL, with an ETA of Oct 7, 2026, 12:00 UTC; its reported draught is 11.7 m (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 12:02 UTC).
Current voyage: from Long Beach (departed Sep 30, 2026, 03:44 UTC) to PUERTO QUETZAL
- Vessel type
- Cargo ship
- Flag
- Marshall Islands
- Year built
- 2013
- Gross tonnage
- 43,691
- Size (length × beam)
- 229 m × 32 m
- Registered owner
- —
Watch this ship
Get an email when Algoma Vision 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 Algoma Vision.
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
- 29.8832° N, 116.8344° W
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 11.6 kn
- Course
- 161°
- Heading
- 162°
Last 30 days: 1 port call (Long Beach).
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-upIdentity & particulars
- Name
- Algoma Vision
- IMO numberWhat is an IMO number?
- 9640944
- MMSIWhat is an MMSI?
- 538005113
- Call signWhat is a call sign?
- V7BC3
- Flag
- Marshall Islands
- Vessel type
- Cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 43,691
- Deadweight (DWT)
- Source: Wikidata, record Q84253967. Added to Voydar on September 23, 2026. Licence: CC0 1.0.71,348 t
- Length overall
- 229 m
- Beam
- 32 m
- Year built
- 2013
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 |
|---|---|---|
| Left Long BeachAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Long BeachAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from San FranciscoAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at San FranciscoAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from Redwood CityAuthority-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.
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 |
|---|---|---|---|
| Long Beach USLGB | Sep 27, 2026, 19:21 UTC | Sep 30, 2026, 03:44 UTC | 2 d 8 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 |
|---|---|---|---|---|
| San Francisco USSFO | Departure | Dec 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Francisco USSFO | Arrival | Dec 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Redwood City USRWC | Departure | Dec 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Redwood City USRWC | Arrival | Dec 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Redwood City USRWC | Departure | Dec 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Redwood City USRWC | Arrival | Dec 1, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Departure | Nov 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Arrival | Nov 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Oct 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Oct 21, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Richmond USRCH | Departure | Oct 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Richmond USRCH | Arrival | Oct 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: October 20, 2013.
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 |
|---|---|---|
| Sep 30, 2026, 02:11 UTC | Draught change Reported draught went from 8.4 m to 11.7 m while in port at Long Beach. Voydar infers the ship probably loaded 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
- Where is Algoma Vision now?
- Algoma Vision (Cargo ship, Marshall Islands flag) was last seen on AIS on Oct 1, 2026, 01:09 UTC, 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. The crew-entered destination was PUERTO QUETZAL (voyage report via AISstream.io global terrestrial AIS, received Sep 30, 2026, 12:02 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Algoma Vision?
- Algoma Vision is a cargo ship sailing under the flag of Marshall Islands, built in 2013 by Chengxi Shipyard. The vessel is 229 m long with a beam of 32 m and has a gross tonnage of 43,691.
- What sanctions and inspection records does Voydar hold for Algoma Vision?
- Voydar has no matched sanctions record displayed for Algoma Vision 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 Algoma Vision. 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/9640944Using 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.