Skip to content

Mikiona

Tug · United States · built 2006 · AIS Class A

IMO9415583MMSI367153070Call signWDD5057Last AIS position Oct 3, 2026, 13:23 UTC

In short

Mikiona (Tug, United States flag) was last seen on AIS on , under way at 8.8 kn, in the North Pacific Ocean. Its crew-entered AIS destination is LA 118, with an ETA of Oct 4, 2026, 21:00 UTC; its reported draught is 5.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 07:13 UTC).

Current voyage: from Tiburon (departed Sep 27, 2026, 04:15 UTC) to LA 118

Vessel type
Tug
Year built
2006
Gross tonnage
496
Size (length × beam)
37 m × 12 m
Registered owner
—

Watch this ship

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

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
36.7974° N, 122.7135° W
Area
North Pacific Ocean
StatusWhat do AIS statuses mean?
Power-driven vessel towing astern
Speed
8.8 kn
Course
161°
Heading
155°
36.7974° N, 122.7135° W
Open the full live map →

Last 30 days: 2 port calls (Tiburon and Richmond).

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
Mikiona
IMO numberWhat is an IMO number?
9415583
MMSIWhat is an MMSI?
367153070
Call signWhat is a call sign?
WDD5057
Vessel type
Tug
AIS ship type
Towing (long/wide)
Length overall
37 m
Beam
12 m
Year built
2006

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.

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 TiburonAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at TiburonAIS-detectedVoydar port-call detector (AIS geofence)
Left RichmondAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at RichmondAIS-detectedVoydar port-call detector (AIS geofence)
Reported arrival at Coos BayAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at PortlandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from RichmondAuthority-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.

Detected from AIS AIS-detected

PortArrivedDepartedTime in port
Tiburon USXTNSep 27, 2026, 02:28 UTCSep 27, 2026, 04:15 UTC1 h 47 min
Richmond USRCHSep 26, 2026, 15:46 UTCSep 27, 2026, 02:20 UTC10 h 34 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
Coos Bay USCOBArrivalAug 9, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Portland USPDXArrivalDec 20, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Richmond USRCHDepartureDec 9, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Richmond USRCHArrivalNov 24, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Richmond USRCHDepartureNov 13, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Port Angeles USCLMArrivalOct 30, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Richmond USRCHDepartureOct 23, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Richmond USRCHArrivalJan 29, 2008(date only)—USACE foreign traffic vessel entrances & clearances
Richmond USRCHDepartureJan 18, 2008(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: January 18, 2008.

Frequently asked questions

Where is Mikiona now?
Mikiona (Tug, United States flag) was last seen on AIS on Oct 3, 2026, 13:23 UTC, under way at 8.8 kn, in the North Pacific Ocean. The crew-entered destination was LA 118 (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 07:13 UTC). This report does not confirm the ship’s current route.
What kind of ship is Mikiona?
Mikiona is a tug sailing under the flag of United States, built in 2006. The vessel is 37 m long with a beam of 12 m and has a gross tonnage of 496.
What sanctions and inspection records does Voydar hold for Mikiona?
Voydar has no matched sanctions record displayed for Mikiona 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 Mikiona. 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/9415583
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