BIZTRAC BETA
Repair and maintenance of machinery

KAM LIFTING CONSULT AS

Org. no. 812026992 Limited company (AS) Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 21.8m
Operating profit NOK 2.7m
Equity NOK 3.5m
Incorporated 2013
Employees 23
Share capital NOK 67,000

KAM LIFTING CONSULT AS is registered as a limited company in Hå, Rogaland with organisation number 812026992. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2013 and has 23 registered employees. Registered share capital is NOK 67,000, divided into 666 shares. The company's stated purpose is: “Mekanisk vedlikehold, inspeksjon og sertifisering av innrettninger, salg av tjenester og varer og andre produkt/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 21.8m in revenue and NOK 2.7m in operating profit.

Key figures · 2024

Revenue
NOK 21.8m
Operating profit
NOK 2.7m
Equity
NOK 3.5m
Est. value
NOK 11.8m

Financial health · 2024

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
38.9%
Good
Equity as a share of total capital

Who owns KAM LIFTING CONSULT AS?

MICHAEL ALBERT DALE
KAM LIFTING CONSULT AS
NOK 21.8m rev. · NOK 2.7m profit

KAM LIFTING CONSULT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KAM LIFTING CONSULT AS

Who owns KAM LIFTING CONSULT AS?

MICHAEL ALBERT DALE is the largest registered owner, with 50.0%.

What is the revenue of KAM LIFTING CONSULT AS?

KAM LIFTING CONSULT AS had revenue of NOK 21.8m in 2024.

Who is the general manager of KAM LIFTING CONSULT AS?

Kåre Vold is registered as general manager of KAM LIFTING CONSULT AS.

Where is KAM LIFTING CONSULT AS based?

KAM LIFTING CONSULT AS has its business address in Vigrestad.

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.