Skip to content

CYGNET

Tug · United States · built 1999 · AIS Class A

IMO9204403MMSI368438450Call signWDQ5855Last AIS position Aug 28, 2026, 10:13 UTC

In short

CYGNET (Tug, United States flag) was last seen on AIS on , moored, near Ketchikan (Gulf of Alaska). Seadar has no more recent AIS position for this ship. Its current location cannot be established from this report.

Vessel type
Tug
Year built
1999
Gross tonnage
366
Size (length × beam)
33 m
Registered owner
—

Watch this ship

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

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 CYGNET
Photo: Pete Markham from Loretto, USA · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

received
Position
55.346° N, 131.6619° W
Area
Gulf of Alaska
Speed
0 kn
Course
223°
Heading
205°
55.346° N, 131.6619° W
Open the full live map →

Seadar detected no port call in the last 30 days.

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
CYGNET
IMO numberWhat is an IMO number?
9204403
MMSIWhat is an MMSI?
368438450
Call signWhat is a call sign?
WDQ5855
Vessel type
Tug
Length overall
33 m
Beam
—
Year built
1999

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 Seadar holds, newest first. Each line names its source; derived items say how they were derived.

DateEventSource
Reported arrival at Corpus ChristiAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from Corpus ChristiAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from Corpus ChristiAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Former name: Delta DeannaWikidata

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
Delta DeannaFormer nameJan 1, 1999Wikidata

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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Corpus Christi USCRPArrivalJun 24, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureJun 17, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureAug 11, 2015(date only)—USACE foreign traffic vessel entrances & clearances
GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON)ArrivalFeb 22, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureNov 14, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Galveston USGLSArrivalOct 6, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureOct 3, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureJun 9, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalJun 8, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureMay 7, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPArrivalMay 6, 2012(date only)—USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRPDepartureJan 31, 2012(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: July 2, 2009.

Frequently asked questions

Where is CYGNET now?
CYGNET (Tug, United States flag) was last seen on AIS on Aug 28, 2026, 10:13 UTC, moored, near Ketchikan (Gulf of Alaska). Seadar has no more recent AIS position for this ship. Its current location cannot be established from this report.
What kind of ship is CYGNET?
CYGNET is a tug sailing under the flag of United States, built in 1999. The vessel is 33 m long and has a gross tonnage of 366.
What sanctions and inspection records does Seadar hold for CYGNET?
Seadar has no matched sanctions record displayed for CYGNET 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 CYGNET. 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/9204403
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