BIZTRAC BETA
COMPANY REGISTER PROFILE
814717402 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

HAVFRUEN INVEST AS

Org. no. 814717402 Limited company (AS) Vega Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 2.4m
Equity NOK 55.7m
Incorporated 2014
Share capital NOK 151,000

HAVFRUEN INVEST AS is registered as a limited company in Vega, Nordland with organisation number 814717402. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 151,000, divided into 1506 shares. The company's stated purpose is: “Eie aksjer i andre selskaper, m.v.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 2.4m in operating profit.

Former names: ARNTSEN INVEST AS

Key figures · 2025

Revenue
NOK 3.5m
▲ +93 %
Operating profit
NOK 2.4m
▲ +228 %
Equity
NOK 55.7m
▲ +6 %
Est. value
NOK 37.1m

Financial health · 2025

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

Who owns HAVFRUEN INVEST AS?

HAVFRUEN INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does HAVFRUEN INVEST AS own?

HAVFRUEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAVFRUEN INVEST AS

Who owns HAVFRUEN INVEST AS?

ARNLJOT ARNTSEN is the largest registered owner, with 26.7%.

What is the revenue of HAVFRUEN INVEST AS?

HAVFRUEN INVEST AS had revenue of NOK 3.5m in 2025.

Who is the general manager of HAVFRUEN INVEST AS?

Arnljot Arntsen is registered as general manager of HAVFRUEN INVEST AS.

Where is HAVFRUEN INVEST AS based?

HAVFRUEN INVEST AS has its business address in Vega.

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

Report a problem

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