BIZTRAC BETA
Rental and operating of own or leased real estate

LJH HOLDING AS

Org. no. 988979821 Limited company (AS) Røros Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 16,000
Operating profit NOK −9,000
Equity NOK 14.4m
Incorporated 2005
Share capital NOK 135,000

Signals

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

LJH HOLDING AS is registered as a limited company in Røros, Trøndelag with organisation number 988979821. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 135,000, divided into 135 shares. The company's stated purpose is: “Investering i andre selskaper og konsulentvirksomhet, samt annet som står i forbindelse med dette herunder deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 16,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 16,000
Operating profit
NOK −9,000
Equity
NOK 14.4m
Est. value
NOK 10.0m

Financial health · 2024

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

Who owns LJH HOLDING AS?

HÅVARD UGLEM HOVDAHL
LJH HOLDING AS
NOK 16,000 rev. · NOK −9,000 profit

LJH HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does LJH HOLDING AS own?

LJH HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about LJH HOLDING AS

Who owns LJH HOLDING AS?

HÅVARD UGLEM HOVDAHL is the largest registered owner, with 32.6%.

What is the revenue of LJH HOLDING AS?

LJH HOLDING AS had revenue of NOK 16,000 in 2024.

Where is LJH HOLDING AS based?

LJH HOLDING AS has its business address in Røros.

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.