Skip to content

SAPEUR

Tug · France · built 2003 · AIS Class A

IMO9270397MMSI228381900Call signFLYALast AIS position Oct 3, 2026, 21:44 UTC

In short

SAPEUR (Tug, France flag) was last seen on AIS on , moored, near Brest (Bay of Biscay). Its crew-entered AIS destination is FRENCH NAVY ORDER; its reported draught is 6.3 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 20:35 UTC). Its last detected port call was at Brest: arrived Jun 9, 2026, left Jun 15, 2026.

Vessel type
Tug
Flag
France
Year built
2003
Gross tonnage
2,725
Size (length × beam)
74 m
Registered owner
—

Watch this ship

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

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.

Photo of SAPEUR
Photo: Alan Jamieson from Aberdeen, Scotland · Licence: CC BY 2.0 · via Wikimedia Commons

Last reported position

received
Position
48.3699° N, 4.5134° W
Area
Bay of Biscay
Speed
0 kn
Course
18°
Heading
137°
48.3699° N, 4.5134° W
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
SAPEUR
IMO numberWhat is an IMO number?
9270397
MMSIWhat is an MMSI?
228381900
Flag
France
Vessel type
Tug
Gross tonnageGross tonnage vs deadweight
2,725
Length overall
74 m
Beam
—
Year built
2003

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
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 BrestAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BrestAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from New OrleansAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Port State Control inspection at New Orleans, LouisianaUSCG PSIX / CGMIX inspections
Reported arrival at New OrleansAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Former name: A.H.San FruttuosoWikidata

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.

Former and other names

Names attested for this ship other than its current name.

NameEvidenceDateSource
A.H.San FruttuosoFormer nameJan 1, 2003Wikidata

A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.

Source: Wikidata. Licence: CC0 1.0.

Safety & inspections

1
Inspections
not recorded
Detentions
0
Deficiencies
DateTypePortFindings
Jun 9, 2007Vessel InspectionPSCNew Orleans, Louisianaclean

Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.

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
Brest FRBESJun 9, 2026, 13:10 UTCJun 15, 2026, 05:42 UTC5 d 16 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.

Reported by authorities Authority-reported

PortRecordDate (UTC)BerthSource
New Orleans USMSYDepartureJun 11, 2007(date only)—USACE foreign traffic vessel entrances & clearances
New Orleans USMSYArrivalJun 8, 2007(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: June 8, 2007.

Frequently asked questions

Where is SAPEUR now?
SAPEUR (Tug, France flag) was last seen on AIS on Oct 3, 2026, 21:44 UTC, moored, near Brest (Bay of Biscay). The crew-entered destination was FRENCH NAVY ORDER (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 20:35 UTC). This report does not confirm the ship’s current route.
What kind of ship is SAPEUR?
SAPEUR is a tug sailing under the flag of France, built in 2003 by Eqva ASA. The vessel is 74 m long and has a gross tonnage of 2,725.
What sanctions and inspection records does Voydar hold for SAPEUR?
Voydar has no matched sanctions record displayed for SAPEUR 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. SAPEUR has 1 recorded Port State Control inspection. Detention and deficiency detail is not recorded for these inspections.

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/9270397
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