biztrac. BETA
COMPANY REGISTER PROFILE
932608626 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

LLH 3 AS

Org. no. 932608626 Limited company (AS) Surnadal Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −131,000
Equity NOK 400.9m
Incorporated 2023
Share capital NOK 2.8m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−131k kr).

LLH 3 AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 932608626. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 2.8m, divided into 37500 shares. The company's stated purpose is: “Selv, eller gjennom hel- eller deleide selskaper, eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, fast eiendom, samt annen virksomhet som har naturlig sammenheng med dette.”.

Former names: LLH III AS

Key figures · 2025

Operating profit
NOK −131,000
▲ +23 %
Equity
NOK 400.9m
▲ +2 %
Est. value
NOK 339.6m

Financial health · 2025

Liquidity
0.29
Not satisfactory
Current assets ÷ current liabilities
Profitability
4.8%
Weak
Return on total assets
Solidity
63.2%
Very good
Equity as a share of total capital

Who owns LLH 3 AS?

LLH 3 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does LLH 3 AS own?

LLH 3 AS holds stakes in 21 companies:

See the full ownership structure →

Frequently asked questions about LLH 3 AS

Who owns LLH 3 AS?

Lars Løseth is the largest registered owner, with 80.0%.

Who is the general manager of LLH 3 AS?

Lars Løseth is registered as general manager of LLH 3 AS.

Where is LLH 3 AS based?

LLH 3 AS has its business address in Surnadal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.