Skip to content

Fuyo Maru No. 5

Bulk carrier · Japan · built 1994 · AIS Class A

IMO9060259MMSI431100123Call signJG5298Last AIS position Oct 3, 2026, 05:59 UTC

In short

Fuyo Maru No. 5 (Bulk carrier, Japan flag) was last seen on AIS on , under way at 12.1 kn, near Uraga (North Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is JP MKW OFF; its reported draught is 6.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 05:21 UTC).

Current voyage: from Yokohama (departed Oct 3, 2026, 05:02 UTC) to JP MKW OFF

Vessel type
Bulk carrier
Flag
Japan
Year built
1994
Gross tonnage
3,568
Size (length × beam)
98 m × 16 m
Registered owner
—

Watch this ship

Fuyo Maru No. 5 has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.

Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position

received
Position
35.2162° N, 139.7697° E
Area
North Pacific Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
12.1 kn
Course
182°
Heading
181°
35.2162° N, 139.7697° E
Open the full live map →

Last 30 days: 3 port calls (Yokohama and Chiba).

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-up

Identity & particulars

Name
Fuyo Maru No. 5
IMO numberWhat is an IMO number?
9060259
MMSIWhat is an MMSI?
431100123
Call signWhat is a call sign?
JG5298
Flag
Japan
Vessel type
Bulk carrier
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
3,568
Length overall
98 m
Beam
16 m
Year built
1994

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.

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.

DateEventSource
Left YokohamaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at YokohamaAIS-detectedVoydar port-call detector (AIS geofence)
Left YokohamaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at YokohamaAIS-detectedVoydar port-call detector (AIS geofence)
Left ChibaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ChibaAIS-detectedVoydar 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

PortArrivedDepartedTime in port
Yokohama JPYOKOct 2, 2026, 01:36 UTCOct 3, 2026, 05:02 UTC27 h 26 min
Yokohama JPYOKSep 29, 2026, 23:10 UTCSep 30, 2026, 03:29 UTC4 h 19 min
Chiba JPCHBSep 28, 2026, 06:21 UTCSep 29, 2026, 07:02 UTC24 h 41 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.

WhenWhat we observedConfidence
Oct 3, 2026, 00:34 UTC
Draught change

Reported draught went from 5.2 m to 6.2 m while in port at Yokohama. 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.

How these are computed →

Frequently asked questions

Where is Fuyo Maru No. 5 now?
Fuyo Maru No. 5 (Bulk carrier, Japan flag) was last seen on AIS on Oct 3, 2026, 05:59 UTC, under way at 12.1 kn, near Uraga (North Pacific Ocean). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was JP MKW OFF (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 05:21 UTC). This report does not confirm the ship’s current route.
What kind of ship is Fuyo Maru No. 5?
Fuyo Maru No. 5 is a bulk carrier sailing under the flag of Japan, built in 1994 by Tsuneishi Kure Dock. The vessel is 98 m long with a beam of 16 m and has a gross tonnage of 3,568.
What sanctions and inspection records does Voydar hold for Fuyo Maru No. 5?
Voydar has no matched sanctions record displayed for Fuyo Maru No. 5 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 Fuyo Maru No. 5. 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/9060259
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

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.

See plans