Where is CAPT. JACK HIGMAN now?

CAPT. JACK HIGMAN (Local vessel, United States flag) was last seen on AIS on Oct 6, 2026, 08:41 UTC, moored, near Baytown (Gulf of Mexico). The crew-entered destination was HOUSTON (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 19:20 UTC). This report does not confirm the ship’s current route.

What kind of ship is CAPT. JACK HIGMAN?

CAPT. JACK HIGMAN is a local vessel sailing under the flag of United States. The vessel is 114 m long with a beam of 34 m.

What sanctions and inspection records does Voydar hold for CAPT. JACK HIGMAN?

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

CAPT. JACK HIGMAN

Local vessel · United States · AIS Class A

IMONo IMOMMSI367323230Call signWDE2304Last AIS position Oct 6, 2026, 08:41 UTC

Open in Terminal

In short

CAPT. JACK HIGMAN (Local vessel, United States flag) was last seen on AIS on Oct 6, 2026, 08:41 UTC, moored, near Baytown (Gulf of Mexico). Its crew-entered AIS destination is HOUSTON; its reported draught is 3.1 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 19:20 UTC). Managing owner (USCG): HIGMAN BARGE LINES INC (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)).

Current voyage: from Freeport (departed Oct 4, 2026, 02:29 UTC) to HOUSTON

Vessel type: Local vessel
Flag: United States
Year built: —
Gross tonnage: —
Size (length × beam): 114 m × 34 m
Managing owner (USCG): HIGMAN BARGE LINES INC

Watch this ship

Get an email when CAPT. JACK HIGMAN 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 Oct 6, 2026, 08:41 UTC

Position: 29.7761° N, 95.0775° W
Area: Gulf of Mexico
StatusWhat do AIS statuses mean?: Moored
Speed: 5 kn
Course: 201°
Heading: 198°

29.7761° N, 95.0775° W

Open the full live map →

Last 30 days: 1 port call (Freeport).

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-up

Identity & particulars

Name: CAPT. JACK HIGMAN
IMO numberWhat is an IMO number?: —
MMSIWhat is an MMSI?: 367323230
Call signWhat is a call sign?: WDE2304
Flag: United States
Vessel type: Local vessel
Gross tonnageGross tonnage vs deadweight: —
Length overall: 114 m
Beam: 34 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.

Managing owner (USCG): HIGMAN BARGE LINES INC(not linked to a company record)
Source: US Coast Guard — Merchant Vessels of the United States (documented vessels) · reported · confidence 0.9 · retrieved Oct 6, 2026Coast Guard documentation record (2026-09 file) matched to this ship by call sign and vessel name. The managing owner is the company the Coast Guard has on record for the ship's certificate of documentation.
Ship radio licensee (FCC): Kirby Inland Marine, LP(not linked to a company record)
Source: FCC Universal Licensing System — ship station licences · since 2017 · reported · confidence 0.9 · retrieved Oct 6, 2026Licence matched to this ship by MMSI and call sign. The licensee holds the radio licence; it is not necessarily the owner.

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
Oct 4, 2026, 02:29 UTC	Left FreeportAIS-detected	Voydar port-call detector (AIS geofence)
Oct 2, 2026, 02:15 UTC	Arrived at FreeportAIS-detected	Voydar port-call detector (AIS geofence)

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.

Detected from AIS AIS-detected

Port	Arrived	Departed	Time in port
Freeport USFPO	Oct 2, 2026, 02:15 UTC	Oct 4, 2026, 02:29 UTC	2 d 0 h

Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.

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.

When	What we observed	Confidence
Sep 21, 2026, 00:39 UTC	AIS gap No AIS position received for 40 h 50 min while our receivers kept hearing other ships there (40 of 40 hours in coverage). Heard again 5 km away. Method seadar.behaviour.ais_gap v1	High (90%)

When

What we observed

Confidence

Sep 21, 2026, 00:39 UTC

AIS gap

No AIS position received for 40 h 50 min while our receivers kept hearing other ships there (40 of 40 hours in coverage). Heard again 5 km away.

Method seadar.behaviour.ais_gap v1

High (90%)

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 CAPT. JACK HIGMAN now?: CAPT. JACK HIGMAN (Local vessel, United States flag) was last seen on AIS on Oct 6, 2026, 08:41 UTC, moored, near Baytown (Gulf of Mexico). The crew-entered destination was HOUSTON (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 19:20 UTC). This report does not confirm the ship’s current route.
What kind of ship is CAPT. JACK HIGMAN?: CAPT. JACK HIGMAN is a local vessel sailing under the flag of United States. The vessel is 114 m long with a beam of 34 m.
Who is recorded as the owner or manager of CAPT. JACK HIGMAN?: HIGMAN BARGE LINES INC is recorded as Managing owner (USCG) for CAPT. JACK HIGMAN (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for CAPT. JACK HIGMAN?: Voydar has no matched sanctions record displayed for CAPT. JACK HIGMAN 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 CAPT. JACK HIGMAN. 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/mmsi-367323230

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