Navi
Bulk carrier · built 1967
In short
Navi (Bulk carrier) has no AIS position on record with Seadar.
- Vessel type
- Bulk carrier
- Flag
- —
- Year built
- 1967
- Gross tonnage
- 18,788
- Size (length × beam)
- 223 m
- Registered owner
- —
Watch this ship
Get an email when Navi 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 Navi.
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
No AIS position on record for this vessel. Identity and particulars are 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
- Navi
- IMO numberWhat is an IMO number?
- 6707961
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Bulk carrier
- Gross tonnageGross tonnage vs deadweight
- 18,788
- Length overall
- 223 m
- Beam
- —
- Year built
- 1967
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 Seadar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Reported departure from ChicagoAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from ChicagoAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from BURNS WATERWAY HARBOR, INAuthority-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 Seadar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Chicago USCHI | Departure | Dec 15, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Chicago USCHI | Departure | Dec 14, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BURNS WATERWAY HARBOR, IN | Departure | Dec 14, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Detroit USDET | Departure | Nov 25, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Detroit USDET | Arrival | Nov 25, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BURNS WATERWAY HARBOR, IN | Departure | Nov 13, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Chicago USCHI | Departure | Nov 6, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Chicago USCHI | Departure | Nov 4, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Milwaukee USMKE | Departure | Nov 4, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Milwaukee USMKE | Arrival | Nov 4, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Chicago USCHI | Arrival | Nov 4, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| INDIANA HARBOR, IN | Departure | Aug 7, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 1, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
About Navi
Algoma Navigator was a Canadian bulk carrier operated by Algoma Central. Like other bulk carriers, her potential cargoes included: coal/coke, aggregates, slag, iron ore/oxides, salt, fertilizers, grain products, gypsum, quartzite, or sand. The vessel was constructed by John Readhead & Sons in the United Kingdom in 1967 for the Cambay Steamship Company and launched as Demeterton. The vessel was enlarged in 1967 and sold in 1975 to the Upper Lakes Group which renamed the ship St. Lawrence Navigator. In 1979, the vessel was renamed Canadian Navigator after a rebuild. In 2011, the ship was sold to Algoma and became Algoma Navigator. In 2016, the bulk carrier was renamed Navi before being sold for scrap and broken up in 2016.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- Where is Navi now?
- Seadar has no displayable AIS position for Navi in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Navi?
- Navi is a bulk carrier, built in 1967 by John Readhead & Sons. The vessel is 223 m long and has a gross tonnage of 18,788.
- What sanctions and inspection records does Seadar hold for Navi?
- Seadar has no matched sanctions record displayed for Navi 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 Navi. 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/6707961Using 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.