Skip to content
voydar.com

JASEN AUGUST

Tug · United States · AIS Class A

IMO7329015MMSI366959090Call signWDR3593Last AIS position Nov 15, 2026, 17:53 UTC

In short

JASEN AUGUST (Tug, United States flag) was last seen on AIS on , not moving, near Galveston (Gulf of Mexico). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its last detected port call was at Brixham: arrived Nov 15, 2026, left Nov 15, 2026.

Data: AISHub contributors

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

Last reported position: 29.386° N, 94.7671° W · Gulf of Mexico · See on the map

Watch this ship

JASEN AUGUST has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.

What you would have been told

Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.

Detected from AIS, as of Nov 16, 2026, 15:16 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for JASEN AUGUST reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans

Get alerts on your phone: Voydar for iPhone

Last reported position

received
Position
29.386° N, 94.7671° W
Area
Gulf of Mexico
Status
Under way using engineWhat do AIS statuses mean?
Speed
0 kn
Course
179°
Heading
—
Compass: course over ground 179°
NArrow: course. Hull: heading. As broadcast on AIS.
29.386° N, 94.7671° W. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
29.386° N, 94.7671° W
See it live in 3D →

Last 30 days: 5 port calls (Brixham and Southwick).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Data: AISHub contributors

Pro shows JASEN AUGUST's track before the last 30 days. Voydar has recorded its port calls since October 9, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Length overall 17 mone tick every 2 m

Beam 7 mPlan outline, to scale

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
JASEN AUGUST
IMO numberWhat is an IMO number?
7329015
MMSIWhat is an MMSI?
366959090
Call signWhat is a call sign?
WDR3593
Vessel type
Tug
Length overall
17 m
Beam
7 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.

Ship radio licensee (FCC)
Ray Marine Boat Works LLC.(not linked to a company record)
Source: FCC Universal Licensing System — ship station licences · since 2026 · reported · high confidence · retrieved Nov 10, 2026Licence matched to this ship by MMSI and call sign. The licensee holds the radio licence; it is not necessarily the owner.

Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →

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
Left BrixhamAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BrixhamAIS-detectedVoydar port-call detector (AIS geofence)
Left BrixhamAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BrixhamAIS-detectedVoydar port-call detector (AIS geofence)
Left BrixhamAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BrixhamAIS-detectedVoydar port-call detector (AIS geofence)
Former name: DANIELLEAIS, seen by Voydar

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
DANIELLEFormer name, change seen on AISOct 20, 2026AIS (vessel's own broadcast)

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 Voydar saw them.

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

Time in port over the last 39 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
Brixham GBBRXNov 15, 2026, 08:27 UTCNov 15, 2026, 13:00 UTC4 h 33 min
Brixham GBBRXNov 8, 2026, 13:44 UTCNov 9, 2026, 13:42 UTC23 h 58 min
Brixham GBBRXNov 1, 2026, 05:36 UTCNov 6, 2026, 10:54 UTC5 d 5 h
Southwick GBSHKOct 30, 2026, 16:27 UTCOct 31, 2026, 15:06 UTC22 h 39 min
Brixham GBBRXOct 21, 2026, 11:48 UTCOct 25, 2026, 11:44 UTC3 d 23 h
Southwick GBSHKOct 9, 2026, 10:36 UTCOct 10, 2026, 12:33 UTC25 h 58 min

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.

WhenWhat we observedConfidence
Nov 9, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,664 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 8, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,637 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 6, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,639 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 5, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,619 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 4, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,625 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Nov 3, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,627 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

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

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,637 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

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

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,637 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 31, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,720 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 29, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,856 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 28, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,860 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 26, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,866 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 25, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,637 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 24, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,637 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 23, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,637 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 22, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,637 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 20, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,835 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 19, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,867 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 15, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,667 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 10, 2026, 00:00 UTC
IMO used twice

IMO 7329015 was broadcast by two ships (MMSI 232005400 and 366959090) 7,834 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

What kind of ship is JASEN AUGUST?
JASEN AUGUST is a tug sailing under the flag of United States. The vessel is 17 m long with a beam of 7 m.
What sanctions and inspection records does Voydar hold for JASEN AUGUST?
Voydar has no matched sanctions record displayed for JASEN AUGUST 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 JASEN AUGUST. Missing records do not establish whether the ship has been detained.

Full Vessel Report

A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.

See a sample report (PDF)

Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.

Every fact on this page stays free.

Know this ship?

Help other readers. Member posts are shown as member content, never as sourced data.

  • Date, place and an optional note
  • Members who know her can answer
  • Suggest a correctionChecked against sources before anything changes

More Tugs

Other tugs with full Voydar profiles. A different set each day. All tugs

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/7329015
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite this page

JASEN AUGUST. Voydar (voydar.com). https://www.voydar.com/vessel/7329015-jasen-august. Retrieved November 16, 2026.

Each fact above names its own source and date. Cite that primary source too when you rely on a fact.

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

Sources and attribution

  • Data: AISHub contributors (AISHub Terms of Use (2026-10-08))

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/7329015-jasen-august

Generated from voydar.com on Nov 16, 2026, 15:16 UTC