Skip to content

SI

Sailing vessel · United States · AIS Class B

IMO9034365MMSI338227743Call signFGYPLast AIS position Oct 6, 2026, 15:05 UTC

In short

SI (Sailing vessel, United States flag) was last seen on AIS on , not moving, near Alameda (North Pacific Ocean). Its last detected port call was at Arcachon: arrived Oct 4, 2026, left Oct 5, 2026.

Vessel type
Sailing vessel
Year built
—
Gross tonnage
—
Size (length × beam)
15 m × 5 m
Registered owner
—

Watch this ship

Get an email when SI arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

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

Last reported position

received
Position
37.7889° N, 122.2743° W
Area
North Pacific Ocean
Speed
0 kn
Course
—
Heading
—
37.7889° N, 122.2743° W
Open the full live map →

Last 30 days: 3 port calls (Arcachon).

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
SI
IMO numberWhat is an IMO number?
9034365
MMSIWhat is an MMSI?
338227743
Vessel type
Sailing vessel
AIS ship type
Sailing
Length overall
15 m
Beam
5 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.

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 ArcachonAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ArcachonAIS-detectedVoydar port-call detector (AIS geofence)
Left ArcachonAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ArcachonAIS-detectedVoydar port-call detector (AIS geofence)
Left ArcachonAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at ArcachonAIS-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
Arcachon FRARCOct 4, 2026, 08:46 UTCOct 5, 2026, 01:14 UTC16 h 28 min
Arcachon FRARCSep 27, 2026, 03:58 UTCSep 27, 2026, 18:19 UTC14 h 21 min
Arcachon FRARCSep 11, 2026, 03:04 UTCSep 27, 2026, 03:58 UTC16 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.

WhenWhat we observedConfidence
Oct 6, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,108 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 5, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,114 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 4, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,135 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 3, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,111 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 2, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,119 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Oct 1, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,119 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 30, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,135 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 29, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,116 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 28, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,122 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 27, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,112 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 26, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,127 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 25, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,106 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)
Sep 24, 2026, 00:00 UTC
IMO used twice

IMO 9034365 was broadcast by two ships (MMSI 227442000 and 338227743) 9,090 km apart at the same time. One of them may be using the wrong IMO number.

Method seadar.behaviour.imo_conflict v1

High (80%)

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 SI now?
SI (Sailing vessel, United States flag) was last seen on AIS on Oct 6, 2026, 15:05 UTC, not moving, near Alameda (North Pacific Ocean).
What kind of ship is SI?
SI is a sailing vessel sailing under the flag of United States. The vessel is 15 m long with a beam of 5 m.
What sanctions and inspection records does Voydar hold for SI?
Voydar has no matched sanctions record displayed for SI 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 SI. 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/9034365
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