Skip to content
voydar.com

INCE BOSPHORUS

Bulk carrier · Singapore · built 2006 · AIS Class A

IMO9354844MMSI563174500Call sign9V8523Last AIS position Nov 6, 2026, 05:21 UTC

In short

INCE BOSPHORUS (Bulk carrier, Singapore flag) was last seen on AIS on , under way at 11.1 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 Ust'-Luga: arrived Oct 20, 2026, left Oct 21, 2026. ISM manager: INCE DENIZCILIK VE TICARET A.S. (source: EU MRV (THETIS-MRV) emissions, reporting year 2024).

Data: AISHub contributors

Vessel type
Bulk carrier
Year built
2006
Gross tonnage
43,205
Size (length × beam)
229 m × 32 m

Last reported position: 36.0374° N, 15.0702° E · Mediterranean Sea · See on the map

Watch this ship

INCE BOSPHORUS has not been received for a while. Follow it for an email update when Voydar receives a new position, and for arrival and departure alerts.

What you would have been told

Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.

Detected from AIS, as of Nov 19, 2026, 01:20 UTC.

Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for INCE BOSPHORUS reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans

Get alerts on your phone: Voydar for iPhone

Last reported position

received
Position
36.0374° N, 15.0702° E
Area
Mediterranean Sea
Status
Constrained by her draughtWhat do AIS statuses mean?
Speed
11.1 kn
Course
114°
Heading
111°
Compass: course over ground 114°, heading 111°
NArrow: course. Hull: heading. As broadcast on AIS.
36.0374° N, 15.0702° E. Reference map only, not for navigation.
Locator map: Natural Earth (public domain)
36.0374° N, 15.0702° E
See it live in 3D →

Last 30 days: 1 port call (Ust'-Luga).

Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.

Data: AISHub contributors

A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)Free forever. No card. Follow a ship and Plus is free for 14 days.

Try the live demo, no sign-up

Identity & particulars

Length overall 228.9 mone tick every 25 m

Beam 32.3 mPlan outline, to scale

Drawn by Voydar from the recorded type, length and beam. The side view is a drawing of the ship type, not of this ship; the length rule and the plan outline's proportions are to scale, the hull shape is not surveyed.
Name
INCE BOSPHORUS
IMO numberWhat is an IMO number?
9354844
MMSIWhat is an MMSI?
563174500
Call signWhat is a call sign?
9V8523
Gross tonnageGross tonnage vs deadweight
43,205
Length overall
228.9 m
Beam
32.3 m
Year built
2006

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 2024 · reported · high confidence · retrieved Nov 16, 2026
Builder
Source: Wikidata · reported · high confidence · retrieved Nov 15, 2026

Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →

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 Ust'-LugaAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Ust'-LugaAIS-detectedVoydar port-call detector (AIS geofence)
Call sign changed from 9V8523 to DATAHUBAIS, seen by Voydar
Reported departure from Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported arrival at Hong KongAuthority-reportedHong Kong vessel arrivals & departures (incl. VTMS daily reports)
Reported departure from PORT OF SOUTH LOUISIANA (LA)Authority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at PORT OF SOUTH LOUISIANA (LA)Authority-reportedUSACE 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.

CO₂ emitted per reporting year, tonnes (EU MRV, as reported and verified). The table below has every figure.
YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20187,956 t2,536 t111 days291 kg
20194,372 t1,396 t59 days325 kg
2024944 t303 t18 days246 kg

