Karina C
General cargo ship · Portugal · built 2010 · AIS Class A
In short
Karina C (General cargo ship, Portugal flag) was last seen on AIS on , under way at 7.9 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 last detected port call was at Gijon: arrived Sep 23, 2026, left Sep 25, 2026. ISM manager: Carisbrooke Shipping Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
- Vessel type
- General cargo ship
- Flag
- Portugal
- Year built
- 2010
- Gross tonnage
- 4,151
- Size (length × beam)
- 106 m × 16 m
- ISM manager
- Carisbrooke Shipping Ltd
Watch this ship
Karina C has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.
Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position
received- Position
- 40.949° N, 13.4617° E
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 7.9 kn
- Course
- 60°
- Heading
- 61°
Last 30 days: 1 port call (Gijon).
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-upIdentity & particulars
- Name
- Karina C
- IMO numberWhat is an IMO number?
- 9558000
- MMSIWhat is an MMSI?
- 255806311
- Call signWhat is a call sign?
- CQAY5
- Flag
- Portugal
- Vessel type
- General cargo ship
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 4,151
- Deadweight (DWT)
- Source: Wikidata, record Q83640568. Added to Voydar on September 23, 2026. Licence: CC0 1.0.6,750 t
- Length overall
- 106.1 m
- Beam
- 15.5 m
- Year built
- 2010
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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Oct 5, 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 GijonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at GijonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from New OrleansAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at New OrleansAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from HOUSTON SHIP CHANNEL, TX (HOUSTON, TX)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Port State Control inspection at Portsmouth, Virginia | USCG PSIX / CGMIX inspections | |
| Inspection at Jacksonville, Florida | USCG PSIX / CGMIX inspections | |
| Inspection at Jacksonville, Florida | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Francisco, California | USCG PSIX / CGMIX inspections |
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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred May 24, 2019merchant-vessel-100-gross-tons-or-overUK MAIB investigation reports (index)Seville, Spain
Crush incident on general cargo vessel Karina C with loss of 1 lifeReport published Nov 26, 2020
Location: Seville, Spain.
Source: UK MAIB investigation reports (index). Contains public sector information licensed under the Open Government Licence v3.0. Licence: Open Government Licence v3.0.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| May 9, 2013 | Vessel InspectionPSC | Portsmouth, Virginia | clean |
| Sep 9, 2011 | Vessel Inspection | Jacksonville, Florida | clean |
| Sep 8, 2011 | Vessel Operational Control | Jacksonville, Florida | clean |
| Sep 29, 2010 | Vessel InspectionPSC | San Francisco, California | clean |
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.
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 |
|---|---|---|---|---|
| 2025 | 2,998 t | 942 t | 146 days | 95 kg |
Technical efficiency: EEXI (11.32 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 |
|---|---|---|---|
| Gijon ESGIJ | Sep 23, 2026, 06:20 UTC | Sep 25, 2026, 15:49 UTC | 2 d 9 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 |
|---|---|---|---|---|
| New Orleans USMSY | Departure | Jun 19, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Jun 17, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | May 23, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | May 21, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tampa USTPA | Arrival | May 17, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Tampa USTPA | Departure | May 17, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Departure | May 9, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER (SOUTHERN BRANCH) VA | Arrival | May 6, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Departure | Sep 21, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| HOUSTON SHIP CHANNEL, TX (HOUSTON, TX) | Arrival | Sep 21, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Departure | Sep 16, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Sep 16, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: September 28, 2010.
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, 23:30 UTC | Draught change Reported draught went from 4.6 m to 6.4 m after leaving Gijon. Voydar infers the ship probably loaded 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 Karina C now?
- Karina C (General cargo ship, Portugal flag) was last seen on AIS on Oct 4, 2026, 02:20 UTC, under way at 7.9 kn, in the Mediterranean Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- What kind of ship is Karina C?
- Karina C is a general cargo ship sailing under the flag of Portugal, built in 2010 by Jiangsu Yangzijiang Shipbuilding. The vessel is 106.1 m long with a beam of 15.5 m and has a gross tonnage of 4,151.
- Who is recorded as the owner or manager of Karina C?
- Carisbrooke Shipping Ltd is recorded as ISM manager for Karina C (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Karina C?
- Voydar has no matched sanctions record displayed for Karina 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. Karina C has 4 recorded Port State Control inspections. 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/9558000Using 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.