Skip to content
voydar.com

AS PETRONIA

Container ship · Portugal · built 2004 · AIS Class A

IMO9286786MMSI255806064Call signDATAHUBLast AIS position Nov 18, 2026, 14:41 UTC

In short

AS PETRONIA (Container ship, Portugal flag) was last seen on AIS on , under way at 17 kn, in the Mediterranean Sea. 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 LAST UPDATE TIME; its reported draught is 11.5 m (voyage report via AISstream.io global terrestrial AIS, received Nov 18, 2026, 14:20 UTC). ISM manager: AS PETRONIA OpCo B.V. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).

Current voyage: from Tanger Med (departed Nov 14, 2026, 22:14 UTC) to LAST UPDATE TIME

Data: AISHub contributors

Vessel type
Container ship
Year built
2004
Gross tonnage
26,833
Size (length × beam)
210 m × 30 m
Photo of AS PETRONIA
Photo: Niels Johannes · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position: 36.6517° N, 14.0617° E · Mediterranean Sea · See on the map

Watch this ship

AS PETRONIA has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.

What you would have been told

Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.

Detected from AIS, as of Nov 19, 2026, 20:24 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for AS PETRONIA reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans

Get alerts on your phone: the Voydar app

Last reported position

received
Position
36.6517° N, 14.0617° E
Area
Mediterranean Sea
Status
Under way using engineWhat do AIS statuses mean?
Speed
17 kn
Course
110°
Heading
112°
Compass: course over ground 110°, heading 112°
NArrow: course. Hull: heading. As broadcast on AIS.
36.6517° N, 14.0617° E. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
36.6517° N, 14.0617° E
See it live in 3D →

Last 30 days: 6 port calls (Tanger Med, Algeciras, Barcelona, Valencia, Haifa, and Mersin).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Data: AISHub contributors

Pro shows AS PETRONIA's track before the last 30 days. Voydar has recorded its port calls since September 12, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Length overall 210 mone tick every 25 m

