JAMES CHARLES
Tug · United States · AIS Class A
In short
JAMES CHARLES (Tug, United States flag) was last seen on AIS on , under way at 5.7 kn, near Bridgeport (North Atlantic Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is NEW YORK; its reported draught is 4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 05:35 UTC).
Current voyage: from Manhattan/New York (departed Oct 3, 2026, 00:09 UTC) to NEW YORK
- Vessel type
- Tug
- Flag
- United States
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- 28 m × 8 m
- Registered owner
- —
Watch this ship
Get an email when JAMES CHARLES 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 JAMES CHARLES.
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
- 41.0916° N, 73.1144° W
- Area
- North Atlantic Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 5.7 kn
- Course
- 71°
- Heading
- 65°
Last 30 days: 10 port calls (Manhattan/New York, Carteret, New York, Bayonne, Perth Amboy, Port Richmond, Port Morris, Bronx, and Howland Hook).
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-upIdentity & particulars
- Name
- JAMES CHARLES
- IMO numberWhat is an IMO number?
- 7042875
- MMSIWhat is an MMSI?
- 367046090
- Call signWhat is a call sign?
- WDN9075
- Flag
- United States
- Vessel type
- Tug
- AIS ship type
- Towing (long/wide)
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 28 m
- Beam
- 8 m
- Year built
- —
United StatesA 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 |
|---|---|---|
| Left Manhattan/New YorkAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Manhattan/New YorkAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left CarteretAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at CarteretAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left New YorkAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at New YorkAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at PortlandAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from FORE RIVER, ME (INCLUDED IN STATISTICS FOR PORTLAND HARBOR, ME)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at PortlandAuthority-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.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Manhattan/New York USMNH | Oct 2, 2026, 22:45 UTC | Oct 3, 2026, 00:09 UTC | 1 h 24 min |
| Carteret USCSF | Oct 2, 2026, 11:13 UTC | Oct 2, 2026, 17:48 UTC | 6 h 35 min |
| New York USNYC | Oct 1, 2026, 07:16 UTC | Oct 1, 2026, 14:16 UTC | 6 h 59 min |
| New York USNYC | Sep 29, 2026, 14:46 UTC | Sep 29, 2026, 18:27 UTC | 3 h 41 min |
| Bayonne USBAY | Sep 27, 2026, 20:36 UTC | Sep 28, 2026, 14:35 UTC | 18 h 0 min |
| Perth Amboy USPAY | Sep 23, 2026, 11:23 UTC | Sep 23, 2026, 12:36 UTC | 1 h 12 min |
| Port Richmond USRI4 | Sep 23, 2026, 08:53 UTC | Sep 23, 2026, 09:45 UTC | 53 min |
| Bayonne USBAY | Sep 22, 2026, 22:35 UTC | Sep 23, 2026, 07:07 UTC | 8 h 32 min |
| Port Morris, Bronx USPM4 | Sep 22, 2026, 17:56 UTC | Sep 22, 2026, 21:34 UTC | 3 h 38 min |
| Howland Hook USH4H | Sep 21, 2026, 08:57 UTC | Sep 22, 2026, 11:05 UTC | 26 h 7 min |
| Brooklyn/New York USBOY | Jun 19, 2026, 20:15 UTC | Jun 20, 2026, 02:33 UTC | 6 h 18 min |
| Brooklyn/New York USBOY | Jun 13, 2026, 00:17 UTC | Jun 19, 2026, 20:11 UTC | 6 d 19 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Portland USPWM | Arrival | Jun 17, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| FORE RIVER, ME (INCLUDED IN STATISTICS FOR PORTLAND HARBOR, ME) | Departure | May 22, 2006(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPWM | Arrival | Oct 11, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| FORE RIVER, ME (INCLUDED IN STATISTICS FOR PORTLAND HARBOR, ME) | Arrival | Oct 8, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPWM | Arrival | Oct 7, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPWM | Departure | Oct 6, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| FORE RIVER, ME (INCLUDED IN STATISTICS FOR PORTLAND HARBOR, ME) | Arrival | Jul 18, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
| FORE RIVER, ME (INCLUDED IN STATISTICS FOR PORTLAND HARBOR, ME) | Departure | Jul 5, 2005(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: July 5, 2005.
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 JAMES CHARLES now?
- JAMES CHARLES (Tug, United States flag) was last seen on AIS on Oct 3, 2026, 05:50 UTC, under way at 5.7 kn, near Bridgeport (North Atlantic Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was NEW YORK (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 05:35 UTC). This report does not confirm the ship’s current route.
- What kind of ship is JAMES CHARLES?
- JAMES CHARLES is a tug sailing under the flag of United States. The vessel is 28 m long with a beam of 8 m.
- What sanctions and inspection records does Voydar hold for JAMES CHARLES?
- Voydar has no matched sanctions record displayed for JAMES CHARLES 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 JAMES CHARLES. Missing records do not establish whether the ship has been detained.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/7042875Using 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.