Skip to content

MERCOSUL ITAJAI

Cargo ship · Brazil · built 2015 · AIS Class A

IMO9697002MMSI710027240Call signPPKQLast AIS position Oct 6, 2026, 13:23 UTC

In short

MERCOSUL ITAJAI (Cargo ship, Brazil flag) was last seen on AIS on , under way at 10 kn, in the South Atlantic Ocean. Its crew-entered AIS destination is ARZAE (Zarate), with an ETA of Oct 6, 2026, 01:00 UTC; its reported draught is 8.8 m (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:34 UTC).

Current voyage: from Santos (departed Oct 3, 2026, 23:25 UTC) to ARZAE (Zarate)

Vessel type
Cargo ship
Flag
Brazil
Year built
2015
Gross tonnage
28,237
Size (length × beam)
195 m × 32 m
Registered owner
—

Watch this ship

Get an email when MERCOSUL ITAJAI reaches Zarate, and when it 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
34.2919° S, 58.5619° W
Area
South Atlantic Ocean
StatusWhat do AIS statuses mean?
Under way using engine
Speed
10 kn
Course
300°
Heading
298°
34.2919° S, 58.5619° W
Open the full live map →

Last 30 days: 2 port calls (Santos and Buenos Aires).

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
MERCOSUL ITAJAI
IMO numberWhat is an IMO number?
9697002
MMSIWhat is an MMSI?
710027240
Flag
Brazil
Vessel type
Cargo ship
AIS ship type
Cargo (hazardous cat. A)
Gross tonnageGross tonnage vs deadweight
28,237
Length overall
194.9 m
Beam
32.3 m
Year built
2015

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
Left SantosAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at SantosAIS-detectedVoydar port-call detector (AIS geofence)
Left Buenos AiresAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Buenos AiresAIS-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
Santos BRSSZOct 2, 2026, 20:34 UTCOct 3, 2026, 23:25 UTC26 h 50 min
Buenos Aires ARBUESep 25, 2026, 00:49 UTCOct 2, 2026, 20:34 UTC7 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.

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 3, 2026, 21:50 UTC
Draught change

Reported draught went from 8.1 m to 8.8 m while in port at Santos. Voydar infers the ship probably loaded cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)
Oct 2, 2026, 19:59 UTC
Draught change

Reported draught went from 9.5 m to 8.1 m while in port at Buenos Aires. Voydar infers the ship probably discharged cargo.

Method seadar.behaviour.draught_change v1

Medium (65%)

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 MERCOSUL ITAJAI now?
MERCOSUL ITAJAI (Cargo ship, Brazil flag) was last seen on AIS on Oct 6, 2026, 13:23 UTC, under way at 10 kn, in the South Atlantic Ocean. The crew-entered destination was ARZAE (voyage report via AISstream.io global terrestrial AIS, received Oct 6, 2026, 11:34 UTC). This report does not confirm the ship’s current route.
What kind of ship is MERCOSUL ITAJAI?
MERCOSUL ITAJAI is a cargo ship sailing under the flag of Brazil, built in 2015 by Guangzhou Wenchong Shipyard. The vessel is 194.9 m long with a beam of 32.3 m and has a gross tonnage of 28,237.
What sanctions and inspection records does Voydar hold for MERCOSUL ITAJAI?
Voydar has no matched sanctions record displayed for MERCOSUL ITAJAI 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 MERCOSUL ITAJAI. 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/9697002
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