BIZTRAC BETA
Freight ocean transport

ODFJELL INSURANCE & PROPERTIES AS

Org. no. 911037092 Limited company (AS) Bergen Incorporated 1981 Active
Ownership graph ↗
Operating profit NOK −192,000
Equity NOK 192.3m
Incorporated 1981
Share capital NOK 6.0m

Signals

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

ODFJELL INSURANCE & PROPERTIES AS is registered as a limited company in Bergen, Vestland with organisation number 911037092. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 1981. Registered share capital is NOK 6.0m, divided into 12000 shares. The company's stated purpose is: “Som agenter og meklere å drive assuransevirksomhet, agentur, kjøp og salg av aksjer samt eiendomsbesittelse og hva dermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −192,000
Equity
NOK 192.3m
Est. value
NOK 147.7m

Financial health · 2024

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

Who owns ODFJELL INSURANCE & PROPERTIES AS?

ODFJELL SE
ODFJELL INSURANCE & PROPERTIES AS
· NOK −192,000 profit

ODFJELL INSURANCE & PROPERTIES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ODFJELL INSURANCE & PROPERTIES AS

Who owns ODFJELL INSURANCE & PROPERTIES AS?

ODFJELL SE is the largest registered owner, with 100.0%.

Who is the general manager of ODFJELL INSURANCE & PROPERTIES AS?

Terje Iversen is registered as general manager of ODFJELL INSURANCE & PROPERTIES AS.

Where is ODFJELL INSURANCE & PROPERTIES AS based?

ODFJELL INSURANCE & PROPERTIES AS has its business address in Bergen.

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.