Technical efficiency: EEXI (3.48 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.

Compared with ships of its type

Where this ship’s reported CO₂ intensity for 2024 sits among the ships EU MRV lists as “Bulk carrier”. Lower is less CO₂.

CO₂ per nautical mile sailed246 kg per nautical mile
Lowest reportedHighest reported

39% of the 3,825 ships in this group reported a lower figure.

Group: lower quartile 223 · median 263.7 · upper quartile 307

Calculated by Voydar from the figures ships report under EU MRV. This is not a rating and not the IMO Carbon Intensity Indicator (CII). EU MRV covers ships over 5,000 gross tonnage on voyages to, from and within the EU/EEA, so the group is those ships, not the world fleet. How this is calculated

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
Ust'-Luga RUULUOct 20, 2026, 10:03 UTCOct 21, 2026, 05:40 UTC19 h 37 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

PortRecordDate (UTC)BerthSource
Hong Kong HKHKGArrivalNov 27, 2021, 15:11 UTCPTHong Kong vessel arrivals & departures (incl. VTMS daily reports)
PORT OF SOUTH LOUISIANA (LA)DepartureAug 1, 2015(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalJul 13, 2015(date only)—USACE foreign traffic vessel entrances & clearances
MATAGORDA SHIP CHANNEL, TX (PORT LAVACA/POINT COMFORT, TX)DepartureJul 8, 2015(date only)—USACE foreign traffic vessel entrances & clearances
MATAGORDA SHIP CHANNEL, TX (PORT LAVACA/POINT COMFORT, TX)ArrivalJul 4, 2015(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)DepartureNov 21, 2014(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF PLAQUEMINES, LAArrivalNov 16, 2014(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF KALAMA, WADepartureJan 27, 2014(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF KALAMA, WAArrivalJan 24, 2014(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEADepartureNov 22, 2013(date only)—USACE foreign traffic vessel entrances & clearances
Seattle USSEAArrivalNov 13, 2013(date only)—USACE foreign traffic vessel entrances & clearances
PORT OF SOUTH LOUISIANA (LA)ArrivalApr 19, 2013(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: May 26, 2006.

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 6, 2026, 22:31 UTC
Two positions

This MMSI was reported in two places 2,163 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 21:20 UTC
Two positions

This MMSI was reported in two places 2,163 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 21:01 UTC
Two positions

This MMSI was reported in two places 2,163 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 20:48 UTC
Two positions

This MMSI was reported in two places 2,163 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 20:17 UTC
Two positions

This MMSI was reported in two places 2,163 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 20:03 UTC
Two positions

This MMSI was reported in two places 2,163 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 19:31 UTC
Two positions

This MMSI was reported in two places 2,160 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 19:16 UTC
Two positions

This MMSI was reported in two places 2,159 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 18:48 UTC
Two positions

This MMSI was reported in two places 2,157 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 16:31 UTC
Two positions

This MMSI was reported in two places 2,145 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 16:17 UTC
Two positions

This MMSI was reported in two places 2,145 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 16:04 UTC
Two positions

This MMSI was reported in two places 2,144 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 15:31 UTC
Two positions

This MMSI was reported in two places 2,142 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 14:03 UTC
Two positions

This MMSI was reported in two places 2,137 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 13:48 UTC
Two positions

This MMSI was reported in two places 2,136 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 13:32 UTC
Two positions

This MMSI was reported in two places 2,135 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 13:02 UTC
Two positions

This MMSI was reported in two places 2,133 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 12:47 UTC
Two positions

This MMSI was reported in two places 2,132 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 12:17 UTC
Two positions

This MMSI was reported in two places 2,129 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)
Oct 6, 2026, 11:50 UTC
Two positions

This MMSI was reported in two places 2,127 km apart at the same time: two transmitters may share the number, or the positions were disturbed.

Method seadar.behaviour.mmsi_conflict v1

Medium (70%)

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

What kind of ship is INCE BOSPHORUS?
INCE BOSPHORUS is a bulk carrier sailing under the flag of Singapore, built in 2006 by Tsuneishi Shipbuilding. The vessel is 228.9 m long with a beam of 32.3 m and has a gross tonnage of 43,205.
Who is recorded as the owner or manager of INCE BOSPHORUS?
INCE DENIZCILIK VE TICARET A.S. is recorded as ISM manager for INCE BOSPHORUS (source: EU MRV (THETIS-MRV) emissions; reporting year 2024). This source record does not independently confirm today’s ownership or management.
What sanctions and inspection records does Voydar hold for INCE BOSPHORUS?
Voydar has no matched sanctions record displayed for INCE BOSPHORUS 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 INCE BOSPHORUS. Missing records do not establish whether the ship has been detained.

Full Vessel Report

A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.

See a sample report (PDF)

Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.

Every fact on this page stays free.

Know this ship?

Help other readers. Member posts are shown as member content, never as sourced data.

  • Date, place and an optional note
  • Members who know her can answer
  • Suggest a correctionChecked against sources before anything changes

More Bulk carriers

Other bulk carriers with full Voydar profiles. A different set each day. All bulk carriers

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/9354844
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Cite this page

INCE BOSPHORUS. Voydar (voydar.com). https://www.voydar.com/vessel/9354844-ince-bosphorus. Retrieved November 19, 2026.

Each fact above names its own source and date. Cite that primary source too when you rely on a fact.

Using this data in code?

Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.

See plans

Sources and attribution

  • Data: AISHub contributors (AISHub Terms of Use (2026-10-08))
  • Wikidata (CC0 1.0)

Each fact above names its source and the date it was retrieved. Each source's licence applies to its data.

Compiled by Voydar from the sources named on this page.

Page: https://www.voydar.com/vessel/9354844-ince-bosphorus

Generated from voydar.com on Nov 19, 2026, 01:20 UTC