Where is Agawa Canyon now?

Voydar has no displayable AIS position for Agawa Canyon in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.

What kind of ship is Agawa Canyon?

Agawa Canyon is a ship, built in 1970 by Collingwood Shipbuilding. The vessel is 197.1 m long with a beam of 22 m and has a gross tonnage of 16,290.

What sanctions and inspection records does Voydar hold for Agawa Canyon?

Voydar has no matched sanctions record displayed for Agawa Canyon 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. No matched inspection records are displayed for Agawa Canyon. Missing records do not establish whether the ship has been detained.

Agawa Canyon

ship · built 1970

IMO7028556No AIS position on record

Open in Terminal

In short

Agawa Canyon (ship) has no AIS position on record with Voydar.

Vessel type: ship
Flag: —
Year built: 1970
Gross tonnage: 16,290
Size (length × beam): 197 m × 22 m
Registered owner: —

Watch this ship

Agawa Canyon has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

Free forever. No card. A free account follows up to 5 ships and ports.

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)Free forever. No card. New accounts include 14 days of Pro.

Try the live demo, no sign-up

Identity & particulars

Name: Agawa Canyon
IMO numberWhat is an IMO number?: 7028556
MMSIWhat is an MMSI?: —
Call signWhat is a call sign?: —
Flag: —
Vessel type: ship
Gross tonnageGross tonnage vs deadweight: 16,290
Length overall: 197.1 m
Beam: 22 m
Year built: 1970

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: Collingwood Shipbuilding
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
Dec 13, 2009	Reported departure from DetroitAuthority-reported	USACE foreign traffic vessel entrances & clearances
Dec 13, 2009	Reported arrival at DetroitAuthority-reported	USACE foreign traffic vessel entrances & clearances
Dec 7, 2009	Reported departure from MilwaukeeAuthority-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.

Reported by authorities Authority-reported

Port	Record	Date (UTC)	Berth	Source
Detroit USDET	Departure	Dec 13, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
Detroit USDET	Arrival	Dec 13, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
Milwaukee USMKE	Departure	Dec 7, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
Milwaukee USMKE	Arrival	Dec 7, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
TOLEDO HARBOR, OH	Departure	Dec 3, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
TOLEDO HARBOR, OH	Arrival	Dec 3, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
Chicago USCHI	Departure	Nov 29, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
Chicago USCHI	Departure	Nov 24, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
Chicago USCHI	Departure	Nov 24, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WI	Departure	Nov 15, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
DULUTH-SUPERIOR HARBOR, MN AND WI	Arrival	Nov 14, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances
Milwaukee USMKE	Departure	Nov 10, 2009(date only)	—	USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: January 1, 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 Agawa Canyon now?: Voydar has no displayable AIS position for Agawa Canyon in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Agawa Canyon?: Agawa Canyon is a ship, built in 1970 by Collingwood Shipbuilding. The vessel is 197.1 m long with a beam of 22 m and has a gross tonnage of 16,290.
What sanctions and inspection records does Voydar hold for Agawa Canyon?: Voydar has no matched sanctions record displayed for Agawa Canyon 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. No matched inspection records are displayed for Agawa Canyon. 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/7028556

View JSON API documentationFree without a key for occasional use; use an API key for more.

Follow by RSS Open data

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