RAVEN
Other · United States · built 1993 · AIS Class A
In short
RAVEN (Other, United States flag) was last seen on AIS on , moored, in the port of Fort Lauderdale. Its crew-entered AIS destination is US SAN DIEGO; its reported draught is 3.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 00:39 UTC). It arrived there on Oct 1, 2026, 08:28 UTC.
- Vessel type
- Other
- Flag
- United States
- Year built
- 1993
- Gross tonnage
- 1,322
- Size (length × beam)
- 100 m × 100 m
- Registered owner
- —
Watch this ship
Get an email when RAVEN 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 RAVEN.
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
- 32.7015° N, 117.1594° W
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 214°
- Heading
- 70°
Last 30 days: at least 12 port calls (Fort Lauderdale and San Diego).
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
- RAVEN
- IMO numberWhat is an IMO number?
- 9044669
- MMSIWhat is an MMSI?
- 367373000
- Call signWhat is a call sign?
- WDQ6683
- Flag
- United States
- Vessel type
- Other
- Gross tonnageGross tonnage vs deadweight
- 1,322
- Length overall
- 100 m
- Beam
- 100 m
- Year built
- 1993
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 |
|---|---|---|
| Arrived at Fort LauderdaleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left San DiegoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at San DiegoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Fort LauderdaleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Fort LauderdaleAIS-detected | Voydar port-call detector (AIS geofence) | |
| Call sign changed from WDQ6683 to WDG6679 | AIS, 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.
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 |
|---|---|---|---|
| Fort Lauderdale USFLL | Oct 1, 2026, 08:28 UTC | in port | — |
| San Diego USSAN | Oct 1, 2026, 06:36 UTC | Oct 1, 2026, 08:28 UTC | 1 h 53 min |
| Fort Lauderdale USFLL | Oct 1, 2026, 05:46 UTC | Oct 1, 2026, 06:36 UTC | 50 min |
| San Diego USSAN | Oct 1, 2026, 05:09 UTC | Oct 1, 2026, 05:46 UTC | 37 min |
| Fort Lauderdale USFLL | Oct 1, 2026, 03:40 UTC | Oct 1, 2026, 05:09 UTC | 1 h 29 min |
| San Diego USSAN | Oct 1, 2026, 03:06 UTC | Oct 1, 2026, 03:40 UTC | 34 min |
| San Diego USSAN | Oct 1, 2026, 00:15 UTC | Oct 1, 2026, 02:37 UTC | 2 h 23 min |
| Fort Lauderdale USFLL | Sep 30, 2026, 19:04 UTC | Oct 1, 2026, 00:15 UTC | 5 h 11 min |
| San Diego USSAN | Sep 30, 2026, 15:21 UTC | Sep 30, 2026, 19:04 UTC | 3 h 43 min |
| Fort Lauderdale USFLL | Sep 30, 2026, 06:26 UTC | Sep 30, 2026, 15:21 UTC | 8 h 54 min |
| San Diego USSAN | Sep 30, 2026, 05:29 UTC | Sep 30, 2026, 06:26 UTC | 57 min |
| Fort Lauderdale USFLL | Sep 29, 2026, 20:32 UTC | Sep 30, 2026, 05:29 UTC | 8 h 57 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.
| When | What we observed | Confidence |
|---|---|---|
| Oct 1, 2026, 18:18 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 1, 2026, 12:17 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 1, 2026, 03:16 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 19:47 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 30, 2026, 06:17 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 29, 2026, 20:47 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 29, 2026, 01:32 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 29, 2026, 00:17 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 28, 2026, 23:20 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 28, 2026, 08:32 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 28, 2026, 08:23 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 28, 2026, 07:17 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 28, 2026, 05:47 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 28, 2026, 00:32 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 27, 2026, 23:32 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 27, 2026, 22:20 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 27, 2026, 14:02 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 27, 2026, 10:17 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 27, 2026, 07:50 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Sep 27, 2026, 05:47 UTC | Two positions This MMSI was reported in two places 3,639 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
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
- Where is RAVEN now?
- RAVEN (Other, United States flag) was last seen on AIS on Oct 2, 2026, 00:36 UTC, moored, in the port of Fort Lauderdale. The crew-entered destination was US SAN DIEGO (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 00:39 UTC). This report does not confirm the ship’s current route.
- What kind of ship is RAVEN?
- RAVEN is a other sailing under the flag of United States, built in 1993. The vessel is 100 m long with a beam of 100 m and has a gross tonnage of 1,322.
- What sanctions and inspection records does Voydar hold for RAVEN?
- Voydar has no matched sanctions record displayed for RAVEN from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for RAVEN. Missing records do not establish whether the ship has been detained.
Sister ships
Ships of the same class, Responder class oil recovery vessels (source: Wikidata).
- MELISSA CIMO 9043835Cargo ship · built 1992 · 1,335 GT
- SEAWARD ENDEAVORIMO 9043885Cargo ship · built 1992 · 1,335 GT
- SEAWARD EXPLORERIMO 9043873Anti-pollution vessel · built 1992 · 1,335 GT
- GULF RESPONDERIMO 9043847Anti-pollution vessel · built 1993 · 1,335 GT
- IMO 9043902IMO 9043902Anti-pollution vessel · built 1993 · 1,557 GT
- OAG RESPONDERIMO 9044645Cargo ship · built 1993
- Point NemoIMO 9043914Port tender · built 1993 · 1,335 GT
- SWIFT RESPONDERIMO 9043938Cargo ship · built 1993 · 1,335 GT
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/9044669Using 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.