ANNA ROSE
Sailing vessel · United States · built 2003 · AIS Class B
In short
ANNA ROSE (Sailing vessel, United States flag) was last seen on AIS on , not moving, near Seattle (North Pacific Ocean). Its last detected port call was at New Haven: arrived Nov 15, 2026, left Nov 16, 2026. Managing owner (USCG): ANNA ROSE LLC (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)).
- Vessel type
- Sailing vessel
- Flag
- United States
- Year built
- 2003
- Gross tonnage
- 687
- Size (length × beam)
- 13 m × 4 m
- Managing owner (USCG)
- ANNA ROSE LLC

Last reported position: 47.6286° N, 122.3953° W · North Pacific Ocean · See on the map
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.
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 20, 2026, 20:43 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for ANNA ROSE 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: the Voydar app
Last reported position
received- Position
- 47.6286° N, 122.3953° W
- Area
- North Pacific Ocean
- Status
- UndefinedWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- —
- Heading
- —
Locator map: Natural Earth (public domain)
Last 30 days: at least 12 port calls (New Haven, Bridgeport, Brooklyn/New York, Tottenville, Staten Island, and Perth Amboy).
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. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 13 mone tick every 2 m
Beam 4 mPlan outline, to scale
- Name
- ANNA ROSE
- IMO numberWhat is an IMO number?
- 9269702
- MMSIWhat is an MMSI?
- 368276180
- Call signWhat is a call sign?
- WDN3910
- Flag
- United States
- Vessel type
- Sailing vessel
- Gross tonnageGross tonnage vs deadweight
- 687
- 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.
- Managing owner (USCG)
- ANNA ROSE LLC(not linked to a company record)Source: US Coast Guard — Merchant Vessels of the United States (documented vessels) · reported · high confidence · retrieved Oct 6, 2026Coast Guard documentation record (2026-09 file) matched to this ship by IMO number and call sign. The managing owner is the company the Coast Guard has on record for the ship's certificate of documentation.
- Ship radio licensee (FCC)
- Centerline Logistics Corporation(not linked to a company record)Source: FCC Universal Licensing System — ship station licences · since 2026 · reported · high confidence · retrieved Nov 17, 2026Licence matched to this ship by MMSI and call sign. The licensee holds the radio licence; it is not necessarily the owner.Rose Cay Maritime(Former)(not linked to a company record)Source: FCC Universal Licensing System — ship station licences · 2022–2026 · reported · high confidence · retrieved Nov 3, 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.
| Date | Event | Source |
|---|---|---|
| Left New HavenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at New HavenAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BridgeportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BridgeportAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Brooklyn/New YorkAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Brooklyn/New YorkAIS-detected | Voydar port-call detector (AIS geofence) | |
| Call sign changed from WDM9041 to WDR5016 | AIS, seen by Voydar | |
| Reported departure from New YorkAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at NEW CASTLE AREA, DEAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from NEW CASTLE AREA, DEAuthority-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 |
|---|---|---|---|
| New Haven USHVN | Nov 15, 2026, 12:30 UTC | Nov 16, 2026, 07:48 UTC | 19 h 19 min |
| Bridgeport USBDR | Nov 14, 2026, 16:19 UTC | Nov 15, 2026, 09:11 UTC | 16 h 52 min |
| Brooklyn/New York USBOY | Nov 13, 2026, 21:09 UTC | Nov 14, 2026, 00:12 UTC | 3 h 3 min |
| Tottenville, Staten Island USTTV | Nov 12, 2026, 03:59 UTC | Nov 13, 2026, 19:10 UTC | 39 h 12 min |
| Brooklyn/New York USBOY | Nov 8, 2026, 22:28 UTC | Nov 12, 2026, 02:53 UTC | 3 d 4 h |
| New Haven USHVN | Nov 6, 2026, 01:21 UTC | Nov 8, 2026, 12:40 UTC | 2 d 11 h |
| Bridgeport USBDR | Nov 5, 2026, 06:32 UTC | Nov 5, 2026, 22:33 UTC | 16 h 1 min |
| Tottenville, Staten Island USTTV | Nov 3, 2026, 14:05 UTC | Nov 4, 2026, 19:09 UTC | 29 h 3 min |
| Bridgeport USBDR | Nov 2, 2026, 07:52 UTC | Nov 3, 2026, 04:38 UTC | 20 h 46 min |
| Brooklyn/New York USBOY | Nov 1, 2026, 22:02 UTC | Nov 2, 2026, 02:20 UTC | 4 h 18 min |
| Tottenville, Staten Island USTTV | Oct 31, 2026, 05:12 UTC | Nov 1, 2026, 20:21 UTC | 39 h 8 min |
| Perth Amboy USPAY | Oct 30, 2026, 20:44 UTC | Oct 31, 2026, 04:55 UTC | 8 h 12 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| New York USNYC | Departure | Apr 12, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW CASTLE AREA, DE | Arrival | Jul 7, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW CASTLE AREA, DE | Departure | Jun 26, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW CASTLE AREA, DE | Arrival | Mar 11, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PISCATAQUA RIVER, ME AND NEW HAMPSHIRE | Departure | Mar 2, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW CASTLE AREA, DE | Arrival | Aug 19, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW CASTLE AREA, DE | Departure | Aug 11, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW CASTLE AREA, DE | Arrival | Jul 31, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW CASTLE AREA, DE | Arrival | Jul 17, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW CASTLE AREA, DE | Departure | Jul 9, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW CASTLE AREA, DE | Arrival | Jul 9, 2007(date only) | — | USACE foreign traffic vessel entrances & clearances |
| NEW CASTLE AREA, DE | Departure | Jul 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.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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 |
|---|---|---|
| Nov 20, 2026, 00:00 UTC | IMO used twice IMO 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,878 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 19, 2026, 00:00 UTC | IMO used twice IMO 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,878 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 18, 2026, 00:00 UTC | IMO used twice IMO 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,878 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 17, 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%) |
| Nov 16, 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%) |
| Nov 15, 2026, 00:00 UTC | IMO used twice IMO 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,934 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 14, 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%) |
| Nov 13, 2026, 00:00 UTC | IMO used twice IMO 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,881 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 12, 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%) |
| Nov 11, 2026, 00:00 UTC | IMO used twice IMO 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,875 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 10, 2026, 00:00 UTC | IMO used twice IMO 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,875 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 9, 2026, 00:00 UTC | IMO used twice IMO 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,875 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 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,884 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 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,934 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 9269702 was broadcast by two ships (MMSI 368248960 and 368276180) 3,936 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 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%) |
| Nov 3, 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%) |
| Nov 2, 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%) |
| Nov 1, 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%) |
| Oct 31, 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%) |
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.
Frequently asked questions
- 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.
- Who is recorded as the owner or manager of ANNA ROSE?
- ANNA ROSE LLC is recorded as Managing owner (USCG) for ANNA ROSE (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 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.
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.
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 Sailing vessels
Other sailing vessels with full Voydar profiles, those under the flag of United States first. A different set each day. All sailing vessels
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/9269702Cite this page
ANNA ROSE. Voydar (voydar.com). https://www.voydar.com/vessel/9269702-anna-rose. Retrieved November 20, 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 includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.