Seaspan Eagle
Tug · Canada · built 2011 · AIS Class A
In short
Seaspan Eagle (Tug, Canada flag) was last seen on AIS on , not moving, near Vancouver (North Pacific Ocean). Its crew-entered AIS destination is SEASPAN; its reported draught is 5.4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 20:45 UTC).
Current voyage: from Thawwassen (departed Sep 22, 2026, 05:03 UTC) to SEASPAN
- Vessel type
- Tug
- Flag
- Canada
- Year built
- 2011
- Gross tonnage
- 441
- Size (length × beam)
- 28 m × 12 m
- Registered owner
- —
Watch this ship
Get an email when Seaspan Eagle 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 Seaspan Eagle.
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
- 49.3127° N, 123.1069° W
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0 kn
- Course
- 162°
- Heading
- 1°
Last 30 days: 1 port call (Thawwassen).
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
- Seaspan Eagle
- IMO numberWhat is an IMO number?
- 9432971
- MMSIWhat is an MMSI?
- 316020871
- Call signWhat is a call sign?
- CFN6642
- Flag
- Canada
- Vessel type
- Tug
- Gross tonnageGross tonnage vs deadweight
- 441
- Length overall
- 28 m
- Beam
- 12 m
- Year built
- 2011
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.
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 ThawwassenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ThawwassenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Reported departure from SeattleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at SeattleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from SeattleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Port State Control inspection at Seattle, Washington | USCG PSIX / CGMIX inspections |
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 |
|---|---|---|---|
| Nov 24, 2024 | Vessel Inspection | Seattle, Washington | clean |
| Sep 26, 2024 | Vessel Inspection | Seattle, Washington | clean |
| Feb 11, 2023 | Vessel InspectionPSC | Seattle, Washington | clean |
| Feb 3, 2023 | Vessel InspectionPSC | Seattle, Washington | clean |
| Jan 27, 2021 | Vessel InspectionPSC | Seattle, Washington | clean |
| May 20, 2020 | Vessel Operational Control | Seattle, Washington | clean |
| Aug 30, 2017 | Vessel InspectionPSC | Seattle, Washington | clean |
| May 15, 2015 | Vessel InspectionPSC | Seattle, Washington | 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 |
|---|---|---|---|
| Thawwassen CATWN | Sep 21, 2026, 03:53 UTC | Sep 22, 2026, 05:03 UTC | 25 h 10 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 |
|---|---|---|---|---|
| Seattle USSEA | Departure | Dec 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Dec 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Dec 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Dec 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Oct 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Oct 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Oct 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Oct 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Oct 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Oct 13, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Oct 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Oct 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: May 14, 2015.
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 Seaspan Eagle now?
- Seaspan Eagle (Tug, Canada flag) was last seen on AIS on Oct 1, 2026, 21:21 UTC, not moving, near Vancouver (North Pacific Ocean). The crew-entered destination was SEASPAN (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 20:45 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Seaspan Eagle?
- Seaspan Eagle is a tug sailing under the flag of Canada, built in 2011. The vessel is 28 m long with a beam of 12 m and has a gross tonnage of 441.
- What sanctions and inspection records does Voydar hold for Seaspan Eagle?
- Voydar has no matched sanctions record displayed for Seaspan Eagle 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. Seaspan Eagle has 8 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/9432971Using 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.