RAVEN
United States · built 1993 · AIS Class A
In short
RAVEN (Other, United States flag) was last seen on AIS on , moored, near San Diego (North Pacific Ocean). Its crew-entered AIS destination is SAN DIEGO; its reported draught is 3.8 m (voyage report via AISstream.io global terrestrial AIS, received Nov 17, 2026, 16:22 UTC). Managing owner (USCG): OCEAN MARINE SERVICES LLC (source: US Coast Guard — Merchant Vessels of the United States (documented vessels)).
Current voyage: from San Francisco (departed Oct 25, 2026, 04:04 UTC) to SAN DIEGO
- Vessel type
- —
- Flag
- United States
- Year built
- 1993
- Gross tonnage
- 1,322
- Size (length × beam)
- 100 m × 100 m
- Managing owner (USCG)
- OCEAN MARINE SERVICES LLC
Last reported position: 32.7013° N, 117.1597° W · North Pacific Ocean · See on the map
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.
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 17, 2026, 17:38 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for RAVEN 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
- 32.7013° N, 117.1597° W
- Area
- North Pacific Ocean
- Status
- MooredWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 201°
- Heading
- 71°
- Compass: course over ground 201°, heading 71°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 7 port calls (San Francisco).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows RAVEN'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-upIdentity & particulars
Length overall 100 mone tick every 10 m
- 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
- —
- Gross tonnageGross tonnage vs deadweight
- 1,322
- Length overall
- 100 m
- Beam
- 100 m
- Year built
- 1993
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)
- OCEAN MARINE SERVICES 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)
- Ocean Marine Services, LLC.(not linked to a company record)Source: FCC Universal Licensing System — ship station licences · since 2025 · 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.
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 |
|---|---|---|
| Call sign changed from WDQ6683 to WDG6679 | AIS, seen by Voydar | |
| Left San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at San FranciscoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Call sign changed from WDQ6683 to WDE5894 | 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 |
|---|---|---|---|
| San Francisco USSFO | Oct 24, 2026, 01:44 UTC | Oct 25, 2026, 04:04 UTC | 26 h 20 min |
| San Francisco USSFO | Oct 23, 2026, 11:41 UTC | Oct 24, 2026, 00:55 UTC | 13 h 14 min |
| San Francisco USSFO | Oct 23, 2026, 02:53 UTC | Oct 23, 2026, 03:50 UTC | 57 min |
| San Francisco USSFO | Oct 22, 2026, 23:32 UTC | Oct 23, 2026, 02:28 UTC | 2 h 56 min |
| San Francisco USSFO | Oct 22, 2026, 13:35 UTC | Oct 22, 2026, 21:59 UTC | 8 h 24 min |
| San Francisco USSFO | Oct 22, 2026, 10:05 UTC | Oct 22, 2026, 11:33 UTC | 1 h 28 min |
| San Francisco USSFO | Oct 21, 2026, 16:33 UTC | Oct 22, 2026, 07:13 UTC | 14 h 40 min |
| San Diego USSAN | Oct 13, 2026, 15:24 UTC | Oct 16, 2026, 20:09 UTC | 3 d 4 h |
| Fort Lauderdale USFLL | Oct 12, 2026, 19:50 UTC | Oct 13, 2026, 13:49 UTC | 17 h 59 min |
| Fort Lauderdale USFLL | Oct 12, 2026, 10:20 UTC | Oct 12, 2026, 19:35 UTC | 9 h 15 min |
| Fort Lauderdale USFLL | Oct 9, 2026, 13:11 UTC | Oct 12, 2026, 10:11 UTC | 2 d 21 h |
| San Diego USSAN | Oct 9, 2026, 11:17 UTC | Oct 9, 2026, 12:50 UTC | 1 h 33 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 30, 2026, 01:22 UTC | Two positions This MMSI was reported in two places 4,468 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 25, 2026, 04:39 UTC | Two positions This MMSI was reported in two places 4,171 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 23, 2026, 07:50 UTC | Two positions This MMSI was reported in two places 3,199 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 23, 2026, 05:27 UTC | Two positions This MMSI was reported in two places 3,199 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 21, 2026, 12:35 UTC | Two positions This MMSI was reported in two places 3,239 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 13, 2026, 10:54 UTC | Two positions This MMSI was reported in two places 3,638 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 13, 2026, 10:30 UTC | Two positions This MMSI was reported in two places 3,638 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 13, 2026, 07:24 UTC | Two positions This MMSI was reported in two places 3,638 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 13, 2026, 02:39 UTC | Two positions This MMSI was reported in two places 3,638 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 13, 2026, 00:36 UTC | Two positions This MMSI was reported in two places 3,638 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 12, 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%) |
| Oct 12, 2026, 03: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%) |
| Oct 11, 2026, 17:05 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 11, 2026, 14: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 11, 2026, 11: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%) |
| Oct 11, 2026, 10: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%) |
| Oct 11, 2026, 07: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%) |
| Oct 11, 2026, 02: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 10, 2026, 23:35 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 10, 2026, 17: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
- 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.
- Who is recorded as the owner or manager of RAVEN?
- OCEAN MARINE SERVICES LLC is recorded as Managing owner (USCG) for RAVEN (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 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, 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 RAVEN. 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
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/9044669Cite this page
RAVEN. Voydar (voydar.com). https://www.voydar.com/vessel/9044669-raven. Retrieved November 17, 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.