biztrac. BETA
COMPANY REGISTER PROFILE
917921830 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Marine fishing

NORDHAVET AS

Org. no. 917921830 Limited company (AS) Ibestad Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 90.1m
Operating profit NOK 27.1m
Equity NOK 167.8m
Incorporated 2016
Share capital NOK 1.1m

NORDHAVET AS is registered as a limited company in Ibestad, Troms with organisation number 917921830. The business is classified under marine fishing (NACE 03.110). The company was incorporated in 2016. Registered share capital is NOK 1.1m, divided into 200 shares. The company's stated purpose is: “Fiske og fangst, samt virksomhet i forbindelse med dette, herunder delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 90.1m in revenue and NOK 27.1m in operating profit.

Former names: EXTRA 158 AS, NORDTORSK AS

Key figures · 2025

Revenue
NOK 90.1m
▲ +37 %
Operating profit
NOK 27.1m
▲ +181 %
Equity
NOK 167.8m
▼ −16 %
Est. value
NOK 141.7m

Financial health · 2025

Liquidity
0.34
Not satisfactory
Current assets ÷ current liabilities
Profitability
7.9%
Satisfactory
Return on total assets
Solidity
42.4%
Very good
Equity as a share of total capital

Who owns NORDHAVET AS?

NORDHAVET AS
NOK 90.1m rev. · NOK 27.1m profit

NORDHAVET AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NORDHAVET AS own?

NORDHAVET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NORDHAVET AS

Who owns NORDHAVET AS?

ARVESEN AS is the largest registered owner, with 100.0%.

What is the revenue of NORDHAVET AS?

NORDHAVET AS had revenue of NOK 90.1m in 2025.

Who is the general manager of NORDHAVET AS?

Børge Arvesen is registered as general manager of NORDHAVET AS.

Where is NORDHAVET AS based?

NORDHAVET AS has its business address in Engenes.

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

Report a problem

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