Sea Eagle II
Tug · Canada · built 1979 · AIS Class A
In short
Sea Eagle II (Tug, Canada flag) was last seen on AIS on , under way at 9.3 kn, in the Great Lakes. Its crew-entered AIS destination is DETROIT SMC ROUGE, with an ETA of Oct 5, 2026, 05:00 UTC; its reported draught is 6.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 13:47 UTC).
Current voyage: from Port Weller (departed Sep 20, 2026, 18:53 UTC) to DETROIT SMC ROUGE
- Vessel type
- Tug
- Flag
- Canada
- Year built
- 1979
- Gross tonnage
- 627
- Size (length × beam)
- 164 m × 23 m
- Registered owner
- —
Watch this ship
Get an email when Sea Eagle II 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 Sea Eagle II.
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
- 42.364° N, 80.5461° W
- Area
- Great Lakes
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 9.3 kn
- Course
- 249°
- Heading
- 248°
Last 30 days: 1 port call (Port Weller).
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
- Sea Eagle II
- IMO numberWhat is an IMO number?
- 7631860
- MMSIWhat is an MMSI?
- 316002063
- Call signWhat is a call sign?
- CZ9891
- Flag
- Canada
- Vessel type
- Tug
- Gross tonnageGross tonnage vs deadweight
- Source: Transport Canada — Canadian Register of Large Vessels (open data), record 800891. Added to Voydar on September 23, 2026. Licence: Open Government Licence – Canada 2.0.627
- Length overall
- 164 m
- Beam
- 23 m
- Year built
- 1979
CanadaA 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.
No owner, operator or manager is recorded for this vessel yet.
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 WellerAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Port WellerAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Port WellerAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Port WellerAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Port WellerAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Port WellerAIS-detected | Voydar port-call detector (AIS geofence) | |
| Inspection at DETROIT, Michigan | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at DETROIT, Michigan | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at DETROIT, Michigan | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at DETROIT, Michigan | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at DETROIT, Michigan | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at DETROIT, Michigan | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at DETROIT, Michigan | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at DETROIT, Michigan | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at DETROIT, Michigan | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Reported arrival at TOLEDO HARBOR, OHAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from TOLEDO HARBOR, OHAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT)Authority-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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Apr 25, 2025 | Vessel Inspection | DETROIT, Michigan | clean |
| Mar 26, 2025 | Vessel InspectionPSC | DETROIT, Michigan | clean |
| Dec 28, 2024 | Vessel InspectionPSC | DETROIT, Michigan | clean |
| Oct 18, 2024 | Vessel InspectionPSC | DETROIT, Michigan | clean |
| Oct 3, 2024 | Vessel InspectionPSC | DETROIT, Michigan | clean |
| Sep 19, 2024 | Vessel InspectionPSC | DETROIT, Michigan | clean |
| Aug 14, 2024 | Vessel InspectionPSC | DETROIT, Michigan | clean |
| Apr 16, 2021 | Vessel InspectionPSC | DETROIT, Michigan | clean |
| Mar 31, 2021 | Vessel InspectionPSC | DETROIT, Michigan | clean |
| Nov 29, 2020 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Apr 6, 2016 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Dec 15, 2015 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Jul 27, 2014 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Apr 6, 2014 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Jul 3, 2013 | Facility Transfer Monitor | Cleveland, Ohio | clean |
| Jul 2, 2013 | Vessel Operational Control | Cleveland, Ohio | clean |
| Apr 25, 2013 | Vessel Inspection | Cleveland, Ohio | clean |
| Apr 8, 2013 | Facility Transfer Monitor | Cleveland, Ohio | clean |
| Jan 30, 2013 | Vessel Transfer Monitor | TOLEDO, Ohio | clean |
| Jul 30, 2012 | Vessel Inspection | Cleveland, Ohio | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 Weller CAPWE | Sep 20, 2026, 18:22 UTC | Sep 20, 2026, 18:53 UTC | 30 min |
| Port Weller CAPWE | Jun 20, 2026, 10:18 UTC | Jun 20, 2026, 12:14 UTC | 1 h 55 min |
| Port Weller CAPWE | Jun 10, 2026, 13:00 UTC | Jun 10, 2026, 17:38 UTC | 4 h 38 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 |
|---|---|---|---|---|
| TOLEDO HARBOR, OH | Arrival | Dec 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TOLEDO HARBOR, OH | Departure | Dec 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT) | Departure | Dec 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT) | Arrival | Dec 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT) | Departure | Dec 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT) | Arrival | Dec 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT) | Departure | Nov 28, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT) | Arrival | Nov 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT) | Departure | Nov 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT) | Arrival | Nov 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TOLEDO HARBOR, OH | Arrival | Nov 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TOLEDO HARBOR, OH | Departure | Nov 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: March 28, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is Sea Eagle II now?
- Sea Eagle II (Tug, Canada flag) was last seen on AIS on Oct 4, 2026, 14:27 UTC, under way at 9.3 kn, in the Great Lakes. The crew-entered destination was DETROIT SMC ROUGE (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 13:47 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Sea Eagle II?
- Sea Eagle II is a tug sailing under the flag of Canada, built in 1979. The vessel is 164 m long with a beam of 23 m and has a gross tonnage of 627.
- What sanctions and inspection records does Voydar hold for Sea Eagle II?
- Voydar has no matched sanctions record displayed for Sea Eagle II 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. Sea Eagle II has 40 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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/7631860Using 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.