BIZTRAC BETA
Development of building projects

LEINA HOLDING AS

Org. no. 996475522 Limited company (AS) Kongsberg Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −70,000
Equity NOK 13.7m
Incorporated 2011
Share capital NOK 900,000

Signals

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

LEINA HOLDING AS is registered as a limited company in Kongsberg, Buskerud with organisation number 996475522. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2011. Registered share capital is NOK 900,000, divided into 4500000 shares. The company's stated purpose is: “Investere i fast eiendom og andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −70,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −70,000
Equity
NOK 13.7m
Est. value
NOK 12.5m

Financial health · 2024

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

Who owns LEINA HOLDING AS?

ENEO EIENDOM AS
LEINA HOLDING AS
NOK 0 rev. · NOK −70,000 profit

LEINA HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does LEINA HOLDING AS own?

LEINA HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about LEINA HOLDING AS

Who owns LEINA HOLDING AS?

ENEO EIENDOM AS is the largest registered owner, with 33.3%.

What is the revenue of LEINA HOLDING AS?

LEINA HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of LEINA HOLDING AS?

Morten Hotvedt is registered as general manager of LEINA HOLDING AS.

Where is LEINA HOLDING AS based?

LEINA HOLDING AS has its business address in Kongsberg.

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.