BIZTRAC BETA
Other captive investment companies

LEE AS

Org. no. 988970824 Limited company (AS) Hemsedal Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −184,000
Equity NOK 20.3m
Incorporated 2005
Share capital NOK 280,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−184k kr).

LEE AS is registered as a limited company in Hemsedal, Buskerud with organisation number 988970824. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 280,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er investering i fast eiendom og andre finansplasseringer samt salg av konsulenttjenester. Selskapet kan delta i andre foretak og hva dermed er forbundet. ”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −184,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −184,000
Equity
NOK 20.3m
Est. value
NOK 29.3m

Financial health · 2024

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

Who owns LEE AS?

LARS ERIK EIKRE
LEE AS
NOK 0 rev. · NOK −184,000 profit

LEE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LEE AS own?

LEE AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about LEE AS

Who owns LEE AS?

LARS ERIK EIKRE is the largest registered owner, with 98.0%.

What is the revenue of LEE AS?

LEE AS had revenue of NOK 0 in 2024.

Who is the general manager of LEE AS?

Lars Erik Eikre is registered as general manager of LEE AS.

Where is LEE AS based?

LEE AS has its business address in Hemsedal.

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.