Skip to content

ANNA ROSE

Sailing vessel · United States · built 2003 · AIS Class B

IMO9269702MMSI368276180Call signWDN3910Last AIS position Oct 5, 2026, 02:59 UTC

In short

ANNA ROSE (Sailing vessel, United States flag) was last seen on AIS on , not moving, in the port of Carteret. It arrived there on Oct 4, 2026, 17:41 UTC.

Vessel type
Sailing vessel
Year built
2003
Gross tonnage
687
Size (length × beam)
13 m × 4 m
Registered owner
—

Watch this ship

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

Photo of ANNA ROSE
Photo: Jim.henderson · Licence: CC0 · via Wikimedia Commons

Last reported position

received
Position
47.6287° N, 122.3953° W
Area
North Pacific Ocean
Speed
0 kn
Course
—
Heading
—
47.6287° N, 122.3953° W
Open the full live map →

Last 30 days: 8 port calls (Carteret, Marcus Hook, Brooklyn/New York, Bridgeport, and Tottenville, Staten Island).

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
ANNA ROSE
IMO numberWhat is an IMO number?
9269702
MMSIWhat is an MMSI?
368276180
Call signWhat is a call sign?
WDN3910
Vessel type
Sailing vessel
AIS ship type
Sailing
Length overall
13 m
Beam
4 m
Year built
2003

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
Arrived at CarteretAIS-detectedVoydar port-call detector (AIS geofence)
Left Marcus HookAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Marcus HookAIS-detectedVoydar port-call detector (AIS geofence)
Left Brooklyn/New YorkAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Brooklyn/New YorkAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from New YorkAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at NEW CASTLE AREA, DEAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from NEW CASTLE AREA, DEAuthority-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.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Carteret USCSFOct 4, 2026, 17:41 UTCin port—
Marcus Hook USMAHOct 2, 2026, 08:22 UTCOct 3, 2026, 14:31 UTC30 h 10 min
Brooklyn/New York USBOYSep 30, 2026, 12:47 UTCOct 1, 2026, 01:12 UTC12 h 26 min
Bridgeport USBDRSep 28, 2026, 13:43 UTCSep 29, 2026, 10:14 UTC20 h 32 min
Brooklyn/New York USBOYSep 27, 2026, 23:41 UTCSep 28, 2026, 02:51 UTC3 h 10 min
Tottenville, Staten Island USTTVSep 26, 2026, 04:37 UTCSep 27, 2026, 21:41 UTC41 h 4 min
Bridgeport USBDRSep 24, 2026, 19:15 UTCSep 25, 2026, 07:48 UTC12 h 33 min
Brooklyn/New York USBOYSep 23, 2026, 02:00 UTCSep 23, 2026, 05:40 UTC3 h 40 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
New York USNYCDepartureApr 12, 2011(date only)—USACE foreign traffic vessel entrances & clearances
NEW CASTLE AREA, DEArrivalJul 7, 2008(date only)—USACE foreign traffic vessel entrances & clearances
NEW CASTLE AREA, DEDepartureJun 26, 2008(date only)—USACE foreign traffic vessel entrances & clearances
NEW CASTLE AREA, DEArrivalMar 11, 2008(date only)—USACE foreign traffic vessel entrances & clearances
PISCATAQUA RIVER, ME AND NEW HAMPSHIREDepartureMar 2, 2008(date only)—USACE foreign traffic vessel entrances & clearances
NEW CASTLE AREA, DEArrivalAug 19, 2007(date only)—USACE foreign traffic vessel entrances & clearances
NEW CASTLE AREA, DEDepartureAug 11, 2007(date only)—USACE foreign traffic vessel entrances & clearances
NEW CASTLE AREA, DEArrivalJul 31, 2007(date only)—USACE foreign traffic vessel entrances & clearances
NEW CASTLE AREA, DEArrivalJul 17, 2007(date only)—USACE foreign traffic vessel entrances & clearances
NEW CASTLE AREA, DEDepartureJul 9, 2007(date only)—USACE foreign traffic vessel entrances & clearances
NEW CASTLE AREA, DEArrivalJul 9, 2007(date only)—USACE foreign traffic vessel entrances & clearances
NEW CASTLE AREA, DEDepartureJul 1, 2007(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: September 21, 2006.

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 4, 2026, 00:00 UTC
IMO used twice

IMO 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,871 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 3, 2026, 00:00 UTC
IMO used twice

IMO 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,895 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 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,823 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 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,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%)
Sep 30, 2026, 00:00 UTC
IMO used twice

IMO 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,880 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 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,932 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 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,919 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 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,880 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 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,871 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 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,892 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 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,919 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 ANNA ROSE now?
ANNA ROSE (Sailing vessel, United States flag) was last seen on AIS on Oct 5, 2026, 02:59 UTC, not moving, in the port of Carteret.
What kind of ship is ANNA ROSE?
ANNA ROSE is a sailing vessel sailing under the flag of United States, built in 2003. The vessel is 13 m long with a beam of 4 m and has a gross tonnage of 687.
What sanctions and inspection records does Voydar hold for ANNA ROSE?
Voydar has no matched sanctions record displayed for ANNA ROSE 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 ANNA ROSE. 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/9269702
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