Signet Constellation
Tug · United States · built 2011 · AIS Class A
In short
Signet Constellation (Tug, United States flag) was last seen on AIS on , not moving, near Ingleside (Gulf of Mexico). Its reported AIS draught is 5.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 18:40 UTC).
- Vessel type
- Tug
- Flag
- United States
- Year built
- 2011
- Gross tonnage
- —
- Size (length × beam)
- —
- Registered owner
- —
Watch this ship
Get an email when Signet Constellation arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 27.8188° N, 97.2001° W
- Area
- Gulf of Mexico
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0 kn
- Course
- 81°
- Heading
- 347°
Voydar detected no port call in the last 30 days.
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)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Signet Constellation
- IMO numberWhat is an IMO number?
- 9593139
- MMSIWhat is an MMSI?
- 367507520
- Call signWhat is a call sign?
- WDF9663
- Flag
- United States
- Vessel type
- Tug
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- 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 |
|---|---|---|
| Reported arrival at BrownsvilleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from BrownsvilleAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from Corpus ChristiAuthority-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 |
|---|---|---|---|---|
| Brownsville USBRO | Arrival | Oct 11, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Brownsville USBRO | Departure | Sep 25, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Departure | Aug 11, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Corpus Christi USCRP | Arrival | Aug 6, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Departure | Jul 30, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Arrival | Jul 30, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Departure | Jul 8, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Arrival | Jul 8, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Departure | Jun 16, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Arrival | Jun 16, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Departure | May 29, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Arrival | May 29, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: May 18, 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 Signet Constellation now?
- Signet Constellation (Tug, United States flag) was last seen on AIS on Oct 5, 2026, 07:17 UTC, not moving, near Ingleside (Gulf of Mexico).
- What kind of ship is Signet Constellation?
- Signet Constellation is a tug sailing under the flag of United States, built in 2011.
- What sanctions and inspection records does Voydar hold for Signet Constellation?
- Voydar has no matched sanctions record displayed for Signet Constellation 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 Signet Constellation. 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/9593139Using 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.