Juan C
Offshore supply vessel · Brazil · built 2013 · AIS Class A
In short
Juan C (Offshore supply vessel, Brazil flag) was last seen on AIS on , under way at 10.7 kn, in the South Atlantic Ocean. 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 ACU, with an ETA of Oct 3, 2026, 17:10 UTC; its reported draught is 4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 15:33 UTC). Its last detected port call was at Rio de Janeiro: arrived Oct 2, 2026, left Oct 3, 2026.
- Vessel type
- Offshore supply vessel
- Flag
- Brazil
- Year built
- 2013
- Gross tonnage
- 3,242
- Size (length × beam)
- 91 m × 18 m
- Registered owner
- —
Watch this ship
Get an email when Juan C 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 Juan C.
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
- 23.0767° S, 42.9619° W
- Area
- South Atlantic Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 10.7 kn
- Course
- 103°
- Heading
- 100°
Last 30 days: 3 port calls (Rio de Janeiro).
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-upIdentity & particulars
- Name
- Juan C
- IMO numberWhat is an IMO number?
- 9670365
- MMSIWhat is an MMSI?
- 710007311
- Call signWhat is a call sign?
- PU8714
- Flag
- Brazil
- AIS ship type
- Reserved
- Gross tonnageGross tonnage vs deadweight
- 3,242
- Deadweight (DWT)
- Source: Wikidata, record Q117110178. Added to Voydar on September 26, 2026. Licence: CC0 1.0.4,938 t
- Length overall
- 91.2 m
- Beam
- 18.3 m
- Year built
- 2013
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.
| Date | Event | Source |
|---|---|---|
| Left Rio de JaneiroAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Rio de JaneiroAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Rio de JaneiroAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Rio de JaneiroAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Rio de JaneiroAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Rio de JaneiroAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON)Authority-reported | USACE 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
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Rio de Janeiro BRRIO | Oct 2, 2026, 20:20 UTC | Oct 3, 2026, 16:45 UTC | 20 h 25 min |
| Rio de Janeiro BRRIO | Sep 30, 2026, 20:59 UTC | Oct 1, 2026, 14:30 UTC | 17 h 30 min |
| Rio de Janeiro BRRIO | Sep 29, 2026, 21:25 UTC | Sep 30, 2026, 14:41 UTC | 17 h 16 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Arrival | Dec 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Departure | Dec 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Arrival | Nov 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Departure | Nov 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Arrival | Oct 5, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Departure | Sep 19, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Arrival | Aug 23, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Departure | Aug 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Arrival | Aug 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Departure | Aug 17, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Arrival | Jul 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| GREATER LAFOURCHE PORT COMMISSION (PORT FOURCHON) | Departure | Jul 11, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 6, 2013.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is Juan C now?
- Juan C (Offshore supply vessel, Brazil flag) was last seen on AIS on Oct 3, 2026, 17:44 UTC, under way at 10.7 kn, in the South Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was ACU (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 15:33 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Juan C?
- Juan C is an offshore supply vessel sailing under the flag of Brazil, built in 2013 by North American Shipbuilding. The vessel is 91.2 m long with a beam of 18.3 m and has a gross tonnage of 3,242.
- What sanctions and inspection records does Voydar hold for Juan C?
- Voydar has no matched sanctions record displayed for Juan C 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 Juan C. 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/9670365Using 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.