Baltic Performer
Reefer ship · Bahamas · built 1992 · AIS Class A
In short
Baltic Performer (Reefer ship, Bahamas flag) was last seen on AIS on , under way at 16 kn, in the North 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 PACTB (Cristobal), with an ETA of Oct 7, 2026, 15:00 UTC; its reported draught is 6.6 m (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 15:31 UTC). ISM manager: OWH Shipmanagement GmbH (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Schiedam (departed Sep 25, 2026, 12:33 UTC) to PACTB (Cristobal)
- Vessel type
- Reefer ship
- Flag
- Bahamas
- Year built
- 1992
- Gross tonnage
- 10,381
- Size (length × beam)
- 150 m × 23 m
- ISM manager
- OWH Shipmanagement GmbH
Watch this ship
Get an email when Baltic Performer 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 Baltic Performer.
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
- 48.7329° N, 6.2689° W
- Area
- North Atlantic Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 16 kn
- Course
- 229°
- Heading
- 230°
Last 30 days: 1 port call (Schiedam).
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
- Baltic Performer
- IMO numberWhat is an IMO number?
- 9016674
- MMSIWhat is an MMSI?
- 311000972
- Call signWhat is a call sign?
- C6EQ6
- Flag
- Bahamas
- Vessel type
- Reefer ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 10,381
- Length overall
- 150 m
- Beam
- 22.8 m
- Year built
- 1992
BahamasA 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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
- 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 SchiedamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SchiedamAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from FERNANDINA HARBOR, FLAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at FERNANDINA HARBOR, FLAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIAAuthority-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.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 0 t | 0 t | 0 days | — |
| 2019 | 5,867 t | 1,875 t | 70 days | 232 kg |
| 2020 | 2,776 t | 883 t | 31 days | 224 kg |
| 2021 | 6,764 t | 2,158 t | 78 days | 222 kg |
| 2022 | 4,711 t | 1,508 t | 53 days | 235 kg |
| 2023 | 3,485 t | 1,116 t | 43 days | 205 kg |
| 2024 | 4,563 t | 1,461 t | 59 days | 217 kg |
| 2025 | 0 t | 0 t | 0 days | — |
Technical efficiency: EIV (25.61 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
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 |
|---|---|---|---|
| Schiedam NLSCI | Sep 23, 2026, 11:10 UTC | Sep 25, 2026, 12:33 UTC | 2 d 1 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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| FERNANDINA HARBOR, FL | Departure | Jan 3, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| FERNANDINA HARBOR, FL | Arrival | Jan 2, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIA | Departure | Dec 28, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| DELAWARE RIVER AT CAMDEN, NJ (INCLUDED IN DELAWARE RIVER, PHILADELPHIA | Arrival | Dec 27, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILG | Departure | Jan 3, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILG | Arrival | Jan 3, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILG | Departure | Dec 1, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Wilmington USILG | Arrival | Dec 1, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Apr 9, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Apr 7, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | Mar 12, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | Mar 11, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: March 26, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
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.
| When | What we observed | Confidence |
|---|---|---|
| Sep 25, 2026, 13:53 UTC | Draught change Reported draught went from 8.3 m to 6.6 m after leaving Schiedam. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
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.
Frequently asked questions
- Where is Baltic Performer now?
- Baltic Performer (Reefer ship, Bahamas flag) was last seen on AIS on Sep 26, 2026, 16:17 UTC, under way at 16 kn, in the North 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 PACTB (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 15:31 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Baltic Performer?
- Baltic Performer is a reefer ship sailing under the flag of Bahamas, built in 1992 by Shikoku Dockyard. The vessel is 150 m long with a beam of 22.8 m and has a gross tonnage of 10,381.
- Who is recorded as the owner or manager of Baltic Performer?
- OWH Shipmanagement GmbH is recorded as ISM manager for Baltic Performer (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 Baltic Performer?
- Voydar has no matched sanctions record displayed for Baltic Performer from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Baltic Performer. Missing records do not establish whether the ship has been detained.
Sister ships
Likely sister ships: built by Shikoku Dockyard, same type, gross tonnage within 2.5% and length within 1.5% of this ship's.
- Baltic PrinceIMO 8813594Reefer ship · built 1990 · 10,394 GT
- Baltic PatriotIMO 9038488Reefer ship · built 1992 · 10,402 GT
- IMO 9016662IMO 9016662Reefer ship · built 1992 · 10,381 GT
- Falcon BayIMO 9070137Reefer ship · built 1993 · 10,374 GT
- FegulusIMO 9055709Reefer ship · built 1993 · 10,374 GT
- Regal BayIMO 9053658Reefer ship · built 1993 · 10,375 GT
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9016674Using 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.