Beam 30 mPlan outline, to scale

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
AS PETRONIA
IMO numberWhat is an IMO number?
9286786
MMSIWhat is an MMSI?
255806064
Call signWhat is a call sign?
DATAHUB
AIS ship type
Cargo (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
26,833
Length overall
210 m
Beam
30 m
Year built
2004

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.

Operator
Ahrenkiel-Gruppe(not linked to a company record)
Source: Wikidata · reported · medium confidence · retrieved Sep 23, 2026
Q402705(not linked to a company record)
Source: Wikidata · reported · medium confidence · retrieved Jun 8, 2026
ISM manager
Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · high confidence · retrieved Nov 16, 2026
Builder
Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026

Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →

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
Call sign changed from CQIT6 to DATAHUBAIS, seen by Voydar
Left Tanger MedAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Tanger MedAIS-detectedVoydar port-call detector (AIS geofence)
Left AlgecirasAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at AlgecirasAIS-detectedVoydar port-call detector (AIS geofence)
Left BarcelonaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BarcelonaAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from PhiladelphiaAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at PhiladelphiaAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from SavannahAuthority-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.

Emissions & fuel consumption

Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.

CO₂ emitted per reporting year, tonnes (EU MRV, as reported and verified). The table below has every figure.
YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
201816,767 t5,357 t111 days479 kg
201933,883 t10,873 t196 days459 kg
202036,140 t11,578 t258 days392 kg
202132,082 t10,274 t207 days429 kg
202225,912 t8,288 t155 days455 kg
202319,232 t6,346 t137 days423 kg
202420,501 t6,556 t134 days429 kg
202513,577 t4,350 t127 days341 kg

Technical efficiency: EEXI (17.07 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

Compared with ships of its type

Where this ship’s reported CO₂ intensity for 2025 sits among the ships EU MRV lists as “Container ship”. Lower is less CO₂.

CO₂ per tonne of cargo carried one nautical mile20.52 g per tonne-nautical mile
Lowest reportedHighest reported

61% of the 2,233 ships in this group reported a lower figure.

Group: lower quartile 9.85 · median 16.45 · upper quartile 29.35

CO₂ per nautical mile sailed340.8 kg per nautical mile
Lowest reportedHighest reported

29% of the 2,256 ships in this group reported a lower figure.

Group: lower quartile 313.5 · median 541.9 · upper quartile 768.9

Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated

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

Time in port over the last 69 days, drawn by Voydar from the AIS-detected calls listed below. Each bar runs from arrival to departure; gaps are time away from a detected port or without reception.
PortArrivedDepartedTime in port
Tanger Med MAPTMNov 14, 2026, 05:00 UTCNov 14, 2026, 22:14 UTC17 h 13 min
Algeciras ESALGNov 12, 2026, 06:08 UTCNov 13, 2026, 06:32 UTC24 h 24 min
Barcelona ESBCNNov 7, 2026, 21:20 UTCNov 8, 2026, 11:39 UTC14 h 19 min
Valencia ESVLCNov 6, 2026, 16:46 UTCNov 7, 2026, 11:21 UTC18 h 35 min
Haifa ILHFAOct 27, 2026, 18:46 UTCOct 28, 2026, 14:02 UTC19 h 16 min
Mersin TRMEROct 25, 2026, 03:59 UTCOct 26, 2026, 13:01 UTC33 h 2 min
Tanger Med MAPTMOct 19, 2026, 17:44 UTCOct 20, 2026, 00:14 UTC6 h 30 min
Algeciras ESALGOct 16, 2026, 22:47 UTCOct 18, 2026, 00:33 UTC25 h 46 min
Haifa ILHFASep 28, 2026, 11:53 UTCSep 28, 2026, 13:05 UTC1 h 13 min
Haifa ILHFASep 28, 2026, 01:50 UTCSep 28, 2026, 11:06 UTC9 h 16 min
Mersin TRMERSep 18, 2026, 13:33 UTCSep 27, 2026, 07:22 UTC8 d 17 h
Tanger Med MAPTMSep 12, 2026, 15:36 UTCSep 18, 2026, 10:36 UTC5 d 19 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
Philadelphia USPHLDepartureJul 19, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Philadelphia USPHLArrivalJul 18, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVDepartureJul 15, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVArrivalJul 15, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVDepartureMay 18, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVArrivalMay 18, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCDepartureMay 16, 2014(date only)—USACE foreign traffic vessel entrances & clearances
New York USNYCArrivalMay 16, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Philadelphia USPHLDepartureApr 24, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Philadelphia USPHLArrivalApr 24, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVDepartureApr 22, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Savannah USSAVArrivalApr 22, 2014(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: October 2, 2005.

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 28, 2026, 14:24 UTC
Draught change

Reported draught went from 11 m to 10.1 m after leaving Haifa. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (55%)
Oct 8, 2026, 10:16 UTC
Two positions

This MMSI was reported in two places 1,165 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 8, 2026, 10:01 UTC
Two positions

This MMSI was reported in two places 1,163 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 8, 2026, 09:46 UTC
Two positions

This MMSI was reported in two places 1,163 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 8, 2026, 09:33 UTC
Two positions

This MMSI was reported in two places 1,162 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 22:31 UTC
Two positions

This MMSI was reported in two places 1,166 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 21:01 UTC
Two positions

This MMSI was reported in two places 1,157 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 20:22 UTC
Two positions

This MMSI was reported in two places 1,139 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 20:01 UTC
Two positions

This MMSI was reported in two places 1,134 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 19:34 UTC
Two positions

This MMSI was reported in two places 1,127 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 18:47 UTC
Two positions

This MMSI was reported in two places 1,128 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 18:16 UTC
Two positions

This MMSI was reported in two places 1,129 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 18:04 UTC
Two positions

This MMSI was reported in two places 1,129 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 16:33 UTC
Two positions

This MMSI was reported in two places 1,131 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 15:48 UTC
Two positions

This MMSI was reported in two places 1,132 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 15:02 UTC
Two positions

This MMSI was reported in two places 1,134 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 14:32 UTC
Two positions

This MMSI was reported in two places 1,135 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 13:05 UTC
Two positions

This MMSI was reported in two places 1,136 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 12:50 UTC
Two positions

This MMSI was reported in two places 1,136 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 7, 2026, 12:03 UTC
Two positions

This MMSI was reported in two places 1,136 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)

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

What kind of ship is AS PETRONIA?
AS PETRONIA is a container ship sailing under the flag of Portugal, built in 2004 by HD Hyundai Heavy Industries. The vessel is 210 m long with a beam of 30 m and has a gross tonnage of 26,833.
Who is recorded as the owner or manager of AS PETRONIA?
AS PETRONIA OpCo B.V. is recorded as ISM manager for AS PETRONIA (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for AS PETRONIA?
Voydar has no matched sanctions record displayed for AS PETRONIA 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 AS PETRONIA. Missing records do not establish whether the ship has been detained.

Full Vessel Report

A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.

See a sample report (PDF)

Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.

Every fact on this page stays free.

Know this ship?

Help other readers. Member posts are shown as member content, never as sourced data.

  • Date, place and an optional note
  • Members who know her can answer
  • Suggest a correctionChecked against sources before anything changes

More Container ships

Other container ships with full Voydar profiles. A different set each day. All container ships

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/9286786
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite this page

AS PETRONIA. Voydar (voydar.com). https://www.voydar.com/vessel/9286786-as-petronia. Retrieved November 19, 2026.

Each fact above names its own source and date. Cite that primary source too when you rely on a fact.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.

See plans

Sources and attribution

  • Data: AISHub contributors (AISHub Terms of Use (2026-10-08))
  • Wikidata (CC0 1.0)

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9286786-as-petronia

Generated from voydar.com on Nov 19, 2026, 20:24 UTC