YUUSEIMARU NO3
Cargo ship · Japan · AIS Class A
In short
YUUSEIMARU NO3 (Cargo ship, Japan flag) was last seen on AIS on , moored, near Yokosuka (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 YOK XX NGI OFF; its reported draught is 4.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 18:34 UTC).
Current voyage: from Funabashi (departed Oct 1, 2026, 09:01 UTC) to >JP YOK XX NGI OFF
- Vessel type
- Cargo ship
- Flag
- Japan
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- Registered owner
- —
Watch this ship
YUUSEIMARU NO3 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.296° N, 139.7341° E
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 11 kn
- Course
- 146°
- Heading
- 143°
Last 30 days: 3 port calls (Funabashi and Yokohama).
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-upIdentity & particulars
- Name
- YUUSEIMARU NO3
- IMO numberWhat is an IMO number?
- —
- MMSIWhat is an MMSI?
- 431012202
- Call signWhat is a call sign?
- JD4435
- Flag
- Japan
- Vessel type
- Cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
JapanA 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 FunabashiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at FunabashiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left FunabashiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at FunabashiAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left YokohamaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at YokohamaAIS-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 |
|---|---|---|---|
| Funabashi JPFNB | Sep 30, 2026, 22:34 UTC | Oct 1, 2026, 09:01 UTC | 10 h 27 min |
| Funabashi JPFNB | Sep 27, 2026, 22:28 UTC | Sep 30, 2026, 08:31 UTC | 2 d 10 h |
| Yokohama JPYOK | Sep 26, 2026, 22:53 UTC | Sep 27, 2026, 02:59 UTC | 4 h 6 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 18, 2026, 18:40 UTC | AIS gap No AIS position received for 3 d 18 h while our receivers kept hearing other ships there (70 of 72 hours in coverage). Heard again 2 km away. Method seadar.behaviour.ais_gap v1 | High (89%) |
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 YUUSEIMARU NO3 now?
- YUUSEIMARU NO3 (Cargo ship, Japan flag) was last seen on AIS on Oct 1, 2026, 21:53 UTC, moored, near Yokosuka (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 YOK XX NGI OFF (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 18:34 UTC). This report does not confirm the ship’s current route.
- What kind of ship is YUUSEIMARU NO3?
- YUUSEIMARU NO3 is a cargo ship sailing under the flag of Japan.
- What sanctions and inspection records does Voydar hold for YUUSEIMARU NO3?
- Voydar has no matched sanctions record displayed for YUUSEIMARU NO3 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 YUUSEIMARU NO3. 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/mmsi-431012202Using 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.