Where is Dayahai now?

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

What kind of ship is Dayahai?

Dayahai is a ship, built in 2002. The vessel is 189.9 m long and has a gross tonnage of 28,653.

What sanctions and inspection records does Seadar hold for Dayahai?

Seadar has no matched sanctions record displayed for Dayahai 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 Dayahai. Missing records do not establish whether the ship has been detained.

Dayahai

ship · built 2002

IMO9251872No AIS position on record

Open in Terminal

In short

Dayahai (ship) has no AIS position on record with Seadar.

Vessel type: ship
Flag: —
Year built: 2002
Gross tonnage: 28,653
Size (length × beam): 190 m
Registered owner: —

Watch this ship

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

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

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)

Try the live demo, no sign-up

Identity & particulars

Name: Dayahai
IMO numberWhat is an IMO number?: 9251872
MMSIWhat is an MMSI?: —
Call signWhat is a call sign?: —
Flag: —
Vessel type: ship
Gross tonnageGross tonnage vs deadweight: 28,653
Length overall: 189.9 m
Beam: —
Year built: 2002

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.

Date	Event	Source
Jul 3, 2015	Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported	USACE foreign traffic vessel entrances & clearances
Jun 22, 2015	Reported arrival at HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported	USACE foreign traffic vessel entrances & clearances
Jun 19, 2015	Reported departure from New OrleansAuthority-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 Seadar 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
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Departure	Jul 3, 2015(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Arrival	Jun 22, 2015(date only)	—	USACE foreign traffic vessel entrances & clearances
New Orleans USMSY	Departure	Jun 19, 2015(date only)	—	USACE foreign traffic vessel entrances & clearances
New Orleans USMSY	Arrival	Jun 19, 2015(date only)	—	USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRP	Departure	Jun 16, 2015(date only)	—	USACE foreign traffic vessel entrances & clearances
Corpus Christi USCRP	Arrival	Jun 15, 2015(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Departure	Jun 14, 2015(date only)	—	USACE foreign traffic vessel entrances & clearances
HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)	Arrival	Jun 9, 2015(date only)	—	USACE foreign traffic vessel entrances & clearances
Portland USPDX	Departure	Mar 11, 2011(date only)	—	USACE foreign traffic vessel entrances & clearances
Longview USLOG	Arrival	Mar 3, 2011(date only)	—	USACE foreign traffic vessel entrances & clearances
PORT OF KALAMA, WA	Departure	Aug 20, 2008(date only)	—	USACE foreign traffic vessel entrances & clearances
PORT OF KALAMA, WA	Arrival	Aug 18, 2008(date only)	—	USACE foreign traffic vessel entrances & clearances

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

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 Dayahai now?: Seadar has no displayable AIS position for Dayahai in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Dayahai?: Dayahai is a ship, built in 2002. The vessel is 189.9 m long and has a gross tonnage of 28,653.
What sanctions and inspection records does Seadar hold for Dayahai?: Seadar has no matched sanctions record displayed for Dayahai 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 Dayahai. 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/9251872

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