MEIWA MARU
Tanker · Japan · AIS Class A
In short
MEIWA MARU (Tanker, Japan flag) was last seen on AIS on , under way at 12.1 kn, near Takamatsu (North Pacific Ocean). Its crew-entered AIS destination is JP OTK OFF, with an ETA of Nov 17, 2026, 08:30 UTC; its reported draught is 3.2 m (voyage report via AISstream.io global terrestrial AIS, received Nov 16, 2026, 14:19 UTC).
Current voyage: from Chiba (departed Nov 15, 2026, 03:39 UTC) to JP OTK OFF
Last reported position: 34.4424° N, 134.1045° E · North Pacific Ocean · See on the map
Watch this ship
Get an email when MEIWA MARU 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 16, 2026, 14:53 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for MEIWA MARU 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
- 34.4424° N, 134.1045° E
- Area
- North Pacific Ocean
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 12.1 kn
- Course
- 283°
- Heading
- 282°
- Compass: course over ground 283°, heading 282°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 6 port calls (Chiba, Narashino, and Kawasaki).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows MEIWA MARU's track before the last 30 days. Voydar has recorded its port calls since July 15, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
- Name
- MEIWA MARU
- IMO numberWhat is an IMO number?
- 9658329
- MMSIWhat is an MMSI?
- 431004474
- Call signWhat is a call sign?
- JD3520
- Flag
- Japan
- Vessel type
- Tanker
- AIS ship type
- Tanker (hazardous cat. C)
- Gross tonnageGross tonnage vs deadweight
- —
- Length (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 16, 2026.64 m
- Beam (AIS-reported)
- Broadcast by the ship over AIS, not a register entry. Received via AISstream.io global terrestrial AIS on November 16, 2026.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.
AIS-reported: the size the ship itself broadcasts over AIS, in whole metres, as entered on board. It is not a register entry. Received via AISstream.io global terrestrial AIS on November 16, 2026.
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.
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 |
|---|---|---|
| Left ChibaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ChibaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left NarashinoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at NarashinoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KawasakiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KawasakiAIS-detected | Voydar port-call detector (AIS geofence) |
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 |
|---|---|---|---|
| Chiba JPCHB | Nov 14, 2026, 22:45 UTC | Nov 15, 2026, 03:39 UTC | 4 h 54 min |
| Narashino JPNAI | Nov 13, 2026, 01:50 UTC | Nov 14, 2026, 22:11 UTC | 44 h 21 min |
| Kawasaki JPKWS | Nov 12, 2026, 00:46 UTC | Nov 13, 2026, 00:47 UTC | 24 h 1 min |
| Kawasaki JPKWS | Nov 9, 2026, 22:06 UTC | Nov 10, 2026, 04:19 UTC | 6 h 12 min |
| Chiba JPCHB | Nov 8, 2026, 09:50 UTC | Nov 9, 2026, 21:34 UTC | 35 h 44 min |
| Chiba JPCHB | Oct 29, 2026, 23:22 UTC | Oct 30, 2026, 02:17 UTC | 2 h 55 min |
| Wakayama JPWAK | Oct 15, 2026, 09:19 UTC | Oct 16, 2026, 16:34 UTC | 31 h 15 min |
| Chiba JPCHB | Oct 9, 2026, 05:37 UTC | Oct 9, 2026, 08:06 UTC | 2 h 29 min |
| Chiba JPCHB | Sep 14, 2026, 22:18 UTC | Sep 15, 2026, 03:14 UTC | 4 h 57 min |
| Narashino JPNAI | Sep 14, 2026, 06:11 UTC | Sep 14, 2026, 21:53 UTC | 15 h 42 min |
| Kawasaki JPKWS | Sep 13, 2026, 22:15 UTC | Sep 14, 2026, 05:21 UTC | 7 h 7 min |
| Yokohama JPYOK | Jul 15, 2026, 07:47 UTC | Jul 16, 2026, 09:30 UTC | 25 h 42 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.
Predicted arrival
Voydar estimates arrival at Funabashi around Nov 17, 2026, 19:12 UTC, most likely between Nov 13, 2026, 03:02 UTC and Dec 6, 2026, 17:02 UTC. Based on 49 past transits between JPKWS and Funabashi seen in our port calls. The crew-reported ETA is Nov 13, 2026, 11:00 UTC.
Medium (51%) · Method seadar.behaviour.eta_prediction v1
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 MEIWA MARU?
- MEIWA MARU is a tanker sailing under the flag of Japan.
- What sanctions and inspection records does Voydar hold for MEIWA MARU?
- Voydar has no matched sanctions record displayed for MEIWA MARU 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 MEIWA MARU. 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
More Tankers
Other tankers with full Voydar profiles. A different set each day. All tankers
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/9658329Cite this page
MEIWA MARU. Voydar (voydar.com). https://www.voydar.com/vessel/9658329-meiwa-maru. Retrieved November 16, 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 adds internal business use; API plans add building the data into your own products.