OREGON II
Naval vessel · United States · AIS Class A
In short
OREGON II (Naval vessel, United States flag) was last seen on AIS on , under way at 4.5 kn, in the Gulf of Mexico. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is PASCAGOULA, MS, with an ETA of Oct 7, 2026, 14:00 UTC; its reported draught is 4.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 20:08 UTC).
- Vessel type
- Naval vessel
- Flag
- United States
- Year built
- —
- Gross tonnage
- 729
- Size (length × beam)
- 52 m × 10 m
- Registered owner
- —
Watch this ship
Get an email when OREGON II 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 OREGON II.
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
- 30.2285° N, 86.4714° W
- Area
- Gulf of Mexico
- StatusWhat do AIS statuses mean?
- Engaged in fishing
- Speed
- 4.5 kn
- Course
- 234°
- Heading
- 225°
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
- OREGON II
- IMO numberWhat is an IMO number?
- 6728068
- MMSIWhat is an MMSI?
- 303976000
- Call signWhat is a call sign?
- WTDO
- Flag
- United States
- Vessel type
- Naval vessel
- AIS ship type
- Noncombatant
- Gross tonnageGross tonnage vs deadweight
- 729
- Length overall
- 52 m
- Beam
- 10 m
- Year built
- —
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.
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
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 |
|---|---|---|
| Inspection at Mobile, Alabama | USCG PSIX / CGMIX inspections | |
| Inspection at Mobile, Alabama | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Inspection at Mobile, Alabama | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections | |
| Inspection at WASHINGTON, District of Columbia | USCG PSIX / CGMIX inspections |
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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Mar 10, 2022 | Vessel Inspection | Mobile, Alabama | clean |
| Jun 14, 2017 | Vessel Inspection | Mobile, Alabama | clean |
| Jun 11, 2010 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| May 16, 2006 | Vessel Inspection | Mobile, Alabama | clean |
| Sep 8, 2003 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Jul 22, 2001 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Jan 2, 2001 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Dec 3, 1995 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Jun 21, 1995 | Incident Investigation | WASHINGTON, District of Columbia | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
About OREGON II
NOAAS Oregon II (R 332) is an American fisheries research vessel in commission in the National Oceanic and Atmospheric Administration (NOAA) fleet since 1977. Prior to her NOAA career, she was delivered to the United States Fish and Wildlife Service's Bureau of Commercial Fisheries in 1967 as US FWS Oregon II, but not commissioned. She was transferred to NOAA in 1970, but was not placed in commission until 1977.
Summary from Wikipedia, licensed CC BY-SA.
Frequently asked questions
- Where is OREGON II now?
- OREGON II (Naval vessel, United States flag) was last seen on AIS on Oct 2, 2026, 22:16 UTC, under way at 4.5 kn, in the Gulf of Mexico. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was PASCAGOULA, MS (voyage report via AISstream.io global terrestrial AIS, received Oct 2, 2026, 20:08 UTC). This report does not confirm the ship’s current route.
- What kind of ship is OREGON II?
- OREGON II is a naval vessel sailing under the flag of United States. The vessel is 52 m long with a beam of 10 m and has a gross tonnage of 729.
- What sanctions and inspection records does Voydar hold for OREGON II?
- Voydar has no matched sanctions record displayed for OREGON II 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. OREGON II has 9 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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/6728068Using 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.