BIZTRAC BETA
Manufacture of fluid power equipment

ASKER HYDRAULIKK AS

Org. no. 919501812 Limited company (AS) Asker Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 45.2m
Operating profit NOK 6.4m
Equity NOK 12.0m
Incorporated 2017
Employees 8
Share capital NOK 30,000

ASKER HYDRAULIKK AS is registered as a limited company in Asker, Akershus with organisation number 919501812. The business is classified under manufacture of fluid power equipment (NACE 28.120). The company was incorporated in 2017 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Å levere hydrauliske løsninger, komponenter og tjenester av høy kvalitet, til riktig pris og med stor grad av service til våre kunder i industri, marine og offshoremarkedet.”. The most recent filed accounts, for the 2025 financial year, show NOK 45.2m in revenue and NOK 6.4m in operating profit.

Key figures · 2025

Revenue
NOK 45.2m
Operating profit
NOK 6.4m
Equity
NOK 12.0m
Est. value
NOK 29.5m

Financial health · 2025

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

Who owns ASKER HYDRAULIKK AS?

ROGER STORAA
ASKER HYDRAULIKK AS
NOK 45.2m rev. · NOK 6.4m profit

ASKER HYDRAULIKK AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about ASKER HYDRAULIKK AS

Who owns ASKER HYDRAULIKK AS?

ROGER STORAA is the largest registered owner, with 22.5%.

What is the revenue of ASKER HYDRAULIKK AS?

ASKER HYDRAULIKK AS had revenue of NOK 45.2m in 2025.

Who is the general manager of ASKER HYDRAULIKK AS?

Lise Svenskerud is registered as general manager of ASKER HYDRAULIKK AS.

Where is ASKER HYDRAULIKK AS based?

ASKER HYDRAULIKK AS has its business address in Asker.

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.