Missy Enterprise
Bulk carrier · Panama · built 2013 · AIS Class A
In short
Missy Enterprise (Bulk carrier, Panama flag) was last seen on AIS on , moored, near Hachinohe (Sea of Japan). Its crew-entered AIS destination is JP HHE (Hachinohe); its reported draught is 8.6 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 02:45 UTC).
- Vessel type
- Bulk carrier
- Flag
- Panama
- Year built
- 2013
- Gross tonnage
- 20,992
- Size (length × beam)
- 181 m
- Registered owner
- —
Watch this ship
Get an email when Missy Enterprise reaches Hachinohe, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 40.5577° N, 141.4964° E
- Area
- Sea of Japan
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 196°
- Heading
- 286°
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)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Missy Enterprise
- IMO numberWhat is an IMO number?
- 9634634
- MMSIWhat is an MMSI?
- 351783000
- Call signWhat is a call sign?
- 3FUD2
- Flag
- Panama
- Vessel type
- Bulk carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 20,992
- Length overall
- 181.2 m
- Beam
- —
- Year built
- 2013
PanamaA 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 |
|---|---|---|
| Reported arrival at VancouverAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from PortlandAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at PortlandAuthority-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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred Oct 20, 2020衝突(単) · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)香川県直島町直島北西方沖(直島北西方灯浮標) 讃岐寺島灯台から真方位265°1,000m付近
貨物船MISSY ENTERPRISE衝突(灯浮標)Report published Aug 25, 2022
貨物船MISSY ENTERPRISEは、船長ほか20人(全員中華人民共和国籍)が乗り組み、水先人が水先を行い、離岸作業中、令和2年10月20日09時07分ごろ直島北西方灯浮標に衝突した。 MISSY ENTERPRISEは、左舷中央部外板に擦過傷を生じたが、死傷者はいなかった。 灯浮標は、手すり等の曲損等を生じた。
Source: 運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports). 出典：運輸安全委員会「船舶事故等調査報告書」（https://jtsb.mlit.go.jp/）。Seadar が項目を抽出・加工して作成 (Source: Japan Transport Safety Board marine accident reports; fields extracted and edited by Seadar). Licence: Public Data License 1.0 (公共データ利用規約 第1.0版, PDL1.0; compatible with CC BY 4.0).
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 4,570 t | 1,463 t | 77 days | 202 kg |
| 2019 | 3,323 t | 1,059 t | 65 days | 181 kg |
| 2020 | 3,361 t | 1,075 t | 62 days | 184 kg |
Technical efficiency: EIV (7 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
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 |
|---|---|---|---|---|
| Vancouver USVAN | Arrival | Dec 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Oct 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Arrival | Oct 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Aug 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Arrival | Aug 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Apr 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Arrival | Apr 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Feb 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Arrival | Feb 21, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Jan 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Arrival | Dec 24, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Nov 5, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: November 3, 2013.
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 Missy Enterprise now?
- Missy Enterprise (Bulk carrier, Panama flag) was last seen on AIS on Oct 6, 2026, 02:54 UTC, moored, near Hachinohe (Sea of Japan). The crew-entered destination was JP HHE (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 02:45 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Missy Enterprise?
- Missy Enterprise is a bulk carrier sailing under the flag of Panama, built in 2013 by Tsuneishi Kure Dock. The vessel is 181.2 m long and has a gross tonnage of 20,992.
- What sanctions and inspection records does Voydar hold for Missy Enterprise?
- Voydar has no matched sanctions record displayed for Missy Enterprise 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 Missy Enterprise. Missing records do not establish whether the ship has been detained.
Sister ships
Likely sister ships: built by Tsuneishi Kure Dock, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
- Felicia KIMO 9614309Bulk carrier · built 2012 · 20,992 GT
- KING MIMO 9614282Bulk carrier · built 2012 · 20,992 GT
- Ac AmityIMO 9623116Bulk carrier · built 2013 · 20,992 GT
- IVS KestrelIMO 9700926Bulk carrier · built 2014 · 20,981 GT
- Martin IslandIMO 9681704Bulk carrier · built 2014 · 20,981 GT
- ECO MONEGASQUEIMO 9701011Bulk carrier · built 2015 · 21,265 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/9634634Using 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.