BIZTRAC BETA
Supply and other sea transport offshore services

ØSTENSJØ DRIFT AS

Org. no. 996144011 Limited company (AS) Haugesund Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 87.6m
Operating profit NOK 4.1m
Equity NOK 10.0m
Incorporated 2010
Employees 56
Share capital NOK 891,000

ØSTENSJØ DRIFT AS is registered as a limited company in Haugesund, Rogaland with organisation number 996144011. The business is classified under supply and other sea transport offshore services (NACE 50.203). The company was incorporated in 2010 and has 56 registered employees. Registered share capital is NOK 891,000, divided into 891 shares. The company's stated purpose is: “Drive skipsfartsvirksomhet, samt hva hermed står i forbindelse, herunder å delta i andre foretak som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 87.6m in revenue and NOK 4.1m in operating profit.

Key figures · 2024

Revenue
NOK 87.6m
Operating profit
NOK 4.1m
Equity
NOK 10.0m
Est. value
NOK 18.3m

Financial health · 2024

Liquidity
1.42
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
29.7%
Good
Equity as a share of total capital

Who owns ØSTENSJØ DRIFT AS?

JOHANNES ØSTENSJØ DY AS
ØSTENSJØ DRIFT AS
NOK 87.6m rev. · NOK 4.1m profit

ØSTENSJØ DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØSTENSJØ DRIFT AS

Who owns ØSTENSJØ DRIFT AS?

JOHANNES ØSTENSJØ DY AS is the largest registered owner, with 100.0%.

What is the revenue of ØSTENSJØ DRIFT AS?

ØSTENSJØ DRIFT AS had revenue of NOK 87.6m in 2024.

Who is the general manager of ØSTENSJØ DRIFT AS?

Kristian Helland Vea is registered as general manager of ØSTENSJØ DRIFT AS.

Where is ØSTENSJØ DRIFT AS based?

ØSTENSJØ DRIFT AS has its business address in Haugesund.

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.