Skip to content

LONG ISLAND

Tug · United States · AIS Class A

IMO8644383MMSI367376440Call signWDI4974Last AIS position Oct 3, 2026, 15:32 UTC

In short

LONG ISLAND (Tug, United States flag) was last seen on AIS on , moored, near Baltimore (North Atlantic Ocean). Its crew-entered AIS destination is BALTIMORE,MD, with an ETA of Oct 2, 2026, 23:00 UTC; its reported draught is 4.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 15:08 UTC).

Vessel type
Tug
Year built
—
Gross tonnage
—
Size (length × beam)
32 m × 9 m
Registered owner
—

Watch this ship

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

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
39.2434° N, 76.5707° W
Area
North Atlantic Ocean
Speed
0 kn
Course
213°
Heading
85°
39.2434° N, 76.5707° W
Open the full live map →

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)

Try the live demo, no sign-up

Identity & particulars

Name
LONG ISLAND
IMO numberWhat is an IMO number?
8644383
MMSIWhat is an MMSI?
367376440
Call signWhat is a call sign?
WDI4974
Vessel type
Tug
AIS ship type
Towing
Length overall
32 m
Beam
9 m
Year built
—

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.

DateEventSource
Reported arrival at MORGAN CITY, LA, PORT OFAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at GalvestonAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from GalvestonAuthority-reportedUSACE 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

PortRecordDate (UTC)BerthSource
MORGAN CITY, LA, PORT OFArrivalMar 29, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Galveston USGLSArrivalMar 24, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Galveston USGLSDepartureMar 23, 2015(date only)—USACE foreign traffic vessel entrances & clearances
GULF INTRACOASTAL WATERWAY, MISSISSIPPI RIVER, LA., TO SABINE RIVER, TX (INCLUDED IN GULF INTRACOASTAL WATERWAY CONSOLIDATED REPORT)ArrivalJan 17, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Galveston USGLSDepartureJan 16, 2015(date only)—USACE foreign traffic vessel entrances & clearances
Galveston USGLSDepartureJan 8, 2015(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: January 8, 2015.

Behaviour at sea Voydar-derived

Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.

WhenWhat we observedConfidence
Oct 3, 2026, 00:00 UTC
IMO used twice

IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 822 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 2, 2026, 00:00 UTC
IMO used twice

IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 822 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 1, 2026, 00:00 UTC
IMO used twice

IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 717 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 30, 2026, 00:00 UTC
IMO used twice

IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 717 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 29, 2026, 00:00 UTC
IMO used twice

IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 717 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 28, 2026, 00:00 UTC
IMO used twice

IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 717 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 27, 2026, 00:00 UTC
IMO used twice

IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 717 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 26, 2026, 00:00 UTC
IMO used twice

IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 717 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 25, 2026, 00:00 UTC
IMO used twice

IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 717 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 24, 2026, 00:00 UTC
IMO used twice

IMO 8644383 was broadcast by two ships (MMSI 367092740 and 367376440) 717 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)

Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.

Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.

How these are computed →

Frequently asked questions

Where is LONG ISLAND now?
LONG ISLAND (Tug, United States flag) was last seen on AIS on Oct 3, 2026, 15:32 UTC, moored, near Baltimore (North Atlantic Ocean). The crew-entered destination was BALTIMORE,MD (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 15:08 UTC). This report does not confirm the ship’s current route.
What kind of ship is LONG ISLAND?
LONG ISLAND is a tug sailing under the flag of United States. The vessel is 32 m long with a beam of 9 m.
What sanctions and inspection records does Voydar hold for LONG ISLAND?
Voydar has no matched sanctions record displayed for LONG ISLAND 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 LONG ISLAND. 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/8644383
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