BIZTRAC BETA
Patent brokering and marketing service activities

HORDALAND MARITIME MILJØSELSKAP AS

Org. no. 992764880 Limited company (AS) Bømlo Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −98,000
Equity NOK 204,000
Incorporated 2008
Share capital NOK 4.5m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−98k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HORDALAND MARITIME MILJØSELSKAP AS is registered as a limited company in Bømlo, Vestland with organisation number 992764880. The business is classified under patent brokering and marketing service activities (NACE 74.910). The company was incorporated in 2008. Registered share capital is NOK 4.5m, divided into 44832 shares. The company's stated purpose is: “Utviklingsarbeid, eie og utnytte patenter og andre rettigheter i forretningsmessig virksomhet, herunder delta i andre foretak med samme formål.”.

Key figures · 2024

Operating profit
NOK −98,000
Equity
NOK 204,000
Est. value
NOK 331,000

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns HORDALAND MARITIME MILJØSELSKAP AS?

EIDESVIK OFFSHORE ASA
HORDALAND MARITIME MILJØSELSKAP AS
· NOK −98,000 profit

HORDALAND MARITIME MILJØSELSKAP AS has 4 registered shareholders:

All shareholders and roles →

Group structure

HORDALAND MARITIME MILJØSELSKAP AS er morselskap for 18 datterselskaper:

Frequently asked questions about HORDALAND MARITIME MILJØSELSKAP AS

Who owns HORDALAND MARITIME MILJØSELSKAP AS?

EIDESVIK OFFSHORE ASA is the largest registered owner, with 91.1%.

Where is HORDALAND MARITIME MILJØSELSKAP AS based?

HORDALAND MARITIME MILJØSELSKAP AS has its business address in Bømlo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.