Skip to content

Algoma Guardian

Bulk carrier · Canada · built 1987 · AIS Class A

IMO8505850MMSI316018031Call signCFK9698Last AIS position Oct 1, 2026, 15:33 UTC

In short

Algoma Guardian (Bulk carrier, Canada flag) was last seen on AIS on , under way at 12.8 kn, in the Great Lakes. Its crew-entered AIS destination is THUNDER BAY, with an ETA of Oct 3, 2026, 21:00 UTC; its reported draught is 8.1 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 08:47 UTC).

Current voyage: from Port Colborne (departed Oct 1, 2026, 02:59 UTC) to THUNDER BAY

Vessel type
Bulk carrier
Flag
Canada
Year built
1987
Gross tonnage
23,306
Size (length × beam)
222 m × 23 m
Registered owner
—

Watch this ship

Get an email when Algoma Guardian 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 Guardian.

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.

Photo of ALGOMA GUARDIAN
Photo: U.S. Army Corps of Engineers Detroit District · Licence: Public domain · via Wikimedia Commons

Last reported position

received
Position
41.8213° N, 82.4806° W
Area
Great Lakes
StatusWhat do AIS statuses mean?
Under way using engine
Speed
12.8 kn
Course
305°
Heading
305°
41.8213° N, 82.4806° W
Open the full live map →

Last 30 days: 5 port calls (Port Colborne, Saint-Catharines, Port Weller, Hamilton, and Sainte-Catherine).

Port calls are detected by Seadar 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-up

Identity & particulars

Name
Algoma Guardian
IMO numberWhat is an IMO number?
8505850
MMSIWhat is an MMSI?
316018031
Call signWhat is a call sign?
CFK9698
Flag
Canada
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
23,306
Length overall
222 m
Year built
1987

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.

DateEventSource
Left Port ColborneAIS-detectedSeadar port-call detector (AIS geofence)
Arrived at Port ColborneAIS-detectedSeadar port-call detector (AIS geofence)
Left Saint-CatharinesAIS-detectedSeadar port-call detector (AIS geofence)
Arrived at Saint-CatharinesAIS-detectedSeadar port-call detector (AIS geofence)
Left Port WellerAIS-detectedSeadar port-call detector (AIS geofence)
Arrived at Port WellerAIS-detectedSeadar port-call detector (AIS geofence)
Reported departure from ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Former name: GovikenWikidata
Former name: OmisaljWikidata

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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
GovikenFormer nameJan 1, 1997Wikidata
OmisaljFormer nameJan 1, 1987Wikidata

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Seadar saw them.

Source: Wikidata. Licence: CC0 1.0.

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.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Port Colborne CAPCOOct 1, 2026, 01:55 UTCOct 1, 2026, 02:59 UTC1 h 5 min
Saint-Catharines CASCASep 30, 2026, 19:13 UTCOct 1, 2026, 00:00 UTC4 h 47 min
Port Weller CAPWESep 30, 2026, 17:49 UTCSep 30, 2026, 19:13 UTC1 h 24 min
Hamilton CAHAMSep 28, 2026, 23:48 UTCSep 30, 2026, 15:25 UTC39 h 37 min
Sainte-Catherine CASCTSep 27, 2026, 00:11 UTCSep 27, 2026, 12:47 UTC12 h 36 min
Saint-Catharines CASCAJun 15, 2026, 15:02 UTCJun 15, 2026, 18:16 UTC3 h 14 min

Detected by Seadar 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
ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT)DepartureDec 11, 2016(date only)—USACE foreign traffic vessel entrances & clearances
ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT)ArrivalDec 11, 2016(date only)—USACE foreign traffic vessel entrances & clearances
ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT)DepartureSep 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT)ArrivalSep 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIDepartureJul 21, 2016(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIArrivalJul 21, 2016(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIDepartureMay 9, 2016(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIArrivalMay 9, 2016(date only)—USACE foreign traffic vessel entrances & clearances
TOLEDO HARBOR, OHDepartureNov 13, 2015(date only)—USACE foreign traffic vessel entrances & clearances
TOLEDO HARBOR, OHArrivalNov 11, 2015(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIDepartureAug 14, 2015(date only)—USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WIArrivalAug 14, 2015(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: January 25, 2002.

Frequently asked questions

Where is Algoma Guardian now?
Algoma Guardian (Bulk carrier, Canada flag) was last seen on AIS on Oct 1, 2026, 15:33 UTC, under way at 12.8 kn, in the Great Lakes. The crew-entered destination was THUNDER BAY (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 08:47 UTC). This report does not confirm the ship’s current route.
What kind of ship is Algoma Guardian?
Algoma Guardian is a bulk carrier sailing under the flag of Canada, built in 1987 by 3. Maj. The vessel is 222 m long with a beam of 23.1 m and has a gross tonnage of 23,306.
What sanctions and inspection records does Seadar hold for Algoma Guardian?
Seadar has no matched sanctions record displayed for Algoma Guardian 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 Guardian. 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/8505850
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using 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.

See plans