BIZTRAC BETA
Other captive investment companies

LØKKE-INVEST AS

Org. no. 912418324 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 2.2m
Equity NOK 13.3m
Incorporated 2013
Share capital NOK 30,000

LØKKE-INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 912418324. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 1 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder investeringer i aksjer, obligasjoner, selskapsandeler og verdipapirer, selv eller gjennom hel- eller deleide selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 2.2m in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 2.2m
Equity
NOK 13.3m
Est. value
NOK 13.5m

Financial health · 2025

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

Who owns LØKKE-INVEST AS?

HEGE LØKKE JOHANNESSEN
LØKKE-INVEST AS
NOK 2.3m rev. · NOK 2.2m profit

LØKKE-INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LØKKE-INVEST AS own?

LØKKE-INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about LØKKE-INVEST AS

Who owns LØKKE-INVEST AS?

HEGE LØKKE JOHANNESSEN is the largest registered owner, with 100.0%.

What is the revenue of LØKKE-INVEST AS?

LØKKE-INVEST AS had revenue of NOK 2.3m in 2025.

Who is the general manager of LØKKE-INVEST AS?

Hege Løkke Johannessen is registered as general manager of LØKKE-INVEST AS.

Where is LØKKE-INVEST AS based?

LØKKE-INVEST AS has its business address in Oslo.

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.