BIZTRAC BETA
Legal activities

LHN HOLDING AS

Org. no. 918314776 Limited company (AS) Kristiansund Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −17,000
Equity NOK −392,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−392k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−17k kr).

LHN HOLDING AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 918314776. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investere i andre selskaper samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK −392,000

Financial health · 2024

Liquidity
0.44
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-430.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LHN HOLDING AS?

LARS HELGE NEERGÅRD
LHN HOLDING AS
NOK 0 rev. · NOK −17,000 profit

LHN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LHN HOLDING AS own?

LHN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LHN HOLDING AS

Who owns LHN HOLDING AS?

LARS HELGE NEERGÅRD is the largest registered owner, with 100.0%.

What is the revenue of LHN HOLDING AS?

LHN HOLDING AS had revenue of NOK 0 in 2024.

Where is LHN HOLDING AS based?

LHN HOLDING AS has its business address in Frei.

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.