Skip to content

JUNO PACIFIC

Cargo ship · Panama · built 2011 · AIS Class A

IMO9424118MMSI355530000Call sign3FQP2Last AIS position Sep 26, 2026, 05:35 UTC

In short

JUNO PACIFIC (Cargo ship, Panama flag) was last seen on AIS on , under way at 1.1 kn, near Jurong (Strait of Malacca). 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 SINGAPORE; its reported draught is 9 m (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 04:08 UTC).

Vessel type
Cargo ship
Flag
Panama
Year built
2011
Gross tonnage
19,801
Size (length × beam)
176 m × 29 m
Registered owner
—

Watch this ship

Get an email when JUNO PACIFIC 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 JUNO PACIFIC.

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
1.2988° N, 103.7253° E
Area
Strait of Malacca
StatusWhat do AIS statuses mean?
Under way using engine
Speed
1.1 kn
Course
327°
Heading
158°
1.2988° N, 103.7253° E
Open the full live map →

Voydar detected no port call in the last 30 days.

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

Identity & particulars

Name
JUNO PACIFIC
IMO numberWhat is an IMO number?
9424118
MMSIWhat is an MMSI?
355530000
Call signWhat is a call sign?
3FQP2
Flag
Panama
Vessel type
Cargo ship
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
19,801
Length overall
175.5 m
Beam
29.4 m
Year built
2011

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
Reported departure from PortlandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at VancouverAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from StocktonAuthority-reportedUSACE foreign traffic vessel entrances & clearances

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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Portland USPDXDepartureNov 27, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANArrivalNov 22, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Stockton USSCKDepartureNov 16, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Stockton USSCKArrivalNov 7, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGDepartureSep 9, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGArrivalAug 31, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGDepartureJun 29, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGArrivalJun 23, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGDepartureMay 10, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGArrivalMay 2, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Olympia USOLMDepartureMar 24, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Olympia USOLMArrivalMar 18, 2016(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: February 11, 2011.

Frequently asked questions

Where is JUNO PACIFIC now?
JUNO PACIFIC (Cargo ship, Panama flag) was last seen on AIS on Sep 26, 2026, 05:35 UTC, under way at 1.1 kn, near Jurong (Strait of Malacca). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was SINGAPORE (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 04:08 UTC). This report does not confirm the ship’s current route.
What kind of ship is JUNO PACIFIC?
JUNO PACIFIC is a cargo ship sailing under the flag of Panama, built in 2011 by Hakodate Dock. The vessel is 175.5 m long with a beam of 29.4 m and has a gross tonnage of 19,801.
What sanctions and inspection records does Voydar hold for JUNO PACIFIC?
Voydar has no matched sanctions record displayed for JUNO PACIFIC 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 JUNO PACIFIC. 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/9424118
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