OSPREY
Tug · United States · built 2006 · AIS Class A
In short
OSPREY (Tug, United States flag) was last seen on AIS on , not moving, near Seattle (North Pacific Ocean). Its crew-entered AIS destination is US 0USS>016S; its reported draught is 5.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 12:16 UTC).
- Vessel type
- Tug
- Flag
- United States
- Year built
- 2006
- Gross tonnage
- 687
- Size (length × beam)
- 40 m × 10 m
- Registered owner
- —
Watch this ship
Get an email when OSPREY 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 OSPREY.
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
- 47.5891° N, 122.3456° W
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 0 kn
- Course
- 294°
- Heading
- 358°
Voydar detected no port call in the last 30 days.
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
- OSPREY
- IMO numberWhat is an IMO number?
- 9405394
- MMSIWhat is an MMSI?
- 367115000
- Call signWhat is a call sign?
- WDM6586
- Flag
- United States
- Vessel type
- Tug
- Gross tonnageGross tonnage vs deadweight
- 687
- Deadweight (DWT)
- Source: Wikidata, record Q86059640. Added to Voydar on September 23, 2026. Licence: CC0 1.0.705 t
- Length overall
- 40 m
- Beam
- 10 m
- Year built
- 2006
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.
| Date | Event | Source |
|---|---|---|
| Reported arrival at PAULSBORO, NJAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from PAULSBORO, NJAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIA, PA TO THE SEA)Authority-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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| PAULSBORO, NJ | Arrival | Oct 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PAULSBORO, NJ | Departure | Oct 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIA, PA TO THE SEA) | Arrival | Jan 4, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PAULSBORO, NJ | Departure | Dec 17, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Port Everglades USPEF | Arrival | Nov 1, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| POTOMAC RIVER BELOW WASHINGTON, DC | Arrival | Oct 6, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Ponce PRPSE | Departure | Sep 29, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New York USNYC | Arrival | Sep 8, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| San Juan PRSJU | Departure | Aug 31, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Miami USMIA | Arrival | Dec 25, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: December 25, 2009.
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 OSPREY now?
- OSPREY (Tug, United States flag) was last seen on AIS on Oct 4, 2026, 12:21 UTC, not moving, near Seattle (North Pacific Ocean). The crew-entered destination was US 0USS>016S (voyage report via AISstream.io global terrestrial AIS, received Oct 4, 2026, 12:16 UTC). This report does not confirm the ship’s current route.
- What kind of ship is OSPREY?
- OSPREY is a tug sailing under the flag of United States, built in 2006. The vessel is 40 m long with a beam of 10 m and has a gross tonnage of 687.
- What sanctions and inspection records does Voydar hold for OSPREY?
- Voydar has no matched sanctions record displayed for OSPREY 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 OSPREY. 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/9405394Using 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.