BIZTRAC BETA
Other captive investment companies

EIKVIN AS

Org. no. 988958980 Limited company (AS) Frogn Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 690,000
Operating profit NOK 685,000
Equity NOK 10.0m
Incorporated 2005
Share capital NOK 100,000

EIKVIN AS is registered as a limited company in Frogn, Akershus with organisation number 988958980. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets viksomheter selv, gjennom hel- eller deleide selskaper eller ved samarbeid med andre virksomheter, å forestå investeringsvirksomhet, utvikling og forvaltning av fast eiendom og annen virkosomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 690,000 in revenue and NOK 685,000 in operating profit.

Key figures · 2025

Revenue
NOK 690,000
Operating profit
NOK 685,000
Equity
NOK 10.0m
Est. value
NOK 7.2m

Financial health · 2025

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

Who owns EIKVIN AS?

HALVARD LAUGLO ØYE
EIKVIN AS
NOK 690,000 rev. · NOK 685,000 profit

EIKVIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EIKVIN AS own?

EIKVIN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EIKVIN AS

Who owns EIKVIN AS?

HALVARD LAUGLO ØYE is the largest registered owner, with 100.0%.

What is the revenue of EIKVIN AS?

EIKVIN AS had revenue of NOK 690,000 in 2025.

Who is the general manager of EIKVIN AS?

Marte Øye is registered as general manager of EIKVIN AS.

Where is EIKVIN AS based?

EIKVIN AS has its business address in Drøbak.

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.