Bulk carrier · India flag · built 2009
MAHA ANOSHA
IMO 9425473 3 reporting years
- CO₂ reported 2023
- 8,830 t
- Fuel burned
- 2,834 t
- Distance
- 17,029 nm
- Time at sea
- 1,506 h
- Emitted at berth
- 1% of total
- Share of year under way
- 17%
- Gross tonnage
- 88,397
Vessel particulars
- IMO number
- 9425473
- Ship type
- Bulk carrier
- Gross tonnage
- 88,397
- Length overall
- 287.5 m
- Beam
- 45.0 m
- Year built
- 2009
- Flag state
- India
- Port of registry
- Mumbai
- Technical efficiency (design)
- EIV (3.21 gCO₂/t·nm)
- Verifier
- Indian Register of Shipping, India
- Accreditation
- V 107
- Compliance document issued
- 2024-04-30
- Compliance document expires
- 2025-06-30
Flag state is derived from rapportert, not reported directly, and reflects the registry at the time of reporting.
Efficiency against its own type2023
Position 137 of 3,262 qualifying bulk carriers by EEOI, at the 4th percentile. The dashed line is the type median, 8.0; this vessel reported 3.7.
EEOI divides emissions by transport work, which for this vessel and year was 2,367,217,158 tonn-nmover 17,029 nautical miles.
Reported CO₂ by year
Between 2018 and 2023 reported CO₂ fell by 17.3%. No return is recorded for 2020, 2021, 2022, so the series has gaps.
From 2019 to 2023, emissions fell 31.9% while distance sailed fell 37.1%and CO₂ per nautical mile rose 8.3%.That points mainly to how much the vessel sailed, rather than the other.
Annual returns2018–2023
| Year | CO₂ (t) | Fuel (t) | Distance (nm) | At sea (h) | At berth (t) | kg CO₂/nm | EEOI | Percentile |
|---|---|---|---|---|---|---|---|---|
| 2023 | 8,830 | 2,834 | 17,029 | 1,506 | 78 | 518.5 | 3.7 | 4 |
| 2019 | 12,970 | 4,157 | 27,082 | 2,238 | 171 | 478.9 | 4.3 | 7 |
| 2018 | 10,676 | 3,416 | 21,355 | 1,865 | 235 | 499.9 | 4.8 | 10 |
Where the 2023 emissions occurred
Sources and how to read this
- Emissions: EU MRV publication (THETIS-MRV), reporting years 2018–2023, published by the European Commission.
- Vessel particulars: Wikidata (CC0).
What this page is built on
- Reporting years
- 3
- Ranked by efficiency
- yes
- Vessel particulars
- 5 of 5
- Movement data
- not observed
- Name history
- none recorded
- Photograph
- none licensed
- Sanctions record
- none
- Inspection record
- none in US waters
Caveats that apply to every vessel page
EEOI above 100,000 is withheld. Those values come from returns where reported transport work is near zero, which makes the ratio meaningless rather than extreme. Median across the dataset is around 12.
Emission categories overlap. In the MRV return, emissions at berth are also counted inside the voyage legs, so the categories do not sum to the total. They are shown side by side rather than stacked for that reason.
Distance is derived, intensity is reported. The MRV return publishes CO₂ per nautical mile but not the distance itself, which is null in all 106,564 rows of the source. The distance column is therefore filled from the ranking step, which reconstructs it, and is blank for years where a vessel was not ranked. That is why a row can show an intensity without a distance.
Percentile is within type and year. It is the vessel's position among qualifying ships of the same type that year, where lower is more efficient. A blank means the vessel did not qualify for ranking that year.
Sister ships share a builder, a type and a build year within two years of this vessel. That holds hull and machinery roughly constant and leaves operation as the variable, which is why they are listed before nearest-by-tonnage.
Methane and nitrous oxide start in 2024. They were not reported before that period, so earlier years cannot be compared against them.
Technical efficiency is a design figure fixed at construction. A vessel can hold a good index and still emit heavily by sailing fast, waiting at anchor or carrying little.
Inspection records cover United States waters only. An empty record is not evidence of a clean history elsewhere.
Empty means unreported, never zero. Nothing here is modelled, estimated or interpolated. See the methodology.
Something wrong on this page? See corrections. We do not hold the source registers and cannot amend them, but we will fix anything we have got wrong in reproducing them.