Naniwa Maru No. 65
Tanker · Japan · built 2008 · AIS Class A
In short
Naniwa Maru No. 65 (Tanker, Japan flag) was last seen on AIS on , at anchor, near Chiba (North Pacific Ocean). Its crew-entered AIS destination is >JP ANE OFF; its reported draught is 5.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 20:50 UTC).
Current voyage: from Chiba (departed Sep 30, 2026, 03:56 UTC) to >JP ANE OFF
- Vessel type
- Tanker
- Flag
- Japan
- Year built
- 2008
- Gross tonnage
- 3,768
- Size (length × beam)
- 105 m × 16 m
- Registered owner
- —
Watch this ship
Get an email when Naniwa Maru No. 65 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 Naniwa Maru No. 65.
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
- 35.5579° N, 140.0229° E
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- At anchor
- Speed
- 0 kn
- Course
- 173°
- Heading
- 336°
Last 30 days: 2 port calls (Chiba and Kawasaki).
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
- Naniwa Maru No. 65
- IMO numberWhat is an IMO number?
- 9460100
- MMSIWhat is an MMSI?
- 431000661
- Call signWhat is a call sign?
- JD2750
- Flag
- Japan
- Vessel type
- Tanker
- Gross tonnageGross tonnage vs deadweight
- 3,768
- Deadweight (DWT)
- Source: Wikidata, record Q105768226. Added to Voydar on September 23, 2026. Licence: CC0 1.0.4,999 t
- Length overall
- 104.9 m
- Beam
- 16 m
- Year built
- 2008
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 |
|---|---|---|
| Left ChibaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ChibaAIS-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 | Sep 28, 2026, 13:09 UTC | Sep 30, 2026, 03:56 UTC | 38 h 47 min |
| Kawasaki JPKWS | Sep 24, 2026, 12:48 UTC | Sep 26, 2026, 09:18 UTC | 44 h 29 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 |
|---|---|---|
| Sep 29, 2026, 01:55 UTC | Draught change Reported draught went from 6.5 m to 5.3 m while in port at Chiba. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 26, 2026, 09:20 UTC | Draught change Reported draught went from 6.3 m to 5.3 m after leaving Kawasaki. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
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
- Where is Naniwa Maru No. 65 now?
- Naniwa Maru No. 65 (Tanker, Japan flag) was last seen on AIS on Oct 1, 2026, 21:11 UTC, at anchor, near Chiba (North Pacific Ocean). The crew-entered destination was >JP ANE OFF (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 20:50 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Naniwa Maru No. 65?
- Naniwa Maru No. 65 is a tanker sailing under the flag of Japan, built in 2008. The vessel is 104.9 m long with a beam of 16 m and has a gross tonnage of 3,768.
- What sanctions and inspection records does Voydar hold for Naniwa Maru No. 65?
- Voydar has no matched sanctions record displayed for Naniwa Maru No. 65 from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Naniwa Maru No. 65. 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/9460100Using 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.