BALSARE 1
General cargo ship · Malta · AIS Class A
In short
BALSARE 1 (General cargo ship, Malta flag) was last seen on AIS on , under way at 5.1 kn, in the Bay of Biscay. 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 Kiel Canal: arrived Sep 11, 2026, left Sep 19, 2026. ISM manager: SARFO DENIZCILIK VE TICARET A.S. (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
- Vessel type
- General cargo ship
- Flag
- Malta
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- —
- ISM manager
- SARFO DENIZCILIK VE TICARET A.S.
Watch this ship
BALSARE 1 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
- 46.7918° N, 6.6839° W
- Area
- Bay of Biscay
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 5.1 kn
- Course
- 187°
- Heading
- 185°
Last 30 days: 1 port call (Kiel Canal).
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
- BALSARE 1
- IMO numberWhat is an IMO number?
- 9963994
- MMSIWhat is an MMSI?
- 249778000
- Call signWhat is a call sign?
- 9HA6381
- Flag
- Malta
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- —
- Beam
- —
- Year built
- —
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
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 Kiel CanalAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Kiel CanalAIS-detected | Voydar 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.
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 | 478 t | 149 t | 31 days | 73 kg |
Technical efficiency: EEDI (13.1 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 |
|---|---|---|---|
| Kiel Canal DECKL | Sep 11, 2026, 09:08 UTC | Sep 19, 2026, 05:15 UTC | 7 d 20 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.
| When | What we observed | Confidence |
|---|---|---|
| Sep 20, 2026, 20:36 UTC | AIS gap No AIS position received for 43 h 26 min while our receivers kept hearing other ships there (42 of 43 hours in coverage). Heard again 3 km away. Method seadar.behaviour.ais_gap v1 | High (89%) |
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 BALSARE 1 now?
- BALSARE 1 (General cargo ship, Malta flag) was last seen on AIS on Oct 3, 2026, 11:53 UTC, under way at 5.1 kn, in the Bay of Biscay. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- What kind of ship is BALSARE 1?
- BALSARE 1 is a general cargo ship sailing under the flag of Malta.
- Who is recorded as the owner or manager of BALSARE 1?
- SARFO DENIZCILIK VE TICARET A.S. is recorded as ISM manager for BALSARE 1 (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 BALSARE 1?
- Voydar has no matched sanctions record displayed for BALSARE 1 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 BALSARE 1. 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/9963994Using 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.