BIZTRAC BETA
Construction of residential and non-residential buildings

HÅNDLYKKEN BYGG AS

Org. no. 986242996 Limited company (AS) Molde Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 5.5m
Operating profit NOK 279,000
Equity NOK 981,000
Incorporated 2003
Employees 6
Share capital NOK 100,000

HÅNDLYKKEN BYGG AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 986242996. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2003 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Byggentreprenør og tilliggende virksomhetsområder med hovedvekt lagt på vedlikehold og oppsetting av trehus.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.5m in revenue and NOK 279,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.5m
Operating profit
NOK 279,000
Equity
NOK 981,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns HÅNDLYKKEN BYGG AS?

HÅNDLYKKEN HOLDING AS
HÅNDLYKKEN BYGG AS
NOK 5.5m rev. · NOK 279,000 profit

HÅNDLYKKEN BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HÅNDLYKKEN BYGG AS

Who owns HÅNDLYKKEN BYGG AS?

HÅNDLYKKEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of HÅNDLYKKEN BYGG AS?

HÅNDLYKKEN BYGG AS had revenue of NOK 5.5m in 2024.

Who is the general manager of HÅNDLYKKEN BYGG AS?

Karl Håndlykken is registered as general manager of HÅNDLYKKEN BYGG AS.

Where is HÅNDLYKKEN BYGG AS based?

HÅNDLYKKEN BYGG AS has its business address in Skåla.

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.