TAIHOU MARU
Cargo ship · Japan · AIS Class A
In short
TAIHOU MARU (Cargo ship, Japan flag) was last seen on AIS on , not moving, near Funabashi (North Pacific Ocean). Its crew-entered AIS destination is >JP FNB IE, with an ETA of Nov 16, 2026, 19:00 UTC; its reported draught is 3.7 m (voyage report via AISstream.io global terrestrial AIS, received Nov 16, 2026, 09:08 UTC). Its last detected port call was at Chiba: arrived Nov 14, 2026, left Nov 16, 2026.
- Vessel type
- Cargo ship
- Flag
- Japan
- Year built
- —
- Gross tonnage
- —
- Size, AIS-reported (length × beam)
- 76 m × 12 m
- Registered owner
- —
Last reported position: 35.6728° N, 139.9548° E · North Pacific Ocean · See on the map
Watch this ship
Get an email when TAIHOU 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
Following TAIHOU MARU over the last 24 hours would have sent 1 message.
- LeftChiba
Detected from AIS, as of Nov 16, 2026, 16:21 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for TAIHOU 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
- 35.6728° N, 139.9548° E
- Area
- North Pacific Ocean
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 52°
- Heading
- 35°
- Compass: course over ground 52°, heading 35°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 1 port call (Chiba).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows TAIHOU MARU's track before the last 30 days. Voydar has recorded its port calls since July 31, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
- Name
- TAIHOU MARU
- IMO numberWhat is an IMO number?
- 1128794
- MMSIWhat is an MMSI?
- 431028705
- Call signWhat is a call sign?
- JD5629
- Flag
- Japan
- Vessel type
- Cargo ship
- 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.76 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.12 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 ImabariAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at ImabariAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left KisarazuAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at KisarazuAIS-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, 16:23 UTC | Nov 16, 2026, 09:41 UTC | 41 h 18 min |
| Imabari JPIMB | Oct 16, 2026, 17:51 UTC | Oct 17, 2026, 00:54 UTC | 7 h 2 min |
| Kisarazu JPKZU | Oct 12, 2026, 05:02 UTC | Oct 14, 2026, 21:06 UTC | 2 d 16 h |
| Chiba JPCHB | Oct 10, 2026, 23:22 UTC | Oct 12, 2026, 03:27 UTC | 28 h 5 min |
| Kawasaki JPKWS | Oct 9, 2026, 17:08 UTC | Oct 10, 2026, 22:32 UTC | 29 h 24 min |
| Wakayama JPWAK | Sep 11, 2026, 22:04 UTC | Sep 14, 2026, 14:00 UTC | 2 d 15 h |
| Wakayama JPWAK | Jul 31, 2026, 06:36 UTC | Aug 30, 2026, 06:46 UTC | 30 d 0 h |
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 16, 2026, 09:08 UTC | Draught change Reported draught went from 4.3 m to 3.7 m while in port at Chiba. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 14, 2026, 19:34 UTC | Draught change Reported draught went from 3.8 m to 4.7 m while in port at Kisarazu. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Oct 12, 2026, 02:53 UTC | Draught change Reported draught went from 4.7 m to 3.8 m while in port at Chiba. Voydar infers the ship probably discharged 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 TAIHOU MARU?
- TAIHOU MARU is a cargo ship sailing under the flag of Japan.
- What sanctions and inspection records does Voydar hold for TAIHOU MARU?
- Voydar has no matched sanctions record displayed for TAIHOU 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 TAIHOU 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.
More Cargo ships
Other cargo ships with full Voydar profiles. A different set each day. All cargo ships
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/1128794Cite this page
TAIHOU MARU. Voydar (voydar.com). https://www.voydar.com/vessel/1128794-taihou-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.