Chie Maru No. 10
Tanker · Japan · built 2007 · AIS Class A
In short
Chie Maru No. 10 (Tanker, Japan flag) was last seen on AIS on , at anchor, in the port of Chiba. Its crew-entered AIS destination is JP FNB HINODE D, with an ETA of Nov 16, 2026, 23:00 UTC; its reported draught is 3.7 m (voyage report via AISstream.io global terrestrial AIS, received Nov 16, 2026, 14:59 UTC). It arrived there on Nov 16, 2026, 06:10 UTC.
Last reported position: 35.6035° N, 139.9197° E · North Pacific Ocean · See on the map
Watch this ship
Get an email when Chie Maru No. 10 arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for Chie Maru No. 10 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
- 35.6035° N, 139.9197° E
- Area
- North Pacific Ocean
- Status
- At anchorWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 66°
- Heading
- 302°
- Compass: course over ground 66°, heading 302°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 3 port calls (Chiba).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows Chie Maru No. 10's track before the last 30 days. Voydar has recorded its port calls since September 30, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 72.1 mone tick every 10 m
Beam 12 mPlan outline, to scale
- Name
- Chie Maru No. 10
- IMO numberWhat is an IMO number?
- 9414010
- MMSIWhat is an MMSI?
- 431000147
- Call signWhat is a call sign?
- JD2376
- Flag
- Japan
- Vessel type
- Tanker
- Gross tonnageGross tonnage vs deadweight
- 745
- Deadweight (DWT)
- Source: Wikidata, record Q85985149. Added to Voydar on October 25, 2026. Licence: CC0 1.0.1,929 t
- Length overall
- 72.1 m
- Beam
- 12 m
- Year built
- 2007
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.
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 |
|---|---|---|
| Arrived at ChibaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left ChibaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ChibaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left ChibaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ChibaAIS-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 16, 2026, 06:10 UTC | in port | — |
| Chiba JPCHB | Oct 27, 2026, 08:02 UTC | Oct 29, 2026, 13:50 UTC | 2 d 5 h |
| Chiba JPCHB | Oct 22, 2026, 11:04 UTC | Oct 27, 2026, 07:01 UTC | 4 d 19 h |
| Kawasaki JPKWS | Oct 14, 2026, 03:58 UTC | Nov 16, 2026, 06:10 UTC | 33 d 2 h |
| Chiba JPCHB | Sep 30, 2026, 09:53 UTC | Oct 1, 2026, 21:13 UTC | 35 h 20 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 |
|---|---|---|
| Nov 9, 2026, 23:22 UTC | Draught change Reported draught went from 4.9 m to 3.9 m while in port at Kawasaki. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Nov 5, 2026, 20:52 UTC | Draught change Reported draught went from 3.7 m to 4.9 m while in port at Kawasaki. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 23, 2026, 03:19 UTC | Draught change Reported draught went from 4.9 m to 3.7 m while in port at Kawasaki. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 22, 2026, 14:01 UTC | Draught change Reported draught went from 3.7 m to 4.9 m while in port at Kawasaki. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 21, 2026, 23:00 UTC | Draught change Reported draught went from 4.9 m to 3.7 m while in port at Kawasaki. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 14, 2026, 04:22 UTC | Draught change Reported draught went from 3.7 m to 4.9 m while in port at Kawasaki. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
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 Chie Maru No. 10?
- Chie Maru No. 10 is a tanker sailing under the flag of Japan, built in 2007. The vessel is 72.1 m long with a beam of 12 m and has a gross tonnage of 745.
- What sanctions and inspection records does Voydar hold for Chie Maru No. 10?
- Voydar has no matched sanctions record displayed for Chie Maru No. 10 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 Chie Maru No. 10. 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/9414010Cite this page
Chie Maru No. 10. Voydar (voydar.com). https://www.voydar.com/vessel/9414010-chie-maru-no10. 